Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
I am working on an application and it seems that the alarm manager doesn't always pick up alarms that are active for a single program cycle.
For example: a timer expiring. The process will run until the timer expires, however the alarm signal of the expired timer is only active for one cycle and the process is stopped. This seems to be too quick for the alarm manager to pick it up and display the error or warning in the alarm table.
My solution in the past has been to introduce a TOF on the alarm signal but I am wondering if anyone has a better solution?
Thank you
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
I am working on an application and it seems that the alarm manager doesn't always pick up alarms that are active for a single program cycle.
For example: a timer expiring. The process will run until the timer expires, however the alarm signal of the expired timer is only active for one cycle and the process is stopped. This seems to be too quick for the alarm manager to pick it up and display the error or warning in the alarm table.
My solution in the past has been to introduce a TOF on the alarm signal but I am wondering if anyone has a better solution?
Thank you
Hi,
some years ago I had the same problem.. (and additional some other things).
For that there was a Jira entry... which is not fixed till now.
I decided to program my own alarm manager which can detect every cycle and which have a correct time stamp (which is also a problem).
One workaround was to add the Alarmmanager PRG a second time in the task.
see attachments.
May it helps.
BR Chris