But, SR3 cannot be ALIGNED state, I gave up today.
SR3 guardian stopped the isolating state and F0 GAS control cannot be performed stably. Should we set the stable temperature control in center area or some offload?
1. Before the GRY flash trial, I performed the Xarm alignment.
- Tweak the PR3 and PR2 manually to see the TEM00 lights in TMSX GigEs.
- Performed the ADS (IMMT2, PR2 and PR3) using guardian
- Tweak the ITMX and ETMX with checking the TCam image.
- Both GRX_norm and IR_norm value became almost 1 now and Fig.1. showed the TCam image.
- PR2 moved a lot
IMMT2 P : 50.6 -> 50.6
IMMT2 Y : -17.65 -> -17.6
PR2 P : -151.5 -> -178.6
PR2 Y : -85.8 -> -71.6
PR3 P : 9.0 -> 12.2
PR3 Y : -1.0 -> 1.1
ITMX P : 0.5 -> 3.5
ITMX Y : 1.5 -> -5.0
ETMX P : 12.0 -> 17.0
ETMX Y : -11.0 -> -9.6
2. GRY flash trial
- When I requested the ALIGNED state to SR3, SR3 guardian stopped the isolated state and found F0 gas control cannot be succeeded.
- I gave up the GRY flash trial today
[Homework]
- Check the status of the SR3 suspension
- Trial of (relatively) stable temperature control in center area
- GAS offload ITMX(F0)
- SR3 alignment check using TCam and single GRY light
- ETMY alignment check using GRY refl PD
- ITMY alignment check using GRY refl PD flash
- Check other Type-B suspensions for the future MICH lock trial
- Should we set the PDA again for the BS alignment or BS alignment using the IR reflection beam from ITMY?
Anyway, first step for processing the IFO commissioning, the commissioning for the Type-B suspension would be necessary.
Guardian log of SR3 from entering ISOLATING to requesting TWR_DAMPED is as follows.
2024-06-14_23:37:20.588149Z VIS_SR3 new target: ISOLATED
2024-06-14_23:37:20.592504Z VIS_SR3 executing state: ISOLATING (390)
2024-06-14_23:37:20.593021Z VIS_SR3 [ISOLATING.enter]
2024-06-14_23:37:20.803851Z VIS_SR3 [ISOLATING.run] USERMSG 0: Now waiting RMS < 5: F0_DAMP_GAS F1_DAMP_GAS BF_DAMP_GAS IP_DCCTRL_L IP_DCCTRL_T IP_DCCTRL_Y
2024-06-14_23:37:40.903045Z VIS_SR3 [ISOLATING.run] USERMSG 0: Now waiting RMS < 5: F0_DAMP_GAS F1_DAMP_GAS IP_DCCTRL_L IP_DCCTRL_T IP_DCCTRL_Y
2024-06-14_23:37:43.513733Z VIS_SR3 [ISOLATING.run] USERMSG 0: Now waiting RMS < 5: F0_DAMP_GAS IP_DCCTRL_L IP_DCCTRL_T IP_DCCTRL_Y
2024-06-14_23:37:45.148265Z VIS_SR3 [ISOLATING.run] USERMSG 0: Now waiting RMS < 5: F0_DAMP_GAS IP_DCCTRL_L IP_DCCTRL_T
2024-06-14_23:39:17.014395Z VIS_SR3 [ISOLATING.run] USERMSG 0: Now waiting RMS < 5: F0_DAMP_GAS IP_DCCTRL_L
2024-06-14_23:39:43.405557Z VIS_SR3 [ISOLATING.run] USERMSG 0: Now waiting RMS < 5: F0_DAMP_GAS
2024-06-14_23:46:23.209870Z VIS_SR3 REQUEST: TWR_DAMPED
2024-06-14_23:46:23.224804Z VIS_SR3 calculating path: ISOLATING->TWR_DAMPED
As you can see, F0_DAMP_GAS wasn't calmed down. And then, checking error and feedback signals of SR3_F0 tell us F0_GAS_OUT was saturated before error signal reached around 0 (see also Fig.1).
-----
side story
Yesterday, Ushiba-kun enabled gas_notification for suspensions in the corner station. So this saturation should be informed on guardian and slack notification. VIS_params was surely modified. I doubt remaining bugs of gas_notification function at first. But I couldn't find a bug yet. And also, I couldn't find log of guardian load. Ushiba-kun might not load guardian after modifying parameters. If so, after loading guardian code, notifications will be enabled.
Sorry, it is my mistake.
I forgot to LOAD the corresponding guardians after changing the saturation check.
I loaded the guardians, and it seems working corerctly.