Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

IEC 60870-5-104 protocol, error in log file.

EcoStruxure Geo SCADA Expert Forum

Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Remote Operations
  • EcoStruxure Geo SCADA Expert Forum
  • IEC 60870-5-104 protocol, error in log file.
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
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 Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
sbeadle
Kirk sbeadle Kirk
307
AndrewScott
Admiral AndrewScott
95
BevanWeiss
Spock BevanWeiss
89
AdamWoodlandToo
Lt. Commander AdamWoodlandToo
36
View All
Related Products
product field
Schneider Electric
EcoStruxure™ Geo SCADA Expert

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to EcoStruxure Geo SCADA Expert Forum
Solved
SergLSV
Crewman SergLSV
Crewman

Posted: ‎2024-11-27 06:02 AM

0 Likes
2
377
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2024-11-27 06:02 AM

IEC 60870-5-104 protocol, error in log file.

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

Labels
  • Labels:
  • Drivers
  • SCADA
  • Telemetry
  • Tags:
  • english
  • scada
  • SCADA app
  • SCADA software
  • SCADA tutorial
  • Telemetry and SCADA
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2024-12-16 01:42 AM . Last Modified: ‎2025-02-06 02:29 AM

0 Likes
0
296
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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.

See Answer In Context

Reply

Link copied. Please paste this link to share this article on your social media post.

Replies 2
sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2024-12-16 01:42 AM . Last Modified: ‎2025-02-06 02:29 AM

0 Likes
0
297
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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.

Reply

Link copied. Please paste this link to share this article on your social media post.

Brian0
Crewman Brian0
Crewman

Posted: ‎2025-02-03 04:00 AM

0 Likes
0
125
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

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.

Reply

Link copied. Please paste this link to share this article on your social media post.

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

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.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

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