Motorola single board computers for vxWorks

dec16



Intro:

Setup:

Documentation:
List of AO boards:
Board history:
Failures


SETUP:



Documentation:


List of AO boards

    The table below is a partial list of the motorola boards we are using for datataking (using vxWorks) at ao. The table also includes spares and boards that have died
If assigned a number (AO# n) to each board. There should be a sticker on the front of each board with this number (for identification).
Status codes:

Board Types:



AO
#
mvme
#
serial
#
status
notes,
1
mv167-04a
1199939
D
  • 10sep14: purchased after pntCrate failure
  • 11sep14: installed in rfi rack slot1 when mv147 cpu failed
    • did not run reliably..removed cpu and sent back to company
2 mv167-02b 3320674 OK
spare
  • purchased 06apr11 as spare for pntp1-3
  • currently in rfi crate
3
mv167-04a
1148597
D
  • was pnt computer until 08sep14 (when it failed)
    • after 2 hour power outage, the board would no boot up.
    • (more info on failure)
4
mv167-034b
1644547
D
da
  • 06apr11 - purchased as spare.
  • 10sep14 - pnt cpu (AO#3) died. cor cpu (AO#6)-> pnt.
    • this cpu (AO#4) -> cor cpu
  • end 2016 ao#4 -> da (switched with ao8 since ao8 had reboot problems
  • 21jan20 - load vwWorks kernel but then tNetTask crashed the system.  cycled power
  • a bunch of times, same trouble. booted without startup script.. but network task always ended up
  • crashing the system. replaced with #20
5
mv167-034a
1406315
D
  • nov93 - arrived installed as da
  • motherboard:1-W3826B 34D
  • 26nov16: failed  (more info on failure)
6
mv167-04a
1427967
OK
pnt
  • 1993 purchased ..check
  • cor computer
  • sep14 -> pnt
7
mv167-34a
1444950
OK
spare
  • 28oct16 purchased as spare for da
  • motherboard: 01-W3826B 32D
  • 34A needs front panel tick input (to gpio.. ).. later installed
  • checked on da and works ok.
  • If used on da.. need to update the ext_tickinit routine in config.. see notes above.
8
mv167-34b
2332527
OK
cor
  • 28oct16  purchased as spare for cor.
  • end 2016: moved to cor..
    • needed occasional reboots. was easier to do it on cor
9
mv162-513a
2986560
OK
corp8
  • 06apr11 purchased as spare for corp6-p9
  • mac: 08003e26c640
  • 01dec16 installed at corp8 when corp8 failed.
10
mv162-533a
2332257
OK
spare
  • oct96: purchased
  • purchased for 2nd cpu in rfi crate.
  • currently in rfi crate (not in use).
  • from mvmeBug:
    • Board Identifier          = "MVME162-533A(CE)"
    • Artwork (PWA) Identifier  = "01-W3960B70A    "
    • Ethernet Address          = 08003E25196C
11


D
  • was pntp1
  • failed on 01feb20.
  • came up , but wouldn't connect to the backplane network.
  • replaced by ao21
12


pntp2
13


pntp3
14


corp1
15


corp6
16


corp7
17


corp9
18


dap1
19


dap2 mac address 08003e26d992. removed 13mar17. yellow light on.
20
mv167-34b


da
  • purchased 2018 or 19
  • installed 21jan20 after ao#4 failed
21
mv167-04a

pntp1
  • installed 01feb20 whn
90
mv162-513
1995332
D
  • purchased (1995?)
  • was corp8 .. one of the 162fx boards for the interim correlator.
  • motherboard:01-W3960B 01C
  • 01dec16: failed when cor crate off for 1 day (more info)fao;e

Board usage history

    The table below tries to keep track of which boards were being used:

date
pnt
cor
da
rfi
spares

pnt
pntp1
pntp1
pntp3
cor
corp1
corp6
corp7
corp8
corp9
da
dap1
dap2
rfi
rfip1

1993




6











9610xx















10
110406
3



6



90

5




2,4,9
140907
3



6



90

5





140908
6



4



90

5





140914
6



4



90

5


rfi crate
removed

161126
6



4



90

8





161201
6



4



9

8





16????



8





4





200121










20





200201

21

















Failures


<- page up
home_~phil