Reports 1-1 of 1 Clear search Modify search
DGS (General)
takahiro.yamamoto - 18:11 Thursday 19 March 2026 (36625) Print this report
Deployment of V2 IO-chassis and the front-end computer for ITMY
[Ikeda, Nakagaki, YamaT]

This is a same work as klog#36572 for ITMX.
V1 IO chassis (S1807864) in IYV1 rack was replaced as V2 one (S2416129).
ADC/DAC noise check still remains, but replacing IO chassis itself was finished.

-----
As the same procedure in ITMX case, V2 IO chassis was launched at outside of IYV1 rack without connecting any circuit. This was a connection test of a new MTP fiber cable between the mine server room and the IYV room. At that time, the front-end was newly installed at U27-28 of C2 rack (but still named as K1IZ1) and K1IY1 at U18-19 of ICV rack was alive with the old configuration. Thanks to the fiber cabling and labeling work yesterday, it can be done smoothly and there was no issue on the connection test.

After the connection test, we stopped both K1IZ1 in C2 rack and K1IY1 in ICV rack, removed V1 IO chassis from U6-9 of IYV1 rack, installed V2 IO chassis to there, and plugged all cables to V2 IO chassis. (In the ITMX case, we connected V2 IO chassis at outside of the rack with circuits at first, but we concluded this procedure can be skipped in the yesterday's experience.) And then, V2 IO chassis was launched with the new K1IY1 in C2 rack which was renamed from K1IZ1. ITMY models were able to be launched without any timing and PCIe activation errors.

We haven't yet measured ADC/DAC noise with new hardware configuration. So replacement work isn't fully completed. On the other hand, noisy channel issue will be mitigated by replacing ADC/DAC board not IO chassis, so we can say replacing IO chassis itself was finished. We plan to measure the ADC/DAC noise in the new configuration on next Tuesday.

V1 IO chassis and the old K1IY1 front-end are still left in IYV room and ICV rack, respectively. After seeing weekend situation, we will return them back to Mozumi for the next replacement work.
Comments to this report:
takahiro.yamamoto - 17:46 Monday 23 March 2026 (36633) Print this report
[Ushiba, Ikeda, Nakagaki, YamaT]

Ushiba-kun found FLDACC loop couldn't be engaged though ITMY was achieved ISOLATED state. IP, GAS and BF loops seemed to work so ADC0 including IP, GAS, BF and FLDACC sensors and DAC0 including IP, GAS, and BF actuators surely worked well. On the other hand, even the DAC output for FLDACC (DAC2) increased, any motion couldn't be found on FLDACC sensors.

We didn't touch DB9 cables for replacing I/O chassis (klog#36625), so we was able to guess a wrong cabling of SCSI cables as the most likely cause soon. So we monitored MNIMV sensors (if our guess is correct, FLDACC actuators had to be swapped to MNIMV actuators) while the DAC output was increased. Then, payload sensors showed some motion.

We entered the mine for fixing swapped SCSI cables for DAC1 and DAC2. Finally, FLDACC loop worked fine after fixing swapped cables. When we replaced the IO chassis, we connected SCSI cables to ADC/DAC boards attached the new IO chassis based on the original tags attached the SCSI cables as "DAC0", "DAC1", and "DAC2". But these tags were faking actual connection. Even if the original tag looks correct, it seems we shouldn't trust it and should re-make new tags. Anyway, we removed original wrong tags and attached new correct tags for those SCSI cables.
Search Help
×

Warning

×