HEPI BS Tripped few minutes before ITMX ISI. This is the only HEPI that tripped in the neighborhood of the large quake.
ITMY ISI tripped--timing (H1:ISI-ITMY_ST2_WD_MON_GPS_TIME) indicates stage2 tripped on ACTuators 1 second before Stage1 on T240s but looking at the plots, the Actuators have only registered a few counts, nothing near saturation/trip level. But the T240s hit their rail almost instantly. It seems the Stage2 Last Trip (H1:ISI-ITMY_ST2_WD_MON_FIRSTTRIG_LATCH) should be indicating ST1WD rather than Actuator. On ETMY, the Trip Time is the same for the two stages and Stage2 notes it is an actuator trip but again, there are only a few counts on the MASTER DRIVE; seems this too should have been a ST1WD trip[ indication trip on Stage2--I'll look into the logic.
On the BS ISI, the Stage1 and Stage2 trip times are the same, and the Last Trip for Stage2 indicates ST1WD. The Stage2 sensors are very rung up after the trip time but not before unlike the T240s which are ramping to to the rail a few seconds before trip. ETMX shows this same logical pattern in the trip sequence indicators.
On the ITMX ISI, Stage1 Tripped 20 minutes before the last Stage2 trip. This indicates the Stage1 did not trip at the last Stage2 trip.
No HAM ISI Tripped on this EQ.
Bottom line: the logical output of the WDs are not consistent from this common model code--needs investigating. Maybe I should open an FRS...
Attachment 1) Trip plots showing Stage2 trip time 1 second before the stage1 trip where the stage2 actuators do not go anywhere near saturation levels.
Attachment 2) Dataviewer plot showing the EQ on the CS ground STS and the platform trip times indicated.
It seems this is not a problem with the watchdog but a problem with the plotting script. It seems for ST2 Actuators, it misses a multiplier on the Y axis. It works correctly for ST1 Actuators and all the sensors; it does not work for other chambers as well for ST2 ACT. FRS 6072.