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
 List  |  Find  |  Login  |  Help 
Entry  Sun Dec 7 13:11:57 2014, manasa, Summary, General, Frequency Offset Locking - To Do List FOLtodolist.pdf
    Reply  Mon Dec 8 15:54:39 2014, manasa, Summary, General, Dec 8 - Check Frequency Counter module 
       Reply  Mon Dec 8 20:53:51 2014, diego, Summary, General, Dec 8 - Check Frequency Counter module 
          Reply  Tue Dec 9 16:06:46 2014, diego, Summary, General, Dec 8 - Check Frequency Counter module 
    Reply  Tue Dec 9 00:30:27 2014, manasa, Summary, General, Dec 9 - Elaborate to do list FOL_FiberChassis.pdf
       Reply  Tue Dec 9 16:07:16 2014, manasa, Summary, General, Dec 9 - FC module and fiber chassis FCmodule.png
    Reply  Wed Dec 10 16:12:29 2014, manasa, Summary, General, Dec 10 - PSL table FiberMod_front.jpgFOL_fiber.jpg
       Reply  Thu Dec 11 12:50:12 2014, manasa, Summary, General, PSL table optical layout 
          Reply  Thu Dec 11 23:34:06 2014, manasa, Summary, General, PSL table optical layout 
             Reply  Fri Dec 12 02:30:25 2014, Jenne, Summary, General, PSL table optical layout 
    Reply  Fri Dec 12 14:38:39 2014, manasa, Summary, General, Frequency Offset Locking - To Do List (Revised) FOLtodolist.pdf
       Reply  Fri Dec 12 15:19:04 2014, manasa, Summary, General, Dec 12 - PSL table PSLtoFiber.pngPSLfiberChassis.pngPSLfiberChassis.png
       Reply  Wed Dec 17 11:57:56 2014, manasa, Summary, General, Y arm optical layout 58.png
Message ID: 10770     Entry time: Tue Dec 9 16:06:46 2014     In reply to: 10766
Author: diego 
Type: Summary 
Category: General 
Subject: Dec 8 - Check Frequency Counter module 

Quote:

Quote:

Quote:

Attached is the timeline for Frequency Offset Locking related activities. All activities will be done mostly in morning and early afternoon hours.

[Diego, Manasa]

We looked into the configuration and settings that the frequency counters (FC) and Domenica (the R pi to which the FCs talk to) were left at . After poking around for a few hours, we were able to readout the FC output and see it on StripTool as well.

We have made a list of modifications that should be done on Domenica and to the readout scripts to make the FC module automated and user-friendly.

I will prepare a user manual that will go on the wiki once these changes are made.

 

 I started working on the scripts/FOL directory (I did a backup before tampering around!):

  • I still need to make some serious polishing in the folder, and into the Raspberry Pi itself, in order to have a clean and understandable environment;
  • as of now, I created an single armFC.c program, which takes as arguments the device (/dev/hidraw0 for the X arm, and /dev/hidraw1 for the Y arm) and the value to write into the frequency counter (0x3 for initialization and 0x2 for actual use); hence, no more need for recompilation!
  • I improved the codetorun.py script (and gave the fellow a proper name, epics_channels.py) which handles the initialization AND the availability of the channels;
  • On the Raspberry Pi, I created two init scripts, /etc/init.d/epics_server.sh and /etc/init.d/epics_channels.sh, which start at the end of the boot process with default runlevels; the former starts the softIOc process (epics itself), while the latter executes the constantly running epics_channels.py script; as they are services, they can be started/stopped with the usual sudo /etc/init.d/NAME start|stop|restart

 

As a result, as soon as the Raspberry Pi completes its boot process, the two beatnote channels are immediately available.

 

 OUTDATED: see elog 10779

 

 Update and corrections:

 

  • I forgot to log that I added a udev rule in /etc/udev/rules.d/98-hidraw-permissions.rules in order to let the controls user access the devices without having to sudo all the time;
  • I updated the ~/.bashrc and /opt/epics/epics-euser-env.sh files to fix syntax errors and add some aliases we usually use;
  • since /etc/init.d/ doesn't support automatic respawn of processes, I purged the two scripts I did yesterday and added two lines to /etc/inittab. This works just as fine (I tried a couple of reboots to verify that) and the two processes now respawn automatically even if killed (and, I assume, if they die for any other reason)
  • Another thing I forgot: for the time being, during the cleanup, the Raspberry Pi works on the network share script directory. Once cleaning is done and everything is fixed, everything will run locally on the RPi, and the scripts/FOL directory on chiara will be used as backup/repository.
ELOG V3.1.3-