WP11914, WP11918 Install ADC in h1iscex for h1pemex readout
Fil, Marc, Erik, Jonathan, Dave
In preparation for testing the new LIGO DAC card in h1susex, an ADC was installed in h1iscex which will read the new DAC's signals.
This ADC belongs to PEM, it was purchased to expand the number of accelerometers.
The ADC, its ribbon cable and interface card were installed in the h1iscex IO Chassis (see drawing). A PEM AA-Chassis was installed and connected to the ADC.
Two models were changed:
h1iopiscex: add 5th ADC
h1pemmx: readout the 5th ADC, route all 32 channels into filter modules with the names H1:PEM-EX_ADC_4_CHAN_n where n=0-31
DAQ restart was needed.
Add WAP channels to DAQ
Erik, Dave:
We took the DAQ restart as an opportunity to use the latest H1EPICS_WAP.ini which adds the missing corner station WAPs. EDC and DAQ restart needed.
Add IRIG-B signals back to end station CAL models
Keita, Fil:
The CNS-II Clock GPS receivers independent IRIG-B signals were reattached to the h1isc[ex,ey] AA chassis.
DAQ Restart
Dave, Jonathan:
The DAQ was restarted for the above model and EDC changes. There were several issues:
gds0 needed a second restart
FW1 spontaneously restarted itself after 728 seconds.
Tue11Jun2024
LOC TIME HOSTNAME MODEL/REBOOT
09:00:01 h1iscex ***REBOOT*** <<< Add 5th ADC
09:01:42 h1iscex h1iopiscex <<< new model
09:01:55 h1iscex h1pemex <<< new model
09:02:08 h1iscex h1iscex
09:02:21 h1iscex h1calex
09:02:34 h1iscex h1alsex
09:11:04 h1daqdc0 [DAQ] <<< 0-leg restart
09:11:15 h1daqfw0 [DAQ]
09:11:15 h1daqtw0 [DAQ]
09:11:16 h1daqnds0 [DAQ]
09:11:24 h1daqgds0 [DAQ]
09:12:07 h1daqgds0 [DAQ] <<< 2nd GDS0 restart
09:12:12 h1susauxb123 h1edc[DAQ] <<< EDC for WAP channels
09:16:20 h1daqdc1 [DAQ] <<< 1-leg restart
09:16:31 h1daqfw1 [DAQ]
09:16:32 h1daqtw1 [DAQ]
09:16:33 h1daqnds1 [DAQ]
09:16:41 h1daqgds1 [DAQ]
09:27:57 h1daqfw1 [DAQ] <<< Spontaneous FW1 restart
IRIB-B code was restored at gps=1402156961 for EX and 1402159619 for EY.
I checked H1:CAL-PCALX_IRIGB_DQ and H1:CAL-PCALX_IRIGB_DQ starting at 1402159619 for 20 seconds using /ligo/svncommon/CalSVN/aligocalibration/trunk/Common/Scripts/Timing/irig_check.sh and the IRIG-B code agreed with the timestamp of the data after the leapsecond correction (which the script automatically does).
H1 was running w/o independent IRIG-B from gps=1400946722 to 1402156961 for EX, from gps=1400947702 to 1402159619 for EY.
IRIG-B codes were confirmed good right before disconnection of the IRIG-B cables and right after the restoration.
The timing system behaved w/o any suspicious behavior during the IRIG-B outage, see the attached plot. Top: X and Y and timing error. 2nd from the top: Duotone zerocross check (not the full duotone fit) for iopiscex, ey, iopsusex and ey. 3rd from the top: Duotone zercross check for h1iopomc0. Bottom: h1iopiscex and ey DAC.
Glitch of the OMC duotone at day 7th (Tue June 04) should be Jeff's test during maintenance (alog 78238), and glitch at EX on day 14 is the rebood described in the parent alog of this.
During this period, we had 3 significant LVK GW public alerts, S240531bp, S240601aj and S240601co.
