Back to the discussion...

Yes #dp and #ixo, i agree that timing is affected by processing priority, as a general consideration.

This is true for most tech equipment.

So, this is one of those arrangements that you need to watch for the timing, so its relevant in this thread

So, ,maybe there is another thread we can post your original water meter solution, along with my full program to give others a sense of how this can happen?

eg. does the block number also have an effect on timing?
 - importance of testing

etc etc

ixo65

#dP,

did you even look at the programs?
Or is your statement just a general statement?

#AlanTrollip,

I just kept to the specification of the topic opener at the time:
"for example it timed 800 pulses in a minute ....".
And so no pulse could stay high for more than 1 second.

Sometimes you have to adapt each solution to the required information.
And with your solution, the second positive edge evaluation is not required. Look in the attachment.

 Second edge is required in my case

That is a semi-proportional dosing program to spread fertilizer over time on a farm irrigation system.
latch DI5 and DI6 to simulate pulses.

The flow display is at blocks 28, 32 , 44 and 76

Perhaps its the simulator, but sometimes it gives a 32626 reading or a zero when there is no extra rising edge (B077)

I await the comments...