One Shot Event is Re-Enabling

[Bolt]

I have some code that alerts me of a fault.  The rung is quite simple.  Any of 4 inputs can be triggered (these are received via Modbus RTU), and a one shot to S22 with an email instruction.  That jumps to S23 to email when system returns back to normal state.  It seems to be randomly re-triggering the S22 email.  I have put together a trend view to see where the bump is coming from, but can't pinpoint it.  Not in trend view, but the program stays running continually.  Also can be seen as S23 stays on continually.

[franji1]

Stick an INC D999 (or whatever) below your SET S22 to see if the SGSET is firing.

If D999 is not incrementing every time the email is being sent, then you have a rogue JMP or SGSET or SGCONVERG or ? to S22.

[franji1]

OR is this rung that drives the SGSET in a Stage or a code-block that is EXITed or HALTed?

If that is true, the edge bit states are CLEARED whenever you JMP out of a SG or exit a code-block that has any edge contacts or edge-triggered box input legs.

[Greg]

But also, if Rung 20 is in a Stage that gets enabled, then if any one of the inputs to that rung happen to be ON when it gets enabled, then it will artificially generate an edge and perform the SGSET S22. So, every time it is enabled (after being disabled), and one of the inputs are ON, it will do the SGSET.

[Bolt]

Thanks for the assistance.  Turns out it was something in a prior stage that was causing the rung with the oneshot to be bumped.  Sorry for the silly question, I really thought I had eliminated the obvious before asking.