Displaying report 1-1 of 1.
Reports until 15:39, Thursday 24 September 2015
H1 SEI
hugh.radkins@LIGO.ORG - posted 15:39, Thursday 24 September 2015 (21908)
HAM5 ISI Rogue Excitation Recovery

BTL logged some details about the Rogue Excitation Problem we suffer with HAM5 ISI.  The solution to this problem is fixing the coil driver monitor or unwiring this signal from the model.  We might get approve to fix this in one way or the other but until then...  We have to recover.

If you look at the model image Brian includes, you can see or not and I'll tell you anyway, if the Masterswitch is opened or the WD is fully (state4) tripped for more than 3 seconds, the Rogue Exc alarm will go off (because of the perceived excess voltage.)  This is why it always goes into Rogue alarm everytime the WD trips.  Also why it is a problem when we have opened the master switch.

So to untrip the platform, you have to untrip the watchdog, and untrip the rogue trip within 3 seconds.  If you manage to do this fast enough which isn't that bad, and the guardian wasn't the one to close the masterswitch, you could end up with an SPM diff showing on the guardian for HAM5 SEI.  Not that this is a big deal as we aren't keying on SPM and yes we could unmonitor the SEI but I like the monitoring.

So if the ISI is tripped:

1) check that the MASTER SWITCH is closed,

2) On the Watchdog page Click RESET ALL Rogue Exc WD RESET, and RESET ALL again, all within a couple seconds.

If it trips again, check the MASTERSWITCH, if it is open, it may be the Guardian, make sure the Guardian is set to Isolated and try the RESETs again.

Until we do the main fixes in line one, if these steps don't work, call me anytime.

If you end up with SPM diffs, and you care, you may be in for a platform cycle to OFFLINE (includes HEPI) so that the GUARDIAN closes the MASTERSWITCH.

Once OFFLINE (MASTERSWITCHs open,) set the guardina to isolated and do the above RESET dance.  I'm crossing my fingers so be patient.

Displaying report 1-1 of 1.