Ask our Experts
Didn't find what you are looking for? Ask our experts!
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).
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Search in
Please select a country to continue with beta search.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-05-22 10:47 AM
I'm configuring a no change alarm for my heart beat tag. The heartbeat is counting up by 1 every 2 second. I want to trigger no change alarm if the system detects the heartbeat doesn't change after 15 Seconds. Attached is screenshot of my configuration. It seems pretty straightforward. But it doesn't work for me.
Wondering if I'm missing anything or anyone successfully make this working?
Thanks
Here is the online instruction:
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-05-26 01:38 AM
Geo SCADA 2025 R2, available soon, enables a No Change alarm based solely on time and not specifically on incoming values being unchanged.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-05-25 05:35 PM
I don't know about any changes in this area to recent versions of Geo SCADA, but originally the no change alarm still required a value to be updated for that point for the check to be to triggered, i.e. it is a no-value-change-when-a-new-value-is-recieved alarm, not a no-new-value-recieved alarm. It has caught many people out, including me, as its not that obvious from the name. Its purpose is to detect stuck values such as say a pump running speed still reporting but not changing, not to detect when you're no longer getting data and so the value would be stale.
For heartbeats using internal points (i.e. something external is writing to Geo SCADA), what I do is set out of range to be the alarm (e.g. if heartbeat is going 0-100 then -1 is alarm, make sure the control range is set to allow) and then run some logic every X seconds and if the point's CurrentTime is less than Now - {your acceptable delay} then set the value to -1, and so alarm raised, and you've not used up an extra point licence. This then also means that when the heartbeat kicks in again then it should clear the alarm automatically.
If the heartbeat is being read from say a device using Modbus, etc, then you'll need to create a second point (internal digital, licence impact) with similar time logic to above to set 0 {normal} or 1 {alarm} as necessary.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2026-05-26 01:38 AM
Geo SCADA 2025 R2, available soon, enables a No Change alarm based solely on time and not specifically on incoming values being unchanged.
Link copied. Please paste this link to share this article on your social media post.
You’ve reached the end of your document
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.