Changeset 14267

Timestamp:

07/16/12 09:46:42 (12 years ago)

Author:

Jens Buss

Message:

additional out put for wait-states in scripts

File:

• trunk/FACT++/ScriptsForDimCtrl/FirstDrsCalib.dim (modified) (14 diffs)

trunk/FACT++/ScriptsForDimCtrl/FirstDrsCalib.dim

@@ -17 +17 @@
 .w 2000
 # stopping should always be possible, and end in state 'Connected'(6)
+> ...waiting for FEEDBACK to be in state 6: Connected
 .s FEEDBACK 6
 > ..done
@@ -30 +31 @@
 BIAS_CONTROL/SET_ZERO_VOLTAGE
 .w 2000
+> ...waiting for BIAS to be in state 7: VoltageOff
 .s BIAS_CONTROL 7
 > ...done
@@ -39 +41 @@
 BIAS_CONTROL/SET_GLOBAL_DAC 1
 .w 2000
+> ...waiting for BIAS to be in state 9: VoltageOn
 .s BIAS_CONTROL 9
 > ...done
@@ -59 +62 @@
 # in order to find out when the calibration ends, we have to wait for the transistion from state
 # 'Calibrating'(13) back to 'Connected'(6)
+> ...waiting for FEEDBACK to be in state 13: Calibrating
 .s FEEDBACK 13
+> ...waiting for FEEDBACK to be in state 6: Connected
 .s FEEDBACK 6
 
@@ -75 +80 @@
 BIAS_CONTROL/SET_ZERO_VOLTAGE
 .w 5000
+> ...waiting for BIAS to be in state 7: VoltageOff
 .s BIAS_CONTROL 7
 > ...done
@@ -83 +89 @@
 # and a second pedestal run, with the same ROI as our next data will be, i.e. ROI=300 in this case
 > taking DRS:Pedestal 1000 ...
-> OPERATOR: observe Events tab and make sure there are no patches with strange behaviour, which can be caused by DRS-CHIP Problems
+> ===================================================
+> OPERATOR: 
+> observe Events tab and make sure there are no patches 
+> with strange behaviour, which can be caused 
+> by DRS-CHIP Problems
+> ===================================================
+
 FAD_CONTROL/START_DRS_CALIBRATION
 ###FAD_CONTROL/SET_FILE_FORMAT 0
 MCP/START -1 1000 drs-pedestal
+> ...waiting for FAD to be in state 8: Writing Data
 .s FAD_CONTROL 8
+> ...waiting for FAD to be in state 4: Connected
 .s FAD_CONTROL 4
 > ... done
@@ -93 +107 @@
 > taking DRS:Gain 1000 ...
 MCP/START -1 1000 drs-gain
+> ...waiting for FAD to be in state 8: Writing Data
 .s FAD_CONTROL 8
+> ...waiting for FAD to be in state 4: Connected
 .s FAD_CONTROL 4
 > ... done
@@ -99 +115 @@
 > taking Pedestal 1000 ...
 MCP/START -1 1000 pedestal
+> ...waiting for FAD to be in state 8: Writing Data
 .s FAD_CONTROL 8
+> ...waiting for FAD to be in state 4: Connected
 .s FAD_CONTROL 4
 > ... done
@@ -111 +129 @@
 ###FAD_CONTROL/SET_FILE_FORMAT 0
 MCP/START -1 1000 pedestal
+> ...waiting for FAD to be in state 8: Writing Data
 .s FAD_CONTROL 8
+> ...waiting for FAD to be in state 4: Connected
 .s FAD_CONTROL 4
 > ... done
@@ -124 +144 @@
 # the feedback should be in state 'CurrentControl'(12) now
 # the feedback should be in state 'CurrentCtrlIdle'(9) now since 30.05.12
+> ...waiting for FEEDBACK to be in state 9: CurrentCtrlIdle
 .s FEEDBACK 9
 > ... done
@@ -130 +151 @@
 BIAS_CONTROL/SET_GLOBAL_DAC 1
 # after this command the bias_ctrl should be in state 'VoltageOn'(9) after a second or so
+> ...waiting for BIAS to be in state 9: VoltageOn
 .s BIAS_CONTROL 9
 > ...1 DAC globally set
@@ -135 +157 @@
 # when the feedback actually kicks in, the bias is first in state 'Ramping'(5) for some seconds and finally in 'VoltageOn'(9)
 # again
+> ...waiting for BIAS to be in state 5: Ramping
 .s BIAS_CONTROL 5
 > ...ramping to nominal voltage
+> ...waiting for BIAS to be in state 9: VoltageOn
 .s BIAS_CONTROL 9
 > ...bias on
@@ -149 +173 @@
 > taking Pedestal with BIAS on 3000 ...
 MCP/START -1 3000 pedestal
+> ...waiting for FAD to be in state 8: Writing Data
 .s FAD_CONTROL 8
+> ...waiting for FAD to be in state 4: Connected
 .s FAD_CONTROL 4
 > ... done
@@ -157 +183 @@
 > switching OFF bias ...
 BIAS_CONTROL/SET_ZERO_VOLTAGE
+> ...waiting for BIAS to be in state 7: VoltageOff
 .s BIAS_CONTROL 7
 > ...done