Bug with TIMEDOUT instruction ?

[belias]

Over the past few days, I've had it happen twice where the TIMEDOUT instruction doesn't activate the output as expected.  The only way (that I've found) to correct the problem is to copy / paste the rung to a new Rung #, remove the old rung, and accept / write changes.  I've never seen this happen with any other instruction.

In the attached screen-shot, turning on C97 would not cause Y0 to be activated at all.  Copy / paste to a new location, and it works perfectly.

[BobO]

Do you have a saved version where it isn't working correctly? That would be very helpful to us.

[belias]

Just sent you a PM

[BobO]

For those who might see this later, there was no bug, just confusion on how the instruction worked. This was exacerbated by the fact that we weren't checking TIMEDOUT for duplicate references to the same output (duplicate coil check), but we have now added that.

[franji1]

For those who might see this later, there was no bug, just confusion on how the instruction worked. This was exacerbated by the fact that we weren't checking TIMEDOUT for duplicate references to the same output (duplicate coil check), but we have now added that.

Here's the fix (also integrates the FLASHER instruction):