Difference between revisions of "Flux-loop reset per detector"

From MCEWiki
Line 1: Line 1:
 
The flux-loop servo can be reset on a per-detector basis without having to stop the data-acquistion in progress. This is particulary useful in cases that only certain detectors are hit by cosmic rays.
 
The flux-loop servo can be reset on a per-detector basis without having to stop the data-acquistion in progress. This is particulary useful in cases that only certain detectors are hit by cosmic rays.
  
To schedule a reset, a per-detector flag can be set using '''servo_rst_colX''' parameter and then the '''servo_rst_arm''' has to be set to 1.
+
To schedule a reset, a per-detector flag can be set using {{param|rc|servo_rst_col0|servo_rst_col''#''}} parameter and then the {{param|rc|servo_rst_arm}} has to be set to 1.
  
 
The reset involves setting the integral-term of the calculated feedback to 0, resetting the corresponding flux-jump counter to 0, and resetting the corresponding [[FSFB_Clamping_Command|'''integral_clamp''']] flag.
 
The reset involves setting the integral-term of the calculated feedback to 0, resetting the corresponding flux-jump counter to 0, and resetting the corresponding [[FSFB_Clamping_Command|'''integral_clamp''']] flag.

Revision as of 20:01, 9 September 2014

The flux-loop servo can be reset on a per-detector basis without having to stop the data-acquistion in progress. This is particulary useful in cases that only certain detectors are hit by cosmic rays.

To schedule a reset, a per-detector flag can be set using servo_rst_col# parameter and then the servo_rst_arm has to be set to 1.

The reset involves setting the integral-term of the calculated feedback to 0, resetting the corresponding flux-jump counter to 0, and resetting the corresponding integral_clamp flag.

For example to schedule a servo reset on col3, row 4, and col5, row 2:

wb rc1 servo_rst_col3 0 0 0 0 1
wb rc1 servo_rst_col5 0 0 1 0 0
wb rc1 servo_rst_arm 1