Reports 1-1 of 1 Clear search Modify search
DGS (General)
keiko.kokeyama - 14:32 Tuesday 30 January 2018 (4050) Print this report
Strange RTC trouble

When I was trying to solve the issue of the tiltsensor model, k1vists on k1imc0 computer, exactly when "startk1vists" on k1imc0, the k1imc0 computer suddenly died. "No route" error appears when ssh. I had to turn off the computer with the remote power control from the web browser (10.68.99.155), and turn it on again.

When k1imc0 is turned on again remotely, because of the known dolphin problem, models on k1ioo died. "startk1psl" did not work in terms of the DAC output. So I "sudo reboot"-ed k1ioo.

After k1ioo is rebooted, IRIG-B of k1ioo on GDS_TP screen went 99999 again crying

Apparently with IRIG-B 99999, the DAQ status is 0x4000. Only the good news is the IMC control through the dolphin (IMC model on k1ioo to the suspensions on k1imc0) seems OK; IMC still can be locked. Phew.

Comments to this report:
keiko.kokeyama - 10:49 Wednesday 21 February 2018 (4234) Print this report

I tried "yamamoto method" [1]  to recover the timing erorr, however, it did not work.

[1] Yamamoto-san reported some of the FE recovered from the timing issue by the following procedure:
- unplug the adapter code of ADC0
- all the models die on that FE
- kill all the slave models
- start the iop model
- start the slave models
 

Search Help
×

Warning

×