Reports of 33553
VIS (IX)
tatsuki.washimi - 22:36 Monday 19 January 2026 (36171) Print this report
Comment to MN OL DAMP Filters tuning for ITMX @ 300K (36146)

For some filters, the coefficients were not loaded. So I measured the OLG again (and also tuned again):

L3, L5, T2, T3, V1, Y2, Y3, Y4

 

Now the coefficient differences are not remain.

Images attached to this comment
VIS (EX)
takafumi.ushiba - 15:07 Monday 19 January 2026 (36170) Print this report
Comment to ETMX tripped (36164)

After the modification, I found that ETMX cannot be damped well for a long time when the suspension was kicked due to the lockloss (fig1).
Figure 2 shows the enlarged view of oscillation, which is at 1.67 Hz.
Since 1.67 Hz is close to 2nd mode of yaw and NBDAMP_L5 frequency, I checked both of them.

First, I checked MN_MNOLDAMP_Y loop to confirm the yaw loop is fine.
Figure 3 shows the OLTF of MN_MNOLDAMP_Y loop with Y1 and Y2 NBDAMP, which seems fine.
Note that MNOLDAMP_Y is designed to damp only 1st (0.3Hz) and 2nd (1.7Hz) resonances, so NBDAMP for 3rd (3.1Hz) and MNR(4.1Hz) should be turned on during the measurement to avoid kicking the resonance at high frequency.

Then, I measured OLTF of NBDAMP_L5 (fig4), which damps 1.67Hz longitudinal mode of Type-A tower.
During the measurement, I turned on MN_MNOLDAMP_Y and NBDAMP_{Y1,Y2} to avoid kicking the yaw resonances.
Since the resonant frequency of 2nd mode of yaw and tower longitudinal mode are very close, the yaw resonance is growing up during the measurement if there is no yaw damping.
This might be the reason of large peaking reported in klog36109.
Anyway, the OLTF of NBDAMP_L5 also seems fine, so I modified the ETMX guardian so that NBDAMP_L5 is engaged at LOCK_ACQUISITION state and disengaged at CARM_DOWN state (fig5 and fig6).

Images attached to this comment
MIF (General)
tatsuki.washimi - 13:01 Monday 19 January 2026 (36169) Print this report
Initial alignment

We performed the initial alignment for the Xarm, Yarm, OMC, and PRMI.

Xarm, Yarm, and OMC were done by the Guardian automatically, but for the PRMI, a manual tuning of the PRM pitch by Ushiba-san was necessary.

RECODE_GOOD_VALUES has been done.

VIS (EX)
dan.chen - 10:32 Monday 19 January 2026 (36168) Print this report
Comment to ETMX tripped (36164)

We are checking why the ETMX suspsneion went to TRIPPED stat.
We found that the MN COILOUTF outputs gave high signal just before the state change.
(There was not earthquack observed.)

Images attached to this comment
VIS (EX)
dan.chen - 10:24 Monday 19 January 2026 (36167) Print this report
Comment to ETMX tripped (36164)

I found this L5 filter which is not used in the main pass was set to be ON in ENGAGE_RAPIDDAMP state.
So I comment-outed this line in the guardian.

Then, the ETMX suspension could reach the LOCK_AQUISITION state.

VIS (EX)
dan.chen - 7:53 Monday 19 January 2026 (36166) Print this report
Comment to ETMX tripped (36164)

The error was at the CLOSE_MASTERSWITCH state.
While investigating the system in the situation, I found the NBDAMP L5 was ON.
After manually turing it OFF, the suspension was able to reach the SAFE state.

We need to check why the L5 was turned ON (while the state transition?).

VIS (EX)
dan.chen - 7:04 Monday 19 January 2026 (36165) Print this report
Comment to ETMX tripped (36164)

After that, the suspension can not reach SAFE state as the guardian gives errors saying BF_COILOUTFs have outputs. (fig1)
It seems they have provided the very hight values from around 1/17 20:20. (They are still high values now.)

The TM oplev values are still oscilating.(fig2)

Images attached to this comment
VIS (EX)
dan.chen - 6:54 Monday 19 January 2026 (36164) Print this report
ETMX tripped

The ETMX have tripped around 3:50 on Jan 18.
It seemed MN H3 triged the tripped.
As the value was much lower than the trigged point, I reseted the WD.

