New Community Ranking System
Our Community ranking system has recently been updated. You may notice changes in user rankings and receive system messages or notifications. If you have questions about how the new ranking works, please refer to the announcement post for more details (click here).
Repeated alarms
HVAC and Pumping Forum
Support Forum for HVAC and pumping machines, Modicon M17x and EcoStruxure Machine Expert HVAC software for chillers, AHU, CRAC units for datacenters or process chillers applications - from design, implementation to troubleshooting and more, by Schneider Electric.
Search in
Improve your search experience:
Exact phrase→Use quotes " "(e.g., "error 404")
Wildcard→Use * for partial words(e.g., build*, *tion)
AND / OR→Combine keywords(e.g., login AND error, login OR sign‑in)
Keep it short→Use 2–3 relevant words, not full sentences
Filters→Narrow results by section(Knowledge Base, Users, Products)
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-02-1511:10 AM. Last Modified: 2022-02-1511:47 AM
Repeated alarms
Based on the link shared by @Bastian_Schmitz I sort of "streamlined" the historical alarm project to make it a little bit easier to setup. I developed an alarm coding mechanism to be able to save alarms and dates on a single UDINT register instead of having four different sets of registers. Code is available here
The caveats are: only 64 (63 if you prefer not to use alarm code 0) different alarms are possible, and alarm date "seconds" are not saved. At least for our usual HVAC projects both caveats are not important. Maybe for some other projects the original approach is better. There is a third caveat is that you need to configure a "reference year" (the idea is to use the year the project is released) because date "year" is limited to 64 years.
My next goal is to try to implement a feature which is found on many parametric controllers, which is that if an alarm occurs repeatedly, usually 3 times in an hour or so, this alarm does not auto-reset, there must be some manual reset for that to happen.
I can write a function block with a FOR LOOP and use an array to keep count of the alarms and make the timing calculation but being honest, I do not know if that would be the best way, I am hunted by the ghost of the WDT overflow. I was hoping that I could somehow index the alarms to only search for one specific alarm when it occurs. First though was using an array but this would mean a 64x50 two dimensional array on memory the way I first though ot it.