DAQ Troubleshooting

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

Figure 1 - CODA window showing EB1 disconnected.

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.

Figure 3 - If a ROC becomes disconnected, you will see warning messages in the message window.

Figure 4 - There may be a report that a particular ROC is disconnected.

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 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)
  1. try to reset; if successful you should get Client is back message and everything should report Configured
  2. if a ROC is still reporting a problem - note which ROC is reporting the problem
     1. if the console for that ROC is responding type reboot and enter (see Figure 5)
     2. otherwise, use the remote power cycle to reboot that ROC (link to be added later)

For Experts

• DAQ NFS - exists but empty
• DAQ Network Ethernet - exists but empty
• DAQ Network Portserver - exists but empty
  • DAQ Documentation Portal