There was not any earthquakes on the time?

Images attached to this report
Comments to this report:
dan.chen - 7:04 Monday 19 January 2026 (36165) Print this report

After that, the suspension can not reach SAFE state as the guardian gives errors saying BF_COILOUTFs have outputs. (fig1)
It seems they have provided the very hight values from around 1/17 20:20. (They are still high values now.)

The TM oplev values are still oscilating.(fig2)

Images attached to this comment
dan.chen - 7:53 Monday 19 January 2026 (36166) Print this report

The error was at the CLOSE_MASTERSWITCH state.
While investigating the system in the situation, I found the NBDAMP L5 was ON.
After manually turing it OFF, the suspension was able to reach the SAFE state.

We need to check why the L5 was turned ON (while the state transition?).

dan.chen - 10:24 Monday 19 January 2026 (36167) Print this report

I found this L5 filter which is not used in the main pass was set to be ON in ENGAGE_RAPIDDAMP state.
So I comment-outed this line in the guardian.

Then, the ETMX suspension could reach the LOCK_AQUISITION state.

dan.chen - 10:32 Monday 19 January 2026 (36168) Print this report

We are checking why the ETMX suspsneion went to TRIPPED stat.
We found that the MN COILOUTF outputs gave high signal just before the state change.
(There was not earthquack observed.)

Images attached to this comment
takafumi.ushiba - 15:07 Monday 19 January 2026 (36170) Print this report

After the modification, I found that ETMX cannot be damped well for a long time when the suspension was kicked due to the lockloss (fig1).
Figure 2 shows the enlarged view of oscillation, which is at 1.67 Hz.
Since 1.67 Hz is close to 2nd mode of yaw and NBDAMP_L5 frequency, I checked both of them.

First, I checked MN_MNOLDAMP_Y loop to confirm the yaw loop is fine.
Figure 3 shows the OLTF of MN_MNOLDAMP_Y loop with Y1 and Y2 NBDAMP, which seems fine.
Note that MNOLDAMP_Y is designed to damp only 1st (0.3Hz) and 2nd (1.7Hz) resonances, so NBDAMP for 3rd (3.1Hz) and MNR(4.1Hz) should be turned on during the measurement to avoid kicking the resonance at high frequency.

Then, I measured OLTF of NBDAMP_L5 (fig4), which damps 1.67Hz longitudinal mode of Type-A tower.
During the measurement, I turned on MN_MNOLDAMP_Y and NBDAMP_{Y1,Y2} to avoid kicking the yaw resonances.
Since the resonant frequency of 2nd mode of yaw and tower longitudinal mode are very close, the yaw resonance is growing up during the measurement if there is no yaw damping.
This might be the reason of large peaking reported in klog36109.
Anyway, the OLTF of NBDAMP_L5 also seems fine, so I modified the ETMX guardian so that NBDAMP_L5 is engaged at LOCK_ACQUISITION state and disengaged at CARM_DOWN state (fig5 and fig6).

Images attached to this comment
VIS (SR3)
dan.chen - 6:47 Monday 19 January 2026 (36163) Print this report
Reset the SR3 trip

The SR3 have tripped around 3:50 on Jan 18.
An eathquake was observed around that time.
I reset it as the values monitored by the WD looks nomal now.

(same as SRM: klog36161)

VIS (SRM)
dan.chen - 6:45 Monday 19 January 2026 (36161) Print this report
Reset the SRM trip

The SRM have tripped around 3:50 on Jan 18.
An eathquake was observed around that time.
I reset it as the values monitored by the WD looks nomal now.

Images attached to this report
VIS (IX)
tatsuki.washimi - 13:24 Friday 16 January 2026 (36160) Print this report
Comment to MN OL DAMP Filters tuning for ITMX @ 300K (36146)

About the ~3 Hz oscillation of the yaw during the pitch OLG measurement, Ushiba-san suggested me to apply the NBDAMP Y1 filter (3.13Hz).
I followed his suggestion and confirmed the oscillation was not occurred in the yaw.

Images attached to this comment
VIS (IX)
tatsuki.washimi - 13:11 Friday 16 January 2026 (36158) Print this report
MN OL DAMP Filter (R) OLG for ITMX @ 300K

