Even though the threshold is set to 32k, the Stage2 tripped when the Actuators only hit 30k. Is this just from the 512k downsampled data?
The attached trend plots shows the full data and although it gets close, it doesn't appear to reach the threshold. Shame we get shut down for such a short transient.
Hugh means 512 [Hz], because the _DQ channel he's posted is down sampled from the native user model rate of 16384 [Hz] to 512 [Hz] before it sent out for frame storage. No way to confirm your suspicion Hugh, with the data that's currently stored. Brian says "We should store that stuff faster." I agree, especially if we add "if we *actually* want to know for these super-high-frequency glitch-type trips," because most people probably don't, they just want it not to happen. #TriggerECR Have y'all reduced the high-frequency roll-off of these loops yet? That's the real solution...