|
Choose one of the following options:
MONITORING VIA STAR SLOW CONTROLS
Screenshots:
slowcontrols.jpg,
tof_top.jpg,
tofphv.jpg,
tofrhv.jpg
- Use STAR Slowcontrols monitor to check TOFr HV:
Go to slow controls terminal and click on TOF->TOFrHV->P
(see slowcontrols.jpg)
or open as user "sysuser" an xterminal on sc3.starp and start the TOF
alarm handler "tof_top" (see tof_top.jpg) and click on
"TOFr HV Monitor" (see tofrhv.jpg)
- watch the unix timestamp update (should do so 1/minute) and
check that the read voltages are all close to the set voltages.
When currents are too high for more than 1 minute audible Yellow or Red SC
alerts will ring.
MONITORING VIA TERMINAL ACCESS
Screenshots:
- Sit in front of the TOFp Control PC, and open a unix terminal window.
Then ssh to the machine tofpdaq.star (the password is posted there).
- Check whether the TOFr HV monitoring daemon is running by typing
crontab -l The output should look like this:
[tofp@tofpdaq ~]% crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (tofrhv.cron installed on Thu Feb 13 15:33:32 2003)
# (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)
#
# TOFr HV monitoring cron job
#
SHELL=/bin/sh
#
# run every minute
* * * * * $HOME/HSCAENETLib-1-3/tofr/tofrhv_mon.sh
- if the program (tofrhv_mon.sh) is not running, contact the
TOFp Detector Experts (tofp@physics.rice.edu)
- To check the history of the V and I readouts, use the command
tail /data/hv/tofrhv.log
The output typically looks like the following, where the columns represent:
linux-timestamp HVA- (Vread, Vset, Iread/10, Iset/10) HVA+(idem), HVB-(idem) and HVB+(idem).
Voltages are in Volts and currents are in nA (note that the currents in the log file
are divided by 10, so 4 means 40nA).
[tofp@tofpdaq ~]% tail /data/hv/tofrhv.log
1048630260 6996 7000 1 1600 7002 7000 0 1600 7000 7000 0 1600 7000 7000 1 1600 Tue Mar 25 17:11:00 2003
1048630320 6994 7000 0 1600 7000 7000 0 1600 6998 7000 0 1600 6998 7000 1 1600 Tue Mar 25 17:12:00 2003
1048630380 6994 7000 1 1600 7000 7000 0 1600 6998 7000 0 1600 6996 7000 1 1600 Tue Mar 25 17:13:00 2003
1048630441 6994 7000 0 1600 7000 7000 0 1600 7000 7000 0 1600 6996 7000 0 1600 Tue Mar 25 17:14:01 2003
1048630500 6994 7000 1 1600 7000 7000 0 1600 6998 7000 0 1600 6998 7000 1 1600 Tue Mar 25 17:15:00 2003
1048630560 6994 7000 1 1600 7000 7000 0 1600 6998 7000 0 1600 6998 7000 0 1600 Tue Mar 25 17:16:00 2003
1048630620 6994 7000 0 1600 7000 7000 0 1600 6998 7000 0 1600 6998 7000 1 1600 Tue Mar 25 17:17:00 2003
1048630680 6994 7000 1 1600 7000 7000 0 1600 6998 7000 0 1600 6998 7000 1 1600 Tue Mar 25 17:18:00 2003
1048630741 6994 7000 0 1600 7000 7000 0 1600 6998 7000 0 1600 6998 7000 0 1600 Tue Mar 25 17:19:01 2003
1048630801 6994 7000 0 1600 7000 7000 0 1600 6998 7000 0 1600 6996 7000 0 1600 Tue Mar 25 17:20:01 2003
- To check the history for recent TOFr HV trips, , use the command
tail /data/hv/tofrhv.err
- The output typically looks like this.
HV channels off ... waiting 3min before recovering phase. Thu Apr 10 19:30:00 2003
TOFr HV switched ON
HV channels off ... waiting 3min before recovering phase. Thu Apr 10 21:00:00 2003
TOFr HV switched ON
HV channels off ... waiting 3min before recovering phase. Thu Apr 10 22:22:00 2003
TOFr HV switched ON
-
The system auto-ramps 3 min after a trip. Contact TOFp Detector
Experts (tofp@physics.rice.edu) when the trips occur very frequently (~1/hr) and
do not seem to be related to beam conditions.
|
