40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  PSL  Not logged in ELOG logo
Entry  Tue Mar 6 22:16:15 2018, Craig, DailyProgress, FSS, FSS Fastmon RMS monitors for automatic gain cycling 
    Reply  Wed Mar 7 11:46:07 2018, awade, DailyProgress, FSS, FSS Fastmon RMS monitors for automatic gain cycling 
       Reply  Wed Mar 7 18:31:25 2018, Craig, DailyProgress, FSS, FSS Fastmon RMS monitors for automatic gain cycling 
Message ID: 2120     Entry time: Tue Mar 6 22:16:15 2018     Reply to this: 2122
Author: Craig 
Type: DailyProgress 
Category: FSS 
Subject: FSS Fastmon RMS monitors for automatic gain cycling 

Very often in our lab our FSS boxes "ring", i.e. the EOM and PZT actuators fight each other for control of the laser frequency, instead of working together.  If the EOM actuator rails, the PZT comes stomping in trying to lock high frequency laser frequency noise, but the EOM comes back in and says, "no, it's my job", but the PZT is all like "obviously you can't do your job cause you're not strong enough", which really only makes the EOM angry, causing rail-to-rail actuation jumps and high, nonlinear noise in our FSS loops.  This is bad for our PLL autolocker, as the high noise hurts the PLL control signal and eventually causes it to lose the beatnote, and obviously bad for the beatnote ASD itself, which we are monitoring at all times on our webpage.
So today I created rmsMonitor.py, a python script which monitors the RMS of the FSS Fastmon voltage, the PZT control signal.  If the Fastmon RMS ever exceeds 250 mV, rmsMonitor.py will call awade's gaincycle.py on the offending FSS box, which brings both Common and Fast Gain values to their lowest setting, then steadily ramps them back up to where they were in a nice way such that ringing won't start up again.  In this way we can automatically eliminate ringing whenever it starts.


rmsMonitor.py lives in ~/Git/cit_ctnlab/ctn_scripts/,  and has two associated .ini files, RMSMonitor_North.ini and RMSMonitor_South.ini.  Inside the .ini files is defined the Fastmon path channel name, i.e. C3:PSL-NCAV_FSS_FASTMON for the north path, and the max rms limit, which is currently 250 mV for both paths.

To run this script on our North path, call
$ python rmsMonitor.py RMSMonitor_North.ini &
Every two seconds, the script should print out something like
C3:PSL-NCAV_FSS_FASTMON rms = 0.0647327284305 V
which is the channel name and the rms calculated for that channel in that two seconds.  Again, if rms is ever above 250 mV, it triggers gaincycle.py for that path and eliminates ringing.


These scripts are perpetually running in tmux sessions named RMSNorth and RMSSouth on acromag1.  To access the north tmux session, log onto acromag1 and run  $ tmux attach -t RMSNorth
These scripts will need to be turned off when debugging persistent FSS ringing.

ELOG V3.1.3-