Counter Malfunction

[BobLfoot 301]

The Following is the code I question:

XIC Local:1:I.Data.0 TON DebounceOnTimer 500 0

XIO Local:1:I.Data.0 TON DebounceOffTimer 1000 0

XIC DebounceOnTimer.DN OTL DebouncedData0

XIC DebounceOffTimer.DN OTU DebouncedData0

XIO DebouncedData0 ONS DataOns.0 CTU CounterData0 32767 0

 

How many counts to expect in 30 seconds max.

How do you explain seeing 600 counts in 30 seconds?

[pcmccartney1 141]

I don't see how it can count more than 20 in a 30 seconds and then only if the scan was perfect and the input turned on and off at exactly the time for each TON preset.

Any chance of duplicate tagging somewhere else in the program?  Duplicate routine?

[Joe E. 259]

Is the counter tag used in another place?

[pcmccartney1 141]

Bob,

 

There is one typo in Rung 4 DebounceData0 versus DebouncedData0.  The little d is missing, what is that tag tied too?

[BobLfoot 301]

Typo Corrected.

Duplicates not found.

And only sporadically.  3 times last month it ran away.

[pcmccartney1 141]

Still don't see how it got to 600, because DebouncedData0 must transition from ON to Off to ONS the CTU.  What limits this to a 30 second period?  External source writing to CTU via RSLinx or OPC?  Something wirting to it from an HMI object tagged to the CTU.ACC?