I discovered this morning that my new HWS camera control code, which only talks to the camera when it needs to turn the camera on or off, was locking up in its caget of the IFO lock status. The last change was for the lock status function to return both the caget call status and the ifo_lock_state.
I reverted the code back to the previous version, and it is now running correctly on h1hwsex, h1hwsey and h1hwsmsr1 but for an unknown reason is still locking up on caget on h1hwsmsr. When I run the caget command on h1hwsmsr's command line it works. Investigation is continuing.
Note due to this bug HWS ITMX camera was mistakingly left ON overnight until I manually turned it OFF at 08:33 PST this morning.
code is running again on h1hwsmsr.
Tagging DetChar: the ITMX HWS camera was on at 5Hz (comb visible in H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ) from 2024/01/09 20:20UTC to 2024/01/11 16:33UTC. Thank you Dave for finding this and turning off.
Today I checked on the status of these cameras. IX and EX were working as expected and Dave's code is working well on all of them.
The HWS code on EY had crashed (or never correctly started) with a segmentation fault but started again fine.
ITMY was failing even though Dave's code successfully turned the camera on. Couldn't restart code, had error: "HWS.HS_Camera.AcquisitionFailure: Image acquisition failed: 1 timeouts and 1 overruns occurred." in state 2B. Even though it successfully connected to the camera. I think we see similar errors when we are trying to stream images and take data at the same time. I tried re-initing the camera but it didn't change. Streaming images gave pixelated noise, no image. This code has properly been working for the last weeks... Unsure of the issue.