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

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

How to detect Modbus Communication Failure at Modicon M580?

Modicon PAC Forum

A forum for topics related to the scope of Modicon PAC offers and ecosystem along the whole lifecycle: Modicon M580 and 340, EcoStruxure Control Expert, EcoStruxure Process Expert (Unity Pro) and more.

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
  • Modicon PAC Forum
  • How to detect Modbus Communication Failure at Modicon M580?
Options
  • 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
ciupol
Lieutenant ciupol
9
MatthewM
Lt. Commander MatthewM
8
RoozeeR
Lt. Commander RoozeeR Lt. Commander
7
Trinxs1
Lt. Commander Trinxs1 Lt. Commander
6
View All

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Modicon PAC Forum
RuchirSomani
RuchirSomani
Cadet

Posted: ‎2025-05-19 04:43 AM

0 Likes
5
396
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • 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-05-19 04:43 AM

How to detect Modbus Communication Failure at Modicon M580?

Hi,

 

I need to understand how to find/configured in Control Expert for M580 whether Modbus Communication with any Modbus Slave device is working or has stopped ?
Is there any fail/error bit/code to sense this ?

 

Right now as values gets transferred between M580 and PSO over Modbus TCP,  the value gets stuck in PSO if downstream devices stop communication with M580 for any reason.
Is it also possible to convert this value automatically to "ZERO" in case the Modbus communication with field device breaks.

Labels
  • Labels:
  • 02. Modicon M580 ePAC
  • 06. EcoStruxure Control Expert
  • Tags:
  • english
Reply

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

  • All forum topics
  • Previous Topic
  • Next Topic
Replies 5
Hennie_Smith
Lieutenant JG Hennie_Smith Lieutenant JG
Lieutenant JG

Posted: ‎2025-05-19 08:50 PM

0 Likes
2
371
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • 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-05-19 08:50 PM

Good day,

 

1. Yes you can monitor the Freshness bit in the Device DDT variable which is created when adding modbus device.

 

Hennie_Smith_1-1747712812166.png

 

Secondly to set the values to 0 if comms fail, open the NOC/CPU in the DTM browser and go to the Request settings of the modbus device. Each request can be set to 'Set to Zero' under the Last Value column. 

 

Hennie_Smith_2-1747712909481.png

 

Regards,

Hennie Smith

 

 

Reply

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

YONGHO-KIM
Lieutenant JG YONGHO-KIM Lieutenant JG
Lieutenant JG

Posted: ‎2025-05-19 10:05 PM

0 Likes
0
360
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • 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-05-19 10:05 PM

1. I have implemented communication fault/normal status detection using the 'Gest' value from Read_Var.
The second word of the GEST value is 0 when communication is normal, and any value greater than 0 indicates an error.
Please refer to the attached PDF file for more details, and feel free to contact us if you have any questions.

YONGHOKIM_0-1747717446500.pngYONGHOKIM_1-1747717475692.png

 

Attachments
Reply

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

RuchirSomani
RuchirSomani
Cadet

Posted: ‎2025-06-18 01:18 AM

In response to Hennie_Smith
0 Likes
1
94
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • 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-06-18 01:18 AM

Hi,
Thanks a lot for your reply.

1) For what you have shared with NOC card, is same feature available with NOM card as well as we are polling around 10 Nos. of Modbus Serial devices using NOM card in M580.

2) Also, we have observed randomly data of MFM(Multi Function Energy meter)getting stuck while using READ VAR block to poll MFM(Multi Function Energy meter) for 10 Nos. MFMs in one single loop.

What is further way to diagnose such issues  i.e. how to understand if query length is too high or if we need to increase delay period between 2 polls of Modbus - this is for Modbus Serial(RTU) communication only. Does M580 inherently supports protocol tracing ?

Looking forward to your support.

Thanks & Regards

Ruchir Somani

Reply

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

ag56
ag56
Cadet

Posted: ‎2025-06-18 01:20 PM

0 Likes
0
72
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • 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-06-18 01:20 PM

Hello Ruchir,

 

There are some key concepts to take into account when implementing READ_VAR function.

 

First, you must specify the timeout period in the third register of the GEST array. A value of 5 means 500 ms and should normally be enough.

Please note that the NOM is configured with its own default answer delay (10 * 100 = 1000ms) and 3 retries. The timeout set in the third register should be greater than the answer delay time X number of retries.

You can reduce the default answer delay and set the number of retries to 0 to speed out the process if needed.

 

Second, it is recommended to expose the READ_VAR EN-ENO pins, then negate the EN pin and connect bit 0 (Active) of the first GEST register to it. This will disable the block call when a communication session is active.

 

Third, for serial communication avoid using more than one READ_VAR in parallel for the same NOM channel. If you are polling several devices on the same line, you need to manage the order in which they are called. For this purpose I am attaching a DFB based on DATA_EXCH function which is designed to manage as many devices as required sequentially and cyclically by proper parametrization. This all-in-one solution DFB requires no extra code. However, I do not have it documented in English so you will probably need some help to implement it. If you are interested in testing it, I can provide some simple examples.

Best Regards.

Attachments
EXCH_MULTI_N.zip
Reply

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

YONGHO-KIM
Lieutenant JG YONGHO-KIM Lieutenant JG
Lieutenant JG

Posted: ‎2025-06-18 08:31 PM

In response to RuchirSomani
0 Likes
0
74
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • 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-06-18 08:31 PM

1. The file I attached was applied to the BMXNOM card. Therefore, the same configuration can be applied to the NOM card as well.
2. Does the freezing issue occur when communication is lost with the device connected to the BMXNOM0200?
If so, please refer to the following link for more information:
https://community.se.com/t5/Modicon-PAC-Forum/BMXNOM0200-READ-VAR/m-p/487416#M1274
3. If the issue is not related to point 2, please increase the polling interval at the READ_VAR EN input as shown in the attached image.
4. Compare the GEST values between normal and abnormal communication cases.
5. If you have any further questions, feel free to reply.image.png

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