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

M251 - Modbus Serial (RTU) Slave : A module reports an error

Machine and Motion Control Forum

Support forum for Machine and Motion Control solutions, including Lexium MC12 and robotics, PacDrive, Modicon PLCs and I/Os, EcoStruxure Machine Expert Twin, … - from design, implementation to troubleshooting and more, by Schneider Electric

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
  • Industrial Automation
  • Machine and Motion Control Forum
  • M251 - Modbus Serial (RTU) Slave : A module reports an error
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
Bastian_Schmitz
Admiral Bastian_Schmitz Admiral
8
FernandoRodrigues
FernandoRodrigues Support
6
Francesco_Begnoni
Francesco_Begnoni Support
5
LeTomas
Lt. Commander LeTomas Lt. Commander
5
View All
Related Products
product field
Schneider Electric
EcoStruxure™ Machine Expert
product field
Schneider Electric
Logic Controller - Modicon M251

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to Machine and Motion Control Forum
Solved
FaresMuhammad
Crewman FaresMuhammad Crewman
Crewman

Posted: ‎2024-12-14 01:05 AM

0 Likes
1
374
  • 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-14 01:05 AM

M251 - Modbus Serial (RTU) Slave : A module reports an error

M251 - Modbus Serial (RTU) Slave: A module reports an error

I have an M251 connected to an EGX, which interfaces with four slave devices. The data is sent to the PLC through the EGX. I've noticed that the data monitoring process is quite slow, leading to data loss, especially when energizing an incomer associated with one of the slave devices. Sometimes, I experience significant delays in data updates or the data might not be updated at all, and I have observed this warning in Machine Expert. Could this warning be related to the issues I'm facing? How can I address the data delay or loss problem overall?

 

I have to mention that when I use any MODBUS scanner to read the data directly from the EGX sometimes I get a timeout error

Screenshot 2024-12-14 105905.png

 

Attachments
Labels
  • Labels:
  • Modicon M2xx
  • Tags:
  • egx
  • egx150
  • english
  • micom p127
  • ModbusRTU
  • ModbusSerial
  • TM251MESE
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
FernandoRodrigues
FernandoRodrigues Support
Support

Posted: ‎2025-04-16 01:47 AM

1 Like
0
106
  • 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-04-16 01:47 AM

Hello @FaresMuhammad 
The gateway (in this case EGX, but any gateway) represents a bottleneck on this communication. The gateway needs to convert requests coming from Ethernet side and send it to the Serial, wait for device's reply and forward it back.
Normally, IO scanning is too aggressive for this application, flooding the gateway and leading to data loss.
I'd suggest you to move to READ_VAR  / WRITE_VAR, where you can manage it on a better way (not easier, but better).

This won't make it faster, but reliable.

Also, number of requests for each device must be reduced to the minimum. E.g.: Better to read in 1 shot a larger length and bring unnecessary data in between than create 2 reading requests (not all devices allow it though, specially power meters..)

By experience, I'd say 100-200ms for each request (meaning 400-600ms for a complete round on those four devices IF one request is done by device, otherwise it will increase drastically) is feasible to reach and matches what serial can provide.

If you have several request for each device, this can goes easily to 1000ms or more to complete one round.


To increase performance, you might need to add extra EGX or to move to an Ethernet based fieldbus.

See Answer In Context

Reply

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

Reply 1
FernandoRodrigues
FernandoRodrigues Support
Support

Posted: ‎2025-04-16 01:47 AM

1 Like
0
107
  • 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-04-16 01:47 AM

Hello @FaresMuhammad 
The gateway (in this case EGX, but any gateway) represents a bottleneck on this communication. The gateway needs to convert requests coming from Ethernet side and send it to the Serial, wait for device's reply and forward it back.
Normally, IO scanning is too aggressive for this application, flooding the gateway and leading to data loss.
I'd suggest you to move to READ_VAR  / WRITE_VAR, where you can manage it on a better way (not easier, but better).

This won't make it faster, but reliable.

Also, number of requests for each device must be reduced to the minimum. E.g.: Better to read in 1 shot a larger length and bring unnecessary data in between than create 2 reading requests (not all devices allow it though, specially power meters..)

By experience, I'd say 100-200ms for each request (meaning 400-600ms for a complete round on those four devices IF one request is done by device, otherwise it will increase drastically) is feasible to reach and matches what serial can provide.

If you have several request for each device, this can goes easily to 1000ms or more to complete one round.


To increase performance, you might need to add extra EGX or to move to an Ethernet based fieldbus.

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