Hi Guys,
Yeah the routine containing the timer is called un-conditionally. This bug is effecting every timer in the project..
It shouldn't matter if the subroutine is called un-conditionally or not; when the timer is enabled the processor 'tics' should be being used in the 'TON' instruction to account for discrepancies in cycle time - there seems to be an issue here..
I am using 1.29.111 at the moment - their tech support guys have asked me to go to the lastest (1.30.52) which has come out in the last 2 days so I'll give that a try & let you know about cycle times.
Regards,
Louis.