From: Frank Geurts (geurts_at_rice.edu)
Date: Wed Feb 12 2003 - 20:02:41 EST
just when you thought you weren't getting enough daily emails from STAR
... here's another one!
TOFr HV event file consists of 6 lines filled with integers only:
unix_timestamp
hv_status
HVA-_Vread HVA-_Vset HVA-_Iread HVA-_Imax
HVA+_Vread HVA+_Vset HVA+_Iread HVA+_Imax
HVB-_Vread HVB-_Vset HVB-_Iread HVB-_Imax
HVB+_Vread HVB+_Vset HVB+_Iread HVB+_Imax
(example see below)
The hv_status tells us whether the system is supposed to be on (1) or
off (0) and should be used to prevent alarms when HVXy_Vread = 0 and
HVXy_Vset != 0. The voltages are all in Volts and the currents are
always in nA.
There will be no control for the TOFr HV through the slowcontrols
interface, only monitoring. The following monitoring alarms apply:
-TOFr HV comm problem:
yellow: if the file hasn't been updates in 1 minute (maybe we should
make that >60 just to be safe from false alarms)
red: if the file hasn't been updated for more than 20 minutes
-TOFr HV problems
yellow: if any of the HV is off by more than 20V
yellow: if any current is >200nA
red: if current is above 500 which is just above the auto-ramp
currents of 470nA (both current limits will change as we gain more and
more experience)
red: if any HV is off by more than 500V (typically this alarm will go
off when the auto-ramp brings the voltage back from 0 to 7125V, which
takes ~10minutes)
I think that the voltage and current limits will all change and
eventually reflect a compromise between keeping the shiftcrew alert and
annoyed ;)
-frank
-----tofrhv.evt
1045094706
1
7118 7125 0 16000
7122 7125 0 16000
7118 7125 0 16000
7118 7125 0 16000
------
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:34 EDT