I measured the OLG of the ITMX MNOLDAMP Filter of roll. It's coherence and phase were looked OK, but the gain was smaller than the reference, about -60dB. [Fig. 1]
At that time, the ROL oplev light was almost only in thee SEG4.

Yokozawa-san went into the mine to perform the centering, and I measured the OLG. Then the result was similer to the reference. [Fig. 2]

Images attached to this report
VIS (IX)
takaaki.yokozawa - 13:09 Friday 16 January 2026 (36159) Print this report
Oplev centering again ITMX MN TILT/ROL
Since the MN oplev was far from center for the ITMX, I performed the oplev centering for MN TILT and ROL QPDs
VIS (IY)
dan.chen - 13:07 Friday 16 January 2026 (36157) Print this report
Comment to ITMY suspension adjustment (36130)

We changed FM5 to FM1 in the T1 loop filter. As a result, the saturation disappeared.
The values of COILOUTF are now slightly larger than they were in O4c. So we decided to keep this situation.
The TF of this T1 loop when using FM1 is the attached figure.

Images attached to this comment
VIS (IY)
takafumi.ushiba - 12:15 Friday 16 January 2026 (36156) Print this report
Comment to ITMY suspension adjustment (36130)

Even if LOCK_ACQUISITION can be kept, this issue should be solved because the output is continuously saturating.
So, some modifications of the NB DAMP T filter (and others if necessary) is necessary.

VIS (IX)
tatsuki.washimi - 12:13 Friday 16 January 2026 (36155) Print this report
OLDAMP Filters OLGs for ITMX @ 300K

[YokozaWashimi]

We measured the OLGs of the OLDAMP filters (P, Y) at the LOCK-AQUISITION state.

Images attached to this report
VIS (IY)
dan.chen - 11:01 Friday 16 January 2026 (36154) Print this report
Comment to ITMY suspension adjustment (36130)

We found the MN COILOUTF values are very high comparing to other suspension.
It can be caused by the loop of NBDAMP T1.
After the adjustment FM5 was used. If we use FM1 for the loop, the COILOUTF values are smaller a little.
FM5 = FM1 + 10dB.

As the suspension could be kept at LOCK_AQUISITION state for long time (>1day), I did not change it.

Images attached to this comment
VIS (IY)
dan.chen - 10:12 Friday 16 January 2026 (36153) Print this report
Comment to ITMY suspension adjustment (36130)

We measured MN OLDAMP filters.

  • Red lines: today
  • Blue lines: 2024/8
  • Green lines: 2025/2

We measured these with LOCK_AQUISITION state.

Images attached to this comment
VIS (EY)
ryutaro.takahashi - 9:22 Friday 16 January 2026 (36152) Print this report
Comment to Offload of F0 GAS (36051)

I offloaded the F0 GAS with the FR.

MIF (General)
takaaki.yokozawa - 9:20 Friday 16 January 2026 (36151) Print this report
PRFPMI RF PRMI 1F locked
The lock of the PRFPMI RF with RPMI 1F lock succeeded, next tuning of the ASC with PRFPMI
Fig.1. - Fig.3. showed the OLTF of the DARM, MICH and PRCL.
Images attached to this report
CRY (General)
nobuhiro.kimura - 8:59 Friday 16 January 2026 (36148) Print this report
Comment to Cryo-cooler Unit Maintenance Work (36134)

[Kimura, Yasui, M. Takahashi, H. Sawada, Ohmae and Yamaguchi]
 On 15 Jan., as part of maintenance work on the cryo-cooler units, the compressor ( Yea ) for the duct shield cryo-cooler unitin the Y-end machine room was replaced.
The removed compressor was packaged for repair.
Preparatory work was performed for replacing the two failed compressors in the center machine room.
Replacement with refurbished compressors is scheduled for next week or later.
 The compressor from the Y-end machine room and the two failed compressors from the center machine room ( X-P53 and Y-P-53 ) are scheduled to be returned to the factory in February.
 The cooling water circulation system in the central machinery room has been temporarily shut down for compressor replacement work.
 Operation is scheduled to resume in early February.

