Displaying report 1-1 of 1.
Reports until 23:08, Tuesday 22 September 2026
H1 IOO
jennifer.wright@LIGO.ORG - posted 23:08, Tuesday 22 September 2026 - last comment - 23:24, Tuesday 22 September 2026(92021)
JAC GUARDIAN problems

Summary: guardian change messed up servo controller, will trial changes this weekend, have now backed out problematic part.

I changed the lines in the JAC temperature servo add in the PZT fb signal to the JAC temperature servo error point during maintenance.

I thought that I had it setup so the heater control error point gets changed as the JAC length changes, unfortunately I had a mistake in the code so this offset was only being added to the temperature servo once when the servo was switched on.

After updating it, this caused overshoot in the JAC temperature which kept unlocking it.

I have taken out these lines (line 46 in JAC_HEATER.py) so now the servo just tracks the set temperature of the heater.

I will leave this to settle overnight.

As part of our efforts to keep the JAC servo locked we had put the power output on the JAC heater to 0, I have turned this back to its nominal at 3W, and the set temperature back to its nominal at 25.4 degrees C.

I will also do another test at the weekend where I put the set temp up further to 30 degrees. The PMC has a set temperature of 32 degrees. While this is in air and so benefots from air cooling, a larger headroom in set temperature would make our control loop faster at cooling.

Comments related to this report
jennifer.wright@LIGO.ORG - 23:24, Tuesday 22 September 2026 (92022)

I took the JAC to DOWN till the temperature settles and then realised the IMC guardian can't be taken to DOWN while the JAC is unlocked. It just stayed in 'FAULT'. Not sure why.

I had to relock the JAC to move the IMC to DOWN then offline. I will leave them both unlocked for the night.

Displaying report 1-1 of 1.