Reports 1-1 of 1 Clear search Modify search
DGS (General)
takahiro.yamamoto - 16:21 Friday 13 March 2026 (36572) Print this report
Deployment of V2 IO-chassis and the front-end computer for ITMX
[Ikeda, Nakagaki, YamaT]

Abstract

IO-chassis and the front-end computer for ITMX were replaced to new hardwares.
Though a simple cabling check by DAC output was able to be done, we haven't checked LOCK_ACQUISITION state is reachable because of a large change in the room temperature of IXV.
These check can be done in tonight, weekend, or next Monday.

Details

A pair of V2 IO chassis and the front-end computer had been launched as k1iz1 without any connection to the circuits (klog#36129, klog#36183). They run stable in recent 1+ month. So we started to use them for ITMX.

After stopping the old k1ix1 and V1 IO-chassis, all SCSI cables for AA inputs/AI outputs were moved from V1 to V2 IO-chassis. After then, the MAC address of the computer that had been operating as k1iz1 was re-registered to DHCP as k1ix1. As a quick check of front-end operation, we launched the new k1ix1 and we didn't find any issue on GDS and DAQ MEDM screens. Note that, RFM card installed in the new k1ix1 is signle-mode one. When we removed old k1ix1, it might be better to replace RFM card as multi-mode one. Using single-mode one for k1ix1 is no problem, but single-mode one can be used both long and short distance and it's useful for another place.

Finally, DB37 BO/BIO cables were also moved from V1 to V2 IO-chassis. After then we changed the guardian request but it IP control cannot be engaged probably because of large change (~2degC) in the room temperature of IXV. It seems come from our activity in long time. Checks with guardian will be able to be done after the room temperature will come back as same level before our work.

For this reason, please note the fact that the Guardian operation has not been verified though it's no problem to request some state to VIS_ITMX guardian.
Comments to this report:
satoru.ikeda - 17:14 Monday 16 March 2026 (36586) Print this report

[Nakagaki-san, YamaT-san(Support), Ikeda]

This task is related to K-Log#36129.
We measured the noise levels of the ADC and DAC using the new V2 IO chassis.
(We used different ADC and DAC cards than those used with the old IO chassis.)
For the DAC measurement, We used an empty port (on the Board 2 side) of the Whitening Chassis (S1909739).

During DAC measurement, the signal is boosted by 42 dB using whitening.

[Data]
/users/DGS/measurements/ADC/K1IX1/{ADC,DAC}/20260316_V2_IO_CHASSESS/
 

Images attached to this comment
Non-image files attached to this comment
ryutaro.takahashi - 23:21 Monday 16 March 2026 (36592) Print this report

I offloaded the IP H2 with the FR for recovery from the saturation. The guardian state could be switched from READY to ISOLATED.

satoru.ikeda - 10:04 Tuesday 17 March 2026 (36595) Print this report

ITMX has successfully reached the LOCK_ACQUISITION state.
We will leave it in this state for a while to verify that no issues arise with the new V2 I/O chassis.

takahiro.yamamoto - 22:43 Wednesday 18 March 2026 (36619) Print this report
[Ikeda, Nakagaki, YamaT]

Finally, V2 IO chassis S2416127 was installed at U6-9 of IXV1 rack after removing V1 IO chassis S1807864.
ITMX is currently operated using a fully installed V2 IO chassis and new MTP optical fiber cabling.
This marks the first successful instance of a DGS hardware upgrade toward O5.

-----
IO chassis for ITMX was replaced from V1 to V2 in klog#36572. But V2 IO chassis was still put at the outside of IXV1 rack because V1 IO chassis was still left in IXV1 rack for easy and quick recovery to the old configuration. After then, we confirmed that ITMX can stay in LOCK_ACQUISITION stably with V2 IO chassis. So we removed the V1 IO chassis from the IXV1 rack and installed V2 IO chassis there, today. With this work completed, ITMX is now operated with V2 IO chassis and a new MTP fiber cable which are fully installed. ITMX now achieved final configuration for O5 and this is the first success of upgrading DGS hardware.

To reduce downtime by DGS upgrade after O5, it is important to do same upgrades on as many other racks as possible before O5. Currently, we plan to do it for ITMY during SRM replacement and for ETMX/ETMY after IR1. ~40 working days will be required only for a same work about remaining 20 front-ends (because of limitation on equipments, working space and conflict each other, parallel upgrades for multiple front-end is probably difficult). According to an experience in this time, fortunately, we can probably do same upgrade works in ~ 2 days per front-end with restoring a front-end operation every day during those 2 days. So, it might be a good idea to consider using the two-week period (two maintenance days) for same upgrade works on remaining front-ends also after the SRM replacement work.

By the way, V1 IO chassis was still left in IXV room and old IX1 front-end was also still in ICV rack (RFM board was stolen today for the next upgrade of ITMY). These equipments can return back to the mine or SK server room anytime though I'm not sure sufficient space in both server rooms.
takahiro.yamamoto - 18:12 Thursday 19 March 2026 (36626) Print this report
We removed the old K1IX1 front-end from U20-21 of ICV rack.
The removed server was moved to SK server room.
satoru.ikeda - 10:23 Friday 27 March 2026 (36666) Print this report

I removed the definition for the sixth DIO6464 card from the k1iopix1 model.
I discovered this card while replacing it with a V2 IO chassis.

It has never been used, and only five cards are currently in use in the new V2 IO chassis and user models.

This definition was added in K-Log #5629.

Images attached to this comment
Non-image files attached to this comment
Search Help
×

Warning

×