EcoStruxure Geo SCADA Expert Forum
Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-11-27 06:02 AM
In the log file for the channel used for communication via the IEC 60870-5-104 protocol, I am constantly encountering the error 'Tx 16 bytes at 26-NOV-2024 06:58:02.557 to "IEC104.Direct Outstation 3" SCN(Error Response)'. What does this error mean, and does it affect the quality of communication via the protocol? I`m using Geo SCADA Expert 2020
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: 2024-12-16 01:42 AM . Last Modified: 2025-02-06 02:29 AM
No reply to this yet? My only suggestion is to look at the protocol comms log and show it to a 60870 expert.
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: 2024-12-16 01:42 AM . Last Modified: 2025-02-06 02:29 AM
No reply to this yet? My only suggestion is to look at the protocol comms log and show it to a 60870 expert.
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: 2025-02-03 04:00 AM
Google: IEC 60870-5-104 SCN error
An "IEC 60870-5-104 SCN error" indicates a communication error within the IEC 60870-5-104 protocol, which is a standard used for data exchange in power system automation, specifically related to the "SCN" (Status Code Not Valid) message, meaning the received status code from a device is not recognized or considered valid by the system trying to communicate with it.
Key points about this error:
Protocol issue:
This error signifies a problem with the data format or structure sent by the device, potentially due to incorrect configuration, firmware issues, or a malfunctioning device.
Status code mismatch:
The "SCN" error means the receiving system couldn't understand the status code received from the device, which is used to indicate the state of a command or data transfer.
Potential causes:
Incorrect device configuration: The device might be set to send an invalid status code due to incorrect settings.
Communication issues: Network problems like packet loss or latency could corrupt the data transmission, leading to a misinterpreted status code.
Firmware incompatibility: Outdated firmware on the device might not be compatible with the communication protocol version used by the system.
Faulty device: Hardware issues with the device itself could be causing the incorrect status code transmission.
Link copied. Please paste this link to share this article on your social media post.
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.
With achievable small steps, users progress and continually feel satisfaction in task accomplishment.
Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.
of