Images attached to this comment
MIF (General)
takaaki.yokozawa - 8:52 Friday 16 January 2026 (36150) Print this report
Measurement of the TM,IM and MN 2 ALSDARM TF
To lock the ALS DARM, I measured the transfer function from TM, IM and MN L to ALS DARM.
Fig.1. showed the TM to ALS DARM.
Compared from July 2024, the gain increased about 0.758 (-259.51718 - (-258.75964) at 5 Hz), so I changed the FM4 of the K1:VIS-ETMX_TM_LOCK_L filter bank
gain(1.255)gain(0.80352)
->
gain(1.255)gain(0.80352)gain(-0.75754)
->
gain(1.3229952)
Fig.2. and Fig.3. showed the IM and MN, respectively, we didn't change the gain for IM and MN (but coherence above the 5 Hz in MN became worse)

Then, we can continuously lock the ALS DARM more than at least 15 min.
Fig.4. showed the OLTF for ALSDARM
Images attached to this report
MIF (General)
takaaki.yokozawa - 6:44 Friday 16 January 2026 (36149) Print this report
Measurement of the OLTF ALS CARM
I measured the CARM OLTF with ALS CARM LOCKED state.
Compared from previous measurement klog35415, the UGF became lower (1.99 kHz -> 1.75 kHz)
I don't know due to lower UGF, the stability of the ALS CARM was too low (continued to lock around 1 min)
After increasing the gain
K1:LSC-CARM_SERVO_IN2GAIN 22 -> 24, the stability became better.

Fig.1. and Fig.2. showed the measured OLTF before and after increasing CARM gain

LSC_LOCK guardian
~L935
from
if ezca['LSC-CARM_SERVO_IN2GAIN'] < 23.5:
CMS_CARM.gain('IN2',ezca['LSC-CARM_SERVO_IN2GAIN']+1)
to
if ezca['LSC-CARM_SERVO_IN2GAIN'] < 23.5:
CMS_CARM.gain('IN2',ezca['LSC-CARM_SERVO_IN2GAIN']+1)
Images attached to this report
DGS (General)
satoru.ikeda - 17:11 Thursday 15 January 2026 (36147) Print this report
Comment to New equipments for ITM front-end (36129)

[YamaT-san, Ikeda]

We created and executed the K1IZ1 model file.
The model was based on K1IX1 and modified to K1IZ1.
All RFM-related components were removed and changed to either terminate or connect to GND.

Not yet registered with the DAQ.
On the maintenance day, add all models to rtsystab and register only the Testpoint for k1iopiz1 with the master.

The following numbers were assigned for DCUID:
58: k1iopiz1
62: k1visitmzt
67: k1visitmzp
77: k1visitmzlsc
118:k1sendbeaconiz

Images attached to this comment
Non-image files attached to this comment
DGS (General)
takahiro.yamamoto - 16:10 Thursday 15 January 2026 (36145) Print this report
Comment to New equipments for ITM front-end (36129)
[Ikeda, YamaT]

We launched up a new V4 computer as K1IZ1.
Now both V4 front-end and a new IO chassis are in the server room to check the stability with short cable connection.
And also, K1IZ1 runs only with PXE/NFS connection to k1boot and without DAQ/RFM connection to another CDS nodes to separate from existing control system.
After checking the stability by short cable connection during next few weeks, a new IO chassis will be moved to IXV or IYV area to check a stability with long (~100-150m) cable connection.
After starting SRM work in March, K1IZ1 will be connected to DAQ/RFM and finally it will be replaced as current ITMX or ITMY until the end of March.

For launching K1IZ1, node information was added to dhcp@k1boot and dns@k1gate.

-----
Rack layout
- An unused old type of IO chassis (S1605837) were moved from U8-11 of C2 rack to U6-9 of C4 rack.
- K1IZ1 front-end and a new type of IO chassis (S2416127) were installed at U29-30 and U8-11 of C2 rack, respectively.
- Spare V4 computer at U1-2 was brought back to SK building for future tests.

Card configuration (same as ITMX and ITMY
- 1 IRIG-B card in front-end
- 1 RFM card in front-end
- 1 4-port Adnaco card in front-end
- 3 ADC boards (S2213882, S2213881, S2113340) in IO chassis
- 3 DAC boards (S2012040, S2517026, S1605727) in IO chassis
- 1 BIO1616 board in IO chassis
- 5 BIO6464 boards in IO chassis
- 1 BO32 board in IO chassis
Search Help
×

Warning

×