J. Kissel

Beginning to tackle the changes approved in ECR E1400102, i.e. modifying of SUS User Watchdog to reduce false alarm rate, I've made it through the three BSC-type suspensions (and their respective HEPIs), QUADs, BSFMs, and TMTSs. The final change list includes:
- Removing the OSEM DC and Actuator AC trigger paths from the watchdogs
- Removing the Optical Lever watchdog trigger paths from the QUAD and BSFMs
- Merging all stages of USER and USER DACKILL MEDM screens
- Creating a one-click, reset all button for all stages of USER and USER DACKILL watchdogs (by hooking a single reset signal to each stage of USER WDs, and copying SEI's script for resetting the USER and USER DACKILL psuedo-simultaneously.)
- Changing the SUS USER DACKILL (which informs the "PAYLOAD" trigger flag of the ISIs) to use the AND of every watchdog stage instead of an OR of just the top mass [behavior is unchanged for TMTS, but TMTS is NOT hooked up to the ISI]
- Removing the SUS USER DACKILL connection to HEPI's PAYLOAD trigger

I've exercised the SEI / SUS watchdogs (by decreasing the trigger threshold below normal values) to ensure the desired behavior is achieved and all screens are reporting the correct status, and no funky reset loops happen. Of note, if just one of the USER WDs are green, then one can reset the USER DACKILL i.e. the PAYLOAD flag for the ISI. This is fine -- those user watchdogs which are still setting off triggers cannot be reset, as has always been the case. This just makes it that much easier to begin resetting a chamber after a "catastrophic" chamber trip, which almost always is because of a front-end boot fest, not anything physically happening to the chamber.

FIXME's as a result of these changes (for BSFMs and QUADs ONLY):
- Because the L3 (fr WUADs) and M3 (for BSFMs) no longer exist, the Guardian is getting confused in its checks for whether the suspension is tripped, and throwing an error. I tried digging into the sustools.py rabbit hole, but got lost and gave up quickly. I'll leave this to Jamie / Mark / Arnaud to fix. Regardless of the guardian failure, all SUS have been turned on, damped, with their previous alignment restored.
- Because the L3 (fr WUADs) and M3 (for BSFMs) no longer exist, I've terminated where the corresponding bit is fed into the ODC bitword creator instead of shifting everything around (again). As such, bits 7 (for QUADs) and 5 (for the BSFM) should be masked out and ignored until we're motivated enough to clean this up in the front end.

Though I've tried to restore all BSC chambers to full isolation, damping and alignment, the ground has been too violently non-stationary (wind, earthquakes, trucks, etc.) to keep things up for too long. I'll try again before I leave, but I doubt it'll stay up for too long.

After all changes were complete, h1dc0 was successfully rebooted at 01:35 UTC (18:35 PDT), with both frame writers (h1fw0 and h1fw1) happily cliking up there up-time (~1500 seconds as of this log)

Those files affected / created and now committed to the USERAPPS repository:

${userapps}/release/sus/common/src/
M       WATCHDOG.c
${userapps}/release/sus/common/models/
M       TMTS_MASTER.mdl
M       QUAD_MASTER.mdl
M       SIXOSEM_F_STAGE_MASTER.mdl
M       FOUROSEM_STAGE_MASTER_OPLEV.mdl
M       BSFM_MASTER.mdl
${userapps}/release/sus/common/scripts/
A       wdreset_all.pl
${userapps}/release/sus/common/medm/
M       bsfm/SUS_CUST_BSFM_OVERVIEW.adl
A       bsfm/SUS_CUST_BSFM_WD.adl
A       quad/SUS_CUST_QUAD_WD.adl
M       quad/SUS_CUST_QUAD_OVERVIEW.adl
M       quad/SUS_CUST_QUAD_R0.adl
A       tmts/SUS_CUST_TMTS_WD.adl
M       tmts/SUS_CUST_TMTS_OVERVIEW.adl
${userapps}/release/hpi/h1/models/
M       h1hpietmx.mdl
M       h1hpietmy.mdl
M       h1hpiitmx.mdl
M       h1hpiitmy.mdl
M       h1hpibs.mdl