Some problems and their solutions: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 15: | Line 15: | ||
The IOC summary page will show you if all the VME crate controllers are talking. The example shown here is from a broken system where IOC 9 is not talking. | The IOC summary page will show you if all the VME crate controllers are talking. The example shown here is from a broken system where IOC 9 is not talking. | ||
[[File:VME_IOC_Summary.png]] | [[File:VME_IOC_Summary.png]] | ||
Open the terminal window for any miscreant IOC. | |||
One possibility is a broken Ethernet cable. This leads to the message | |||
0x3ff73940 (tBoot): miiPhyInit check cable connection | |||
at the beginning of the boot, and the IOC never loads and never works. | |||
== problem: == | == problem: == | ||
write your text here | write your text here | ||
Revision as of 22:02, October 30, 2017
problem: Mike has too many windows on the screen
Yea, we know!
Things are in general broken and you don't know what it is
That's specific, eh? Well, hopefully we can disambiguate a bit from here.
Are all the IOCs in the mood?
The nominal first step is to use DGSCommander's main screen. Hit the VME Status button to bring up the IOC summary.
The IOC summary page will show you if all the VME crate controllers are talking. The example shown here is from a broken system where IOC 9 is not talking.
Open the terminal window for any miscreant IOC.
One possibility is a broken Ethernet cable. This leads to the message
0x3ff73940 (tBoot): miiPhyInit check cable connection
at the beginning of the boot, and the IOC never loads and never works.
problem:
write your text here