Reports until 17:36, Wednesday 03 August 2016
H1 AOS
jeffrey.kissel@LIGO.ORG - posted 17:36, Wednesday 03 August 2016 - last comment - 17:57, Wednesday 03 August 2016(28858)
H1SUSETMs Modified to Have Individual Coil Driver Switching; ITMs will be done tomorrow.
J. Kissel
ECR E1500045
FRS 6014
WP 6051

I've begun the roll out of individual state switch-ability for the PUM / L2 coil drivers. This is essentially complete for the ETMs (just a few more aesthetic MEDM screen changes are needed). I've confirmed all functionality behaves as expected. I've reconciled the SDF "down" snap before hand, and made sure that all settings were restored, including initializing/accepting the new EPICs records that come with this update.

Though the model changes have been made to the simulink model for the ITMs (because the ITMs and ETMs are using a generic L2 stage library part), they have not yet been compiled or installed, and MEDM screens have not been updated (because they now have separate MEDM infrastructure [see LHO aLOG 27641], generic changes to all QUADs like this takes twice as long). Stay tuned for more details and screenshot in tomorrow's "it's complete" aLOG.

Still to Do:
- Edit EUL2OSEM MEDM screens to support the ramping matrix on ETMs
- Compile / Install / Restart ITM models (with accompanying DAQ restart)
- Edit ITM QUAD OVERVIEW and BIO screens for all the same changes as I've done to the ETM QUAD overview
- commit everything to the SVN
- Make sure that the ISC_LOCK guardian hits the "LOAD MATRIX" button on the PUMs in the DOWN state.
- Integrate new "three wheel motion" coil driver switching into the ISC_LOCK guardian in the COIL_DRIVERS state
Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 17:57, Wednesday 03 August 2016 (28860)

We had a strange issue with the h1susetmx restart. The H1SUSETMX.ini file was changed at 17:08, h1susetmx was restarted at 17:10 and the DAQ was restarted at 17:12. Yet the DAQ status for h1susetmx ended up as 0x2000 (ini file check sum mismatch). A restart of h1susetmx fixed the problem. With so much time between restarts this does not look like a slow NFS file issue.