Home » Categories » Protocols » Modbus |
How do you detect the individual Slave failure? |
Article Number: 292 | Rating: 5/5 from 1 votes | Last Updated: Fri, Jan 18, 2008 at 12:00 AM |
To detect the slave failure, you may use the command error list. Each command returns an error code once it is executed. If a command returns a value different of 0, this means that there was a problem during the command execution. The command error list can be found in the read data zone at the address you specified in mcm.port1.cmderrptr. |
Attachments (0)
![]()
There are no attachments for this article.
|
Comments
![]()
There are no comments for this article. Be the first to post a comment.
|
I have limited or no experience with Modbus. How can I find out more about the protocol and command structure?
Viewed 1 times since Tue, Nov 28, 2006
Do any Prosoft modules support Modbus UDP?
Viewed 1 times since Mon, Aug 24, 2015
Why is the bit or coil level data incorrect?
Viewed 1 times since Tue, Nov 28, 2006
What's the difference between Modbus ASCII and Modbus RTU?
Viewed 1 times since Wed, Mar 19, 2008
What are the causes of a -11 error code using a ProSoft Modbus product?
Viewed 1 times since Mon, May 17, 2010
How do I enter a Modbus address of 40001 or higher in the DevAddress command field of my MVI56-MCM?
Viewed 1 times since Tue, Nov 28, 2006
Read Commands from my Modbus Master to a ProSoft MCM Slave are working but Write Commands are failing. How do I fix this?
Viewed 1 times since Fri, Feb 8, 2008
My RX light is on solid, what might that indicate?
Viewed 1 times since Fri, Jul 17, 2015
I have a ProSoft Modbus Master solution and would like to know, is the Slave Status List the best place to monitor for communications health of the network?
Viewed 1 times since Tue, Mar 18, 2008
|