pturmel
December 13, 2021, 4:27am
2
If you can have such execution problems, I would re-implement the transaction group as a gateway tag change script. Within a script, you can capture then do whatever you like with exceptions.
Edit: See "case 3" in this topic for ideas:
Ok. I use multiple techniques depending on the client’s needs and trust in hardware at various points along the chain.
In all cases, I avoid triggering on booleans, and I avoid writing any given value from more than one direction. I like to use small integers as triggers–increment to trigger, rolling over naturally, but skipping zero. Sometimes an LINT timestamp is a natural trigger (Logix UTC wallclock µs or Omron clock ns, perhaps).
1 Like