Trying to gather more info about the nature of these M3 SRM WD trips in light of OWL Ops being called (at least twice in recent weeks) to press one button.

• Since 10/16/2024, there have been 10 instances where M3 WD trips during SRC align during initial alignment, which have caused a total loss of 1hr and 49 mins of locking time. While this isn't a lot, the trending WD trips for SRM shows that this is a more recent occurrence.
• Out of the 31 total M3 SRM WD trips since start of O4b (and not counting vent), 12 happened in the last 5 weeks, with 10 of these being during initial alignment (i.e. this type of trip).
• Since the rise of this issue, we have gone through a total of 112 initial alignments, meaning it's occurred in 9% of initial alignments. Doesn't sound like a lot but if guardian has an initial alignment during an OWL shift, this suggests a 1/10 chance of being woken up just to press "untrip".
• Sometimes, M3 is too rung up in this state that untripping takes 20 mins but other times it only takes 1-2 mins.
• FRS Ticket

Relevant Alogs:

Part 1 of this investigation: 81476

Tony OWL Call: alog 81661

TJ OWL Call: alog 81455

TJ OWL Call: alog 81325

It's mentioned in some more OPS alogs but no new info.

Next Steps:

• The possible cause per a last convo with TJ was that guardian thinks that SRC is aligned when actually it is locked to the wrong mode, causing the SRM controls to go awry when re-misaligning during initial alignment - so just rehash that conversation when possible.
• Find out what proportion of initial alignments this has happened to since 10/16.