717
Comment:
|
1237
|
Deletions are marked like this. | Additions are marked like this. |
Line 22: | Line 22: |
=== When DC status is 0x2 == Real time model is not sending data to k1dc0 machine. Try following. The first name is a computer name where the model is running, |
|| DC status || What to do || || 0x0 || Good status! || || x4000|| Data is being sent and you can leave it. Master IOP gets it when the timing synchronization is fuked up. || || x2000|| When the master IOP's timing is not synchrimized properly, slave model shows this code.|| || 0x2 || Real time model is not sending data to k1dc0 machine. Go to (1) || |
Line 25: | Line 28: |
{{{ssh k1}}} | (1) {{{ ssh <FE macehine name such as k1pr0> sudo /etc/init.d/mx_stream restart }}} (2) {{{ ps -ef | grep daqd }}} Check the process number of daqd. There may be two or three and pick the first and left number (###). {{{ kill ### }}} {{{daqd}}} process will automatically start up again, and the DAC status will be cleared. |
Check if the real time models are sending data to DAQ
1. Open sitemap on an workstation
$sc $medm sitemap.adl
2. Open CDS screen
3. Open GDS_TP screen of each model (blue buttons)
4. Check that "DC Status" is 0x0
DC status |
What to do |
0x0 |
Good status! |
x4000 |
Data is being sent and you can leave it. Master IOP gets it when the timing synchronization is fuked up. |
x2000 |
When the master IOP's timing is not synchrimized properly, slave model shows this code. |
0x2 |
Real time model is not sending data to k1dc0 machine. Go to (1) |
(1)
ssh <FE macehine name such as k1pr0> sudo /etc/init.d/mx_stream restart
(2)
ps -ef | grep daqd
Check the process number of daqd. There may be two or three and pick the first and left number (###).
kill ###
daqd process will automatically start up again, and the DAC status will be cleared.