Hall probe logbook

----------------------
Nov 25, 2002 (PB)

Version 3.0 of the read-out code installed: Writes the year to the raw data
after the timestamp (timestamp didn't include the year so far).
Version 7 of the calibrator installed: Reads the year from the raw data
and writes it to the "calibrated" data (.results files).

hallGrabber.py script doesn't like this additional info in the data,
keeps sending error messages. Script stopped, data will queue up on PC
now. Waiting for Vladimir to give us an updated version of the script.
----------------------
Jul 10, 2002 (PB)

New cable installed between read-out PC and power supply (yesterday). This 
will allow the PC to be moved to the top of the rack.
----------------------
Mar 3, 2002  (RPS)

Hall readout crashes ~23:40.  System off until Mar 4, ~10:30 when I 
cycled the power to the system.   Cause of crash unknown, fix successful.
----------------------
Feb 23, 2002 (PB)

Stopped writing down every incident of a read-out crash.
I conclude the system is sensitive to external noise from ramping
HV or magnets, and that this is not prohibitive to the operation.
----------------------
Feb 23, 2002 (PB)

Installed Oracle client and tnsnames on d0ntnik06. Stu Fuess had
to do the Oracle client, because admin privs were needed.
----------------------
Feb 20, 2002 (PB)

Automatic read-out faild Feb 20 between 9.20 and 10.20am.
System recovered automatically and data taking continued normally
at 11.30 on Feb 20.
----------------------
Feb 19, 2002 (PB)

Automatic read-out faild Feb 18 between 16.20 and 17.20.
Automatic recovery didn't help and I had to power-cycle the system
Feb 19 11.50am to get it to work again. 
Reason for failure: Magnets have been on steadily, but there has
been a lot of "HV activity" in the time frame of the failure: trips, 
muon HV ramped to full, new store, new run... Lots of possibilities.
----------------------
Feb 18, 2002 (PB)

Automatic read-out faild Feb 17 between 22.20 and 23.20.
System recovered automatically and data taking continued normally
at 00.30 on Feb 18.
During this time the magnets have been charged and together
with R.P.Smith I determined that in three out the previous four
glitches of the read-out the magnets were being charged or
decharged as well.
----------------------
Feb 15, 2002 (PB)

Installed python 2.2 and DCOracle 2 on d0ntnik06 (the readout pc).
Installed new calibration software, v6, and took first data with
that version at 14:38. Calibrator v6 also stores field values in
ADC counts in the result files, so that it can be stored in the
online database.
----------------------
Feb 14, 2002 (PB)

Automatic read-out failed Feb 14 2002 between 00.30 and 01.30. 
System recovered automatically and data taking continued normally
at 2.30am.
----------------------
Feb 12, 2002 (PB)

Automatic read-out failed Feb 11 2002 between 19.20 and 20.20. No
power cycling was necessary to get the system going again. I set up 
automatic recovery from instances like this.
Logbook says solenoid and toroid were switched on in reverse at 19.37,
and CFT crate 0x52 was power cycled around 20.00.
----------------------
Feb 11, 2002 (PB)

Automatic read-out failed Feb 9 2002 between 1am and 2am. When trying to
start the automatic read-out, CAN node 48 sends an emergency signal when
it tries to initialize. I couldn't find anything that went wrong, and power
cycling the system solved the problem. The only thing that seemed remotely
relevant from the shifter's log was that Ryan Hooper power-cycled the VLPC's
at 1.37 am.
----------------------
Feb 2, 2002

Installed read-out software that reads out the entire system once and
writes field file and geometry file.
Started automatic read-out (once every hour).
----------------------
March 1, 2001

We installed cushions of soft plastic foam under conditioner lids, to push 
down the Hall head connectors, to prevent them from coming loose again. 
Cushions installed in *all* conditioners but N2I. Scaffolding is not high 
enough, conditioner unreachable. 
The remaining problems are invalid temperatures at heads N3OC and S6OA. All 
magnetic sensors can be read out.

----------------------
Feb 28, 2001

Swapped conditioners on port 3 and 5 on South CAN, we found the problem 
first seen on port 3 had moved to port 5, and port 3 was OK. We swapped them 
back again.
Currently read-out errors are being seen at
CAN  port
32   0, 3, 4
48   0, 1, 2, 3

Found a disconnected Hall head inside conditioner 4 (CAN 48, port 3). Connected 
again, power down&up, take run: conditioner was OK again!

The head in conditioner 8 doesn't have disconnected Hall heads, but at a 
second look, we see that the Bx, By, Bz seem to be OK, it's only the temperature 
that's not valid (ADC has status F3, all others F0).

----------------------
Feb 26, 2001

5pm: Found following conditioners giving read-out errors: S1I, S2I, S3I,
S4I, N1I, N4I, N5I.
6pm: Replaced cables between South CAN and S1I and S2I, unplugged and
plugged back in all the others, power cycled the system
7pm: S2I and N4I are back alive
8pm: Replace cables between CAN nodes and S3I, S4I, N1I, N5I. Then power
cycle the system
9pm: S4I back alive. S1I, S3I, N1I and N5I are still having problems.

----------------------