Changes between Version 7 and Version 8 of TroubleShootingBias

Timestamp:

02/18/15 00:12:22 (10 years ago)

Author:

Daniela Dorner

Comment:

added OverCurrent information

TroubleShootingBias

@@ -19 +19 @@
 - do not close or kill biasctrl
 
-== Overcurrent Status ==
+== OverCurrent Status ==
 
 __Symptom__
 
-- when biasctrl ramped the voltage, it get in the state OVERCURRENT
+- when biasctrl ramped the voltage, it get in the state OverCurrent
 
 __Solution__
 
-- First try biasctrl/RESET_OVER_CURRENT_STATUS (maybe a few times)
-- if it don't help try to ramp the voltage down
- - biasctrl/SET_GLOBAL_DAC 0
+1. BIAS_CONTROL/RESET_OVER_CURRENT_STATUS 
+2. then ramp down voltage, e.g. BIAS_CONTROL/SET_ZERO_VOLTAGE
+3. maybe you have to repeat 1. and 2. as during ramping down another OverCurrent can happen
 
 __Not Helping__
@@ -35 +35 @@
 - do not close or kill biasctrl
 
-== Status notReferenced ==
+__Repeated OverCurrent Status__
+
+if OverCurrent appears again
+
+- switch to bias-off measurement (see https://trac.fact-project.org/wiki/SpecialMeasurements) 
+- try data taking again after ~ 1 hour
+
+if this continues for several hours, you may go to bed earlier
+
+== Status NotReferenced ==
 
 __Symptom__
 
-- biasctrl is in state notReferenced
+- biasctrl is in state NotReferenced
 
 __Solution__
@@ -49 +58 @@
 
 - do not close or kill biasctrl
+
+== Locked ==
+
+__Symptom__
+
+biasctrl goes into Locked state (after ramping down the voltage) in case 
+
+* the (uncalibrated) currents increase to values > 2200 DAC
+* the voltage is on after the end of nautical twilight
+
+__Solution__
+
+- investigate why biasctrl went into Locked 
+- report in the logbook what happened
+- in case you consider it safe, you may send UNLOCK
+
+
+__Not Helping__
+
+- do not close or kill biasctrl
+