|
Size: 243
Comment:
|
Size: 1649
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| 1. Open sitemap on an workstation | == 1. Open sitemap on an workstation == |
| Line 8: | Line 8: |
| [[attachment:sitemap.png|{{attachment:sitemap.png|text describing image|width=300}}]] | |
| Line 9: | Line 10: |
| 1. Open CDS screen | |
| Line 11: | Line 11: |
| 1. Open GDS_TP screen of each model (blue buttons) | == 2. Open CDS screen == |
| Line 13: | Line 13: |
| 1. Check that "DC Status" is 0x0 | [[attachment:cdsscreen.png|{{attachment:cdsscreen.png|text describing image|width=300}}]] == 3. Open GDS_TP screen of each model (blue buttons) == == 4. Check that "DC Status" is 0x0 == [[attachment:gdstp.png|{{attachment:gdstp.png|text describing image|width=300}}]] || DC status || What to do || || 0x0 || Good status! || || x4000|| It is OK. Data is being sent and you can leave it. A master IOP gets this error when the timing synchronization is fucked up. || || x2000|| It is OK. When the master IOP's timing is not synchronized properly, their slave models show this code.|| || 0x2 || The real time model is not sending data to the data concentrator machine, k1dc0. Go to (1) || || blank || Channels are not registered to send to k1dc0. Go to (2) || (1) When DC status is 0x2 {{{ ssh <FE macehine name such as k1pr0> sudo /etc/init.d/mx_stream restart }}} mx_stream process will automatically start up again, and the DAC status will be cleared. (2) When DC status is blank {{{ ssh k1dc0 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. If it did not work, try to reboot the data concentrator: {{{ ssh k1dc0 sudo reboot}}} Wait patiently until {{{k1dc0}}} restarts. |
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 |
It is OK. Data is being sent and you can leave it. A master IOP gets this error when the timing synchronization is fucked up. |
x2000 |
It is OK. When the master IOP's timing is not synchronized properly, their slave models show this code. |
0x2 |
The real time model is not sending data to the data concentrator machine, k1dc0. Go to (1) |
blank |
Channels are not registered to send to k1dc0. Go to (2) |
(1) When DC status is 0x2
ssh <FE macehine name such as k1pr0> sudo /etc/init.d/mx_stream restart
mx_stream process will automatically start up again, and the DAC status will be cleared.
(2) When DC status is blank
ssh k1dc0 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. If it did not work, try to reboot the data concentrator:
ssh k1dc0 sudo reboot
Wait patiently until k1dc0 restarts.