WP9584
Jeff K, TJ, Jim, Corey, Dave:
The IOP models which handle the SWWD system were modified today to change the bypass time from an internal model constant to an EPICS input part.
The following models were modified and restarted: h1iopsus[b123, h2a, h34, h56, ex, ey] h1iopsei[b1, b2, b3, h16, h23, h45, ex, ey]. Of course all the user models on these front end computers were also restarted as part of the IOP restart procedure.
Even though this change meant an EPICS output part was converted to an EPICS input part with the same name, the reordering of the simlink parts and possibly porting from matlab2015 to matlab2019 meant that the INI files were changed, requiring a DAQ restart.
The order of the upgrade was: Corner Station SUS, End Station SUS, Corner station SEI, End Station SEI.
The IOP SDF safe.snap files were modified to track the bypass time setting. We set them to their original values of 1200 seconds for SUS, 900 seconds for SEI.
The detailed SWWD MEDM screens were modified to make the BYPASS_TIME an input widget, allowing the user to change it.
The CDS Overview MEDM was modified for the SWWD IOP models, I sacrificed the TP_NUM circle for these IOPs to show their SWWD bypass status as a circle with a border;
Circle shows the SWWD input signal status; GREEN = input good, RED = input bad, watchdog will trip
Border shows the SWWD bypass status; GREEN = no bypass, YELLOW = watchdog is bypassed.
For example, a red circle with a yellow border means the bypass is active, but if it were to time-out or be cancelled then the watchdog would eventually trip.
The SWWD circles are clickable, which will open the SWWD Overview MEDM.
Following all the restarts, the DAQ was restarted once to sync up the INI files. The DAQ agreed that no effective change had been made and a new run number was not issued.
The attached MEDM shows the situation when the Guardian node had bypassed all the SUS SWWDs
For the record, here are the 18bit/20bit DAC Auto-Calibration results following the restart of the SUS IOP models on Tuesday (sans h1sush2b)
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susb123.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susex.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susex.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susex.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susex.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susex.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susey.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susey.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susey.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susey.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1susey.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush2a.cds.ligo-wa.caltech.edu DAC AUTOCAL FAILED
h1sush2a.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush2a.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush2a.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush2a.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush2a.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush2a.cds.ligo-wa.caltech.edu DAC AUTOCAL FAILED
h1sush34.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush34.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush34.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush34.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush34.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush34.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush56.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush56.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush56.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush56.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS
h1sush56.cds.ligo-wa.caltech.edu DAC AUTOCAL SUCCESS