I offloaded the F3 and BF GAS filters with the FRs after closing the EXC.
I offloaded the F3 and BF GAS filters with the FRs after closing the EXC.
The health check was performed again after solving the low-coherence problem in BF GAS. Compared with the reference, the coupling from Y to T and R in IM changed. Other TFs look healthy.
[Moriwaki, Aoumi, Shimode, Hirose]
We checked the existing beam shutter connections in the PSL room and around the OMCDCPD in preparation for the future installation of the Fast Beam Shutter.
OMC DC Driver ["Zsw Ctrl"] (S2416233)→ (D-sub 9-pin cable)→ Binary In/Out Converter (S1910321)["Ch00-07"->"Ch24"]→ (BNC cable)→ OMC Piezo Driver [Shutter Trigger](S1910872)
For the future installation of the Fast Beam Shutter, we are considering disconnecting the D-sub 9-pin cable currently connected between OMC DC Driver ["Zsw Ctrl"] and the Binary In/Out Converter, and connecting the BI/BO of the Fast Beam Shutter directly to OMC DC Driver ["Zsw Ctrl"] instead.
The current connector of the Fast Beam Shutter circuit is a D-sub 25-pin connector, while the output from OMC DC Driver ["Zsw Ctrl"] uses a D-sub 9-pin connector.
Therefore, we are considering changing the connector of the Fast Beam Shutter circuit from D-sub 25-pin to D-sub 9-pin.
Before making this modification, the pin assignments and electrical interface (signal levels, BI/BO configuration, etc.) need to be checked to confirm compatibility with OMC DC Driver ["Zsw Ctrl"].
I offloaded the F0 GAS with the FR.
I offloaded the F0 GAS with the FR.
Though I tried to offload the F0 GAS with the FR, the FR didn't work well. So I changed the setpoint for the F0 GAS from 4250 to 4230 temporarily to avoid saturation.
To test the latest version of the DetChar tools, I checked the Segment files automatically generated using HTCondor and compared them with those generated on k1det1.
The files from August 19 and 20 were not consistent. The likely cause was that the HTCondor job ran at 0, 15, 30, and 45 minutes past each hour, before all data for each 15-minute period were available.
I changed the schedule to 3, 18, 33, and 48 minutes past each hour, following the crontab configuration on k1det1.
I will check the results again after a few days.
[Kimura]
I found the operational analysis report (in Japanese) for this TMP, which was conducted in October 2021, so I am uploading it.
This TMP had experienced the same anomaly in October 2021 as it did this time.
[Kimura, Yasui and Uchiyama ]
On the afternoon of Oct. 5, when we checked the fault history using the TMP’s external controller, the attached error log was displayed.
Based on a comparison between the internal clock and my watch, we estimate that this error occurred around 8:30 a.m. on Oct. 2.
On Oct. 6, we plan to extract the operation history stored in the TMP and perform a fault analysis.
(Okabe, Machida, Miyakawa)
We checked the status of the ISS after recovery from the power outage. Due to the outage, the protection circuit for abnormal operation of the main PD power supply had been triggered, cutting off power to the PD. We reset the protection circuit and restored power to the PD, and confirmed that the PD responded to the incident light.
We then set the frequency and output level of the LO supplied to the AOM driver. According to the records from the University of Toyama, the driver should be supplied with an 80 MHz signal at 10 dBm. Since a 1/2 power divider is connected to the LO, this corresponds to an LO setting of 13 dBm, i.e., 1.0 Vrms or 2.825 Vpp into 50 Ω. However, with this setting, approximately 20% of the laser power was lost. We therefore reduced the power to 1/8, i.e., 1 dBm at the driver. With the 1/2 power divider connected to the LO, this corresponds to an LO setting of 4 dBm, i.e., 0.354 Vrms or 1 Vpp into 50 Ω. With this setting, the laser power loss was reduced to approximately 5%, which is consistent with the previous operating condition.
We then brought the ISS Guardian to the Locked state and confirmed that the servo engaged without any problems and that the boost was also turned on.
Regarding the noise performance, we confirmed that both the in-loop and out-of-loop noise levels remained nearly unchanged from their previous levels (Fig.1).
We also measured the OLTF and confirmed that the UGF was approximately 56 kHz, with a phase margin of 21 degrees (Fig.2).
I compared the BF GAS TFs measured in the different executions below.
The COILOUTF output in the third case saturated (over +/- 32768) during the actuation (Fig. 5). The COILOUTF output in the first health check did not saturate (Fig. 6). The low coherence was not due to the saturated actuation.
Since the data for the IP TFs were not recorded in the last health check, I measured the IP TFs again. The resonant frequency of the T direction shifted from 62 mHz to 66 mHz.
Since the data for the IP TFs were not recorded in the last health check, I measured the IP TFs again. The measured TFs look healthy.
I checked the previous actuation amplitude in the health check. 10000 amplitude and a 20 Hz frequency range were used in the health check in 2024. I measured the BF GAS TF again with 10000 amplitude but a 5 Hz range. The measured TF had good coherence (Fig. 1). There is a steep peak at 11.3Hz in the TFs. Fig. 2 shows the spectra of the BF/SF GAS and the IM V. There is a steep peak at 13.6Hz in the BF/SF GAS but no peak in the IM V. The IM V sensor should show almost the same spectrum as the BF GAS one with a low noise floor. The peak in the BF GAS spectrum does not seem to be a mechanical resonance.
By the way, the whitening filters in the COILOUTF increase the gain by 40dB at > 10Hz. Therefore, the COILOUTF output sometimes saturates (over +/- 32768) during the 10000-counts actuation at 20Hz range.
Today I finished the surface seismic measurement.
The batterlies were already empty and the data taking was stopped on September 22th.
Since the Y-axis signal looks to be strange, I checked the connector cables. Finaly I founf the cut pin and I have fixed it.
Also, we found that both side of heat links between the cooling bar and the heat-link-vibration-isolation-system touched to the inner shield, so we repaired them.
Regarding duct shield, we carried out visual inspection and found no unexpected connections.