Observing the many trips HAM2 has experienced using the guardian recently, I've seen that after the first group of dofs are isolating, the remaining dof error points often grow large and when these dofs gains are ramped up, the ISI trips with a rung up GS13.  I saw that the guardian was loading the reference locations between the dof groups engagement.  Whereas the old seismic command scripts would only load the reference locations after all the dofs are isolating at the free hanging position.  Remember, the command script was not having any trouble turning the isolation back on.

Jamie modified the Guardian to do the loading of the reference location at the end of the isolation process like the command scripts.  When I got my window to test this, I actually forgot at first to restart the guardian.  And, the first couple times guardian was able to bring it up!  When I realized it wasn't doing it the new way, I remembered the restart, but I kept trying the guardian.  On the third or fourth attempt with the guardian it tripped.  I then restarted the guardian and then the guardian was successful at full isolation at least 6 times before the commissioners returned to the control room.

So again, my theory is, when the isolation loops are servoing to a place away from the free hanging position, the uncontrolled dofs error points can grow large.  This is dependent on many thing and lots of luck good & bad.  When the loop is engaged at low gain, the error point may be swinging about zero and if the loop gain is changed to 1.0 (from 0.01) at an unlucky time, bam goes the GS13.

Currently, HAM2 ISI is successfully back under Guardian conrol.