Difference between revisions of "DAQ Troubleshooting"
From PREX Wiki
Jump to navigationJump to search| Line 4: | Line 4: | ||
== For shift workers == | == For shift workers == | ||
| − | [[File:EB_disconnected.png|thumb|600px|right|Figure | + | [[File:EB_disconnected.png|thumb|600px|right|Figure 1 - CODA window showing EB1 disconnected. ]] |
| − | [[File:Kcoda_while_running.png|thumb|400px|right|Figure | + | [[File:Kcoda_while_running.png|thumb|400px|right|Figure 2 - If you attempt to kill CODA while is it running, this window pops up. Type Y if you really want to kill it.]] |
| − | [[File:ROC_disconnected.png|thumb|600px|right|Figure | + | [[File:ROC_disconnected.png|thumb|600px|right|Figure 3 - If a ROC becomes disconnected, you will see warning messages in the message window.]] |
| − | [[File:ROC_disconnected_2.png|thumb|600px|right|Figure | + | [[File:ROC_disconnected_2.png|thumb|600px|right|Figure 4 - There may be a report that a particular ROC is disconnected.]] |
| − | [[File:Reboot_ROC_from_terminal.png|thumb|400px|right|Figure | + | [[File:Reboot_ROC_from_terminal.png|thumb|400px|right|Figure 5 - If the ROC's console is responding, you can type ''reboot''. ]] |
| − | * Either the Event Builder (EB1) or Event Recorder (ER1) are disconnected (see Figure | + | * Either the Event Builder (EB1) or Event Recorder (ER1) are disconnected (see Figure 1) |
| − | ** type '''kcoda''' in a terminal, say '''Y'''(see Figure | + | ** type '''kcoda''' in a terminal, say '''Y'''(see Figure 2) |
** '''startcoda''' (follow instructions for [[CODA#Starting the GUI| starting CODA]]) | ** '''startcoda''' (follow instructions for [[CODA#Starting the GUI| starting CODA]]) | ||
| − | * If a ROC is disconnected (see Figures | + | * If a ROC is disconnected (see Figures 3 and 4) |
*# try to reset; if successful you should get Client is back message and everything should report ''Configured'' | *# try to reset; if successful you should get Client is back message and everything should report ''Configured'' | ||
*# if a ROC is still reporting a problem - note which ROC is reporting the problem | *# if a ROC is still reporting a problem - note which ROC is reporting the problem | ||
| − | *## if the console for that ROC is responding type '''reboot''' and enter (see Figure | + | *## if the console for that ROC is responding type '''reboot''' and enter (see Figure 5) |
*## otherwise, use the remote power cycle to reboot that ROC (link to be added later) | *## otherwise, use the remote power cycle to reboot that ROC (link to be added later) | ||
== For Experts == | == For Experts == | ||
Revision as of 14:34, 9 June 2019
In the process of editing and updating this page. Please contact Juliette Mammei crowder@jlab.org with questions or suggestions.
PREX Main<< CODA
For shift workers
- Either the Event Builder (EB1) or Event Recorder (ER1) are disconnected (see Figure 1)
- type kcoda in a terminal, say Y(see Figure 2)
- startcoda (follow instructions for starting CODA)
- If a ROC is disconnected (see Figures 3 and 4)
- try to reset; if successful you should get Client is back message and everything should report Configured
- if a ROC is still reporting a problem - note which ROC is reporting the problem
- if the console for that ROC is responding type reboot and enter (see Figure 5)
- otherwise, use the remote power cycle to reboot that ROC (link to be added later)
