- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-06-13 10:27 PM . Last Modified: 2023-05-02 11:55 PM
Lost comms with outstation on channel XX in GEO SCADA
Hello,
"Lost comms with outstation on channel XX"
our client, issue a repeated behavior around specific hour every day!!!, where most the outstations lost comm. and establish it again in seconds repeatedly as noticed in the events journal at GEO SCADA while they were really connected after checking.
We have traced their drivers log (modbus and dnp3) nothing found except shows similar messages to the events log
What could causes such behavior? and how to prevent it?
Appreciate any suggestions /hints.
Thanks in advance.
Link copied. Please paste this link to share this article on your social media post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-06-14 12:25 AM
Hi,
You could enable comms logging on the channel to see what's happening at the time. Either a poll (or a number of them) are going unanswered by the device, or perhaps some noise is returned.
It might be that the driver is waiting for a server response and misses a reply, but if that's the case you may see the replies later in the log.
Steve
Link copied. Please paste this link to share this article on your social media post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-06-14 04:59 AM
Thanks Steve
We did enable Comms Logging on a sample and we will see>>>
But to give you more clear picture as below of the event journal of an outstation:
as you see the comms keeps lost and established in less than second between each event
Is it possible of missing or wrong configs at channel level or outstation level?
Thanks again
Link copied. Please paste this link to share this article on your social media post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-06-15 05:05 AM
I've seen similar behaviour in a few situations.
- A DNP3 device firmware bug that caused it to swap the active route to the backup channel when it received a Shared Outstation Channel heartbeat. It caused ClearSCADA to fail over channels, and then the same behaviour would occur on that channel.
- Poorly configured firewall rule that allowed the Establishment messages (for TCP) but not Connected messages (i.e. the actual traffic).
Does your client have an RTU that is directly adjacent to their GeoSCADA server (i.e. that wouldn't be prone to network issues)?
Are there outstations that don't have this same behaviour?
Does the timing coincide with anything else, like network operations, large backups elsewhere, backups on the GeoSCADA Expert servers etc?
Lead Control Systems Engineer for Alliance Automation (VIC).
All opinions are my own and do not represent the opinions or policies of my employer, or of my cat..
Link copied. Please paste this link to share this article on your social media post.

