40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  40m Log  Not logged in ELOG logo
Entry  Mon Oct 19 11:20:34 2015, gautam, Update, VAC, RGA scan reset RGAscan_151019.png
    Reply  Thu Apr 21 15:12:38 2016, Steve, Update, VAC, RGA is not working 
       Reply  Wed May 11 16:39:01 2016, ericq, Update, VAC, c0rga alive, output wonky 
          Reply  Thu May 12 14:29:58 2016, gautam, Update, VAC, RGA back up and running RGAscan_12May2016.png
             Reply  Tue May 17 14:46:51 2016, Steve, Update, VAC, RGA scan at day 595 RGAscan595d.pngpd78-560Hz-d600.png
                Reply  Mon Aug 21 14:53:32 2017, gautam, Update, VAC, RGA reset 
Message ID: 11697     Entry time: Mon Oct 19 11:20:34 2015     Reply to this: 12086
Author: gautam 
Type: Update 
Category: VAC 
Subject: RGA scan reset 

Steve pointed out that in the aftermath of the Nitrogen running out a couple of times last week, the RGA had shut itself off thinking that there was a leak and so it was not performing the scheduled scans once a day. So the data files from the scheduled scans were empty in the /opt/rtcds/caltech/c1/scripts/RGA/logs directory. The wiki page for getting it up and running again is up-to-date, but the script RGAset.py did not exist on the c0rga machine, which the RGA is communicating with via serial port. I copied over the script RGAset.py from rossa to c0rga and ran the script on that machine - but the error flags it returned were not all 0 (indicating some error according to the manual) - so I edited the script to send just the initialize command ('IN0') and commented out the other commands, after which I got error flags which were all 0. After this, I ran a manual scan using 'RGAlogger.py', and it appears that the RGA is now able to take scans again - I'm attaching a plot of the scan results. We've saved this scan as a reference to compare against after a few days. 

Attachment 1: RGAscan_151019.png  25 kB  | Hide | Hide all
RGAscan_151019.png
ELOG V3.1.3-