40m QIL Cryo_Lab CTN SUS_Lab TCS_Lab OMC_Lab CRIME_Lab FEA ENG_Labs OptContFac Mariner WBEEShop
  TCS elog, Page 6 of 6  Not logged in ELOG logo
New entries since:Wed Dec 31 16:00:00 1969
ID Date Author Typedown Category Subject
  212   Wed May 30 18:50:05 2018 awadeComputingDAQRebooted fb4

Time was still off by nine days as of yesterday.  I tried rebooting remotely to see if time would correct to system clock.  It didn't and fb4 hung.

Just manually restarted the box.  Now dataviewer is showing a 'Time Now'  of 5 Jan 1980.   

Not sure how to set the frame builder clock time. Ultimately the best solution is to have ADC cards but can we find a hack for now? Is it possible to run a cron script it to reset time to the computer time?

 

 

 

Quote:

The framebuilder on FB4 thinks the current time is 26-Jan-2018 6:18AM UTC. The date command on FB4 yields the correct date and time (5-Feb-2018 15:17 PST).

There is a major error with the framebuilder clock.

 

  213   Wed May 30 18:59:49 2018 awadeComputingDAQFB4 ip address has changed

Maybe you've resolved this now. I moved the DHCP allocation to 10.0.1.160 and above around that time because a bunch of misc devices were starting to populate the dynamically allocated IP space around there.  I'd say FB4 was not setup with a manual IP at the time.

 

Quote:

We've had trouble logging into FB4. I access the computer directly in the AWC lab and found that the IP address had changed from 10.0.1.156 to 10.0.1.161.

I'm not sure how this happened. It's possible that the IP address is not set to a static value and FB4 was rebooted. I'm not familar with Debian so I don't know where to look to find whether the IP address is static or not.

The DAQD is still running.

 

  221   Thu Aug 16 11:52:27 2018 AidanComputingDAQAdded AWC thermocouple reader back to acromag1
  • Thermcouple reader is plugged into an Acromag ADC (10.0.1.55)
  • acromag1 is now reading this in:
    • ~/modbus/iocBoot/iocTest/test_acromag.cmd (contains ip address of ADC)
    • ~/modbus/db/TEMPMONCHANS.db (contains the EPICS channel definitions and calibration of thermocouple reader)
  • C4:AWC-TEMPMON_C (output channel)

Restored work done in http://nodus.ligo.caltech.edu:8080/TCS_Lab/201

 

 

 

  222   Wed Oct 17 16:17:45 2018 awade, AidanComputingDAQAdded AWC thermocouple reader back to acromag1

Acromag IOC process was removed from PSL lab acromag1 computer a few months ago.  Aidan needs them again but it would be better if it were run from TCS lab computers.

An instance of the modbus IOC is now running on tcs-ws within a docker container.  Docker is named tcslabioc.  Configuration files are located in ~/modbus.  Instructions on how to use the docker are located in ATF:2249.  To install docker see google.

To set up the specific instance in the TCS lab run

>sudo docker run -dt --name tcslabioc -v /home/controls/modbus/test_acromag.cmd:/home/modbus/IOCStart.cmd -v /home/controls/modbus:/home/modbus -p 5064:5064 -p 5065:5065 -p 5064:5064/udp -p 5065:5065/udp andrewwade/modbusepicsdocker 

Then whenever you want to stop, run:

> sudo docker stop tcslabioc

or to restart run

>sudo docker restart tcslabioc. 

So if you update the .cmd or .db files just run the restart command above and the channels should automatically update when it reboots. For other cleanup and control commands see docker documentation.  It can also be configured to keep alive on system reboot.

The cmd and db files are included below in the attachments for reference. 

 

Quote:
  • Thermcouple reader is plugged into an Acromag ADC (10.0.1.55)
  • acromag1 is now reading this in:
    • ~/modbus/iocBoot/iocTest/test_acromag.cmd (contains ip address of ADC)
    • ~/modbus/db/TEMPMONCHANS.db (contains the EPICS channel definitions and calibration of thermocouple reader)
  • C4:AWC-TEMPMON_C (output channel)

Restored work done in http://nodus.ligo.caltech.edu:8080/TCS_Lab/201

 

 

 

 

Attachment 1: TCSIOCFILS.tar.gz
  224   Tue Dec 4 16:57:08 2018 AidanComputingHartmann sensorUpdated GIT version of HWS code

I changed the HWS code to the new git.ligo HWS version.

  • Object files are in ~/hws
  • scripts are in ~/hws-server
  • utilities are still in old git repo moved to ~/.HWS_code_temporary_home

I've set up some symbolic links to these directories to mimic the old directory structure, so ..

  • ~/pyHWS links to new object file directory
  • ~/pyHWS/scripts lnks to new scripts directory
  • ~/pyHWS/utilities links to old utilities directory
ELOG V3.1.3-