Reports 1-1 of 1 Clear search Modify search
VIS (PR3)
kenta.tanaka - 22:05 Tuesday 02 June 2026 (37007) Print this report
Since PR3 H3 OSEM has large glitch, PR3 local alignment control seems to be kicked

Ushiba, Takano, Fujimoto, Hirose, Tanaka

## Abstract

We found that PR3 IM OSEM H3 has large gilitch frequently. This glitch shakes PR3 largely, more than 10 urads and disturbs PRMI/SRMI lock.

## Details

As reported in klog36978, PR3 moved largely again during today's commissioning.

First, GAS LVDT signals seem to become glitchy at this moment. We turned off only GAS controls and monitored the local sensor signals. Although GAS LVDT signal seems to be not changed, PR3 moved largely (fig.1). So GASs are not gulity.

Second, We turned off TM OLDAMP controls after restoring GAS controls. Similarly, PR3 moved largely (fig.2). So, TM oplev seems to be innocent.

Third, we turned off IM DAMP. Actually, we requested PR3 guardian to be the PAY_FLAOT state. Then, we found that IM OSEM H3 has large glitch, ~10 cnts? in the view from K1:VIS-PR3_IM_OSEMINF_H3_OUT (fig.3). This time, TM oplev seems to be stable(fig.4). IM OSEM H3 seems to be used for IM DAMP T and Y. We turned on the PAYLOAD controls (actually we requested the guardian to be LOCK_ACQUISITION) and then we turned off the IM DAMP T and Y. In this state, TM OLDAMP started oscillate 1.15 Hz. Except for this 1.15 Hz oscillation, PR3 seems not to move largely (fig.5). 

Finally, we closed the laser shutter in order to confime whether this glitches are caused by the scattered light from IFO. The glitch is still in the OSEM signals even though the laser shutter was closed (K1:PSL-BEAM_SHUTTER = 0) (fig.6). This indicates this glitch comes from OSEM itself.

According to OSEM2EUL matrix, the coefficient from DGS cnts to urad? in Y direction is 5.8. So This 10 cnts glitch is relavant with ~58 urad.  

OSEM giltch seems to appear in only one direction, that is in negative direction in K1:VIS-PR3_IM_OSEMINF_H3_OUT. we suspect that somethin ex. OSEM LED intensity? or LED current? gets weak.

We left PR3 in the PAY_FLOAT state overnight to check how frequent this glitch occurrs.

Images attached to this report
Comments to this report:
kenta.tanaka - 9:46 Wednesday 03 June 2026 (37013) Print this report

Fig.1 is OSEM signal timeseries in last night. The interval between cursors shows the duration when PR3 was in PAY_FLOAT state. As you can see, There seems to be the noisy timing and the quiet timing. 

In the noisy timing, the glitch occurres per 1-2 mins (fig.2). If this becomes noisy at once, the situation continues several hours.  On the other hands, any glitch seems to not occured over several hours if it is in quiet timing (fig.3).

 

Images attached to this comment
satoru.ikeda - 15:02 Wednesday 03 June 2026 (37014) Print this report

(Remote) R. Takahashi, Nakagaki, Ikeda

This work is related to K-Log #37013.
We replaced the PR3 satellite box.

[Details]
1. We measured the forward voltage at the end of the conversion cable connected to the feedthrough.
   There was no significant change in the values, and all measurements were normal.

IM H3

  Before Today
1-6 PD 0.524V 0.529V
3-8 LED 1.065V 1.065V

(Reference value)IM H1

  Before Today
1-6 PD 0.524V 0.527V
3-8 LED 1.063V 1.063V

2. Next, we replaced the satellite box.
We placed the new satellite box (S1604893) on top of the old satellite box (S1504430) and reconnected the DSUB cables from the old box to the new one.
H2 and H3 were connected to the replacement satellite box.Fig.1
 

Images attached to this comment
Non-image files attached to this comment
takashi.uchiyama - 16:53 Wednesday 03 June 2026 (37016) Print this report
2026/06/03

Uchiyama

I looked for an OSEM unit around SRM and found something similar in a plastic box on the metal shelf on the +X side of SR3. It was in an unopened plastic bag.

I wiped the surface of the plastic bag and put it in the desiccator near OMC.
Images attached to this comment
Search Help
×

Warning

×