Hi,

I experienced a strange issue with S_PEXT timers recently. Somehow, two timers I have in my program (running machine) got stuck in SET. Also the countdown was incorrect? They are both the same type (S_PEXT).

See the attached picture. This is the exact scenario. The input to the timer is low but the timer got stuck in SET and the countdown is showing 7s60ms although the S5 time is only 250ms?

Has anyone come across this issue before? Is this some kind of CPU firmware problem?

I had to reset the timers in the program to get it going again as I had nothing on the REST side of them.

If I remember correctly it happened before (a couple of years ago)- exactly the same scenario. The machine runs constantly 24/7.

Please don't post twice for the same problem.

You make also a topic here for the same problem:

S_PEXT timers stuck

I have deleted the copy of the post, it must have posted twice by accident.

Hi achris,

are you calling T20 mutiple times (second call very rare)?

Regards,

Frink

Hi,

Checked the simple things already, definitely not calling it twice.