patrick.thomas@LIGO.ORG - posted 15:34, Wednesday 30 April 2025 - last comment - 17:10, Wednesday 30 April 2025(84208)
Restarted h0vaclx TwinCAT system, updated high voltage trip points
WP 12505. Patrick, Gerardo I tried various restarts of the Beckhoff PLC on h0vaclx, but none of them changed the error on the PT110 gauge. I did notice an additional diagnosis of the error, which is that the status of the EtherCAT ports is abnormal, which I think is an indication that something is not right with the connection of the gauge to the h0vaclx EtherCAT network. Gerardo went out to reseat the cable and look for anything odd about it. I went through and checked the relay trip point levels for each of the gauges on h0vaclx. I found PT110, PT180 and PT170 set to 1E-5 and changed them to 5E-5. PT132 was already at 5E-5. The other gauges do not have the trip points enabled. PT110 1E-5 -> 5E-5 PT140 not enabled PT180 1E-5 -> 5E-5 PT170 1E-5 -> 5E-5 PT132 5E-5 PT193 not enabled PT192 not enabled PT191 not enabled
Images attached to this report
Comments related to this report
I used the vacuum SDF safe.snap file to restore CP2's PID settings. To speed this up in the future I wrote a script to do this, the script should be ran on a machine with write access to the vacuum controls IOCs.
/ligo/home/vacuum/burt_restore_h0vaclx.bsh
cp /opt/rtcds/userapps/release/cds/h1/burtfiles/h1vacuumsdf/h1vacuumsdf_safe.snap /tmp/h1vacuumsdf_safe.snap
cat /tmp/h1vacuumsdf_safe.snap|grep "^H0:VAC-LX_"|awk '{print "caput ",$1,$3}' > /tmp/h0vaclx
while read -r i;do
${i}
done < /tmp/h0vaclx
Error is fixed, all we had to do was connect the Ethernet cable to correct port, yes somehow I managed to connect it on the wrong port, but the odd part is that we had a valid pressure signal, except for the error noted by Patrick.
For future reference, specifically, the correct port (in vs. out) on the gauge itself.