| 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.
|
What are the causes of a -11 error code using a ProSoft Modbus product?
Viewed 1 times since Mon, May 17, 2010
I am trying to use a ProSoft Modbus solution to send/receive data to a MSA Ultima X gas dectection system with Modbus interface and am having problems. How can I resolve this issue?
Viewed 1 times since Thu, Apr 24, 2008
How can I detect the feedback status of individual command successful or failed?
Viewed 1 times since Wed, Nov 29, 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
Why is the bit or coil level data incorrect?
Viewed 1 times since Tue, Nov 28, 2006
How do I read/write Modbus binary data?
Viewed 1 times since Wed, Nov 29, 2006
Defining the Slave ID when issuing Modbus Broadcast write commands
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
How can a module's Modbus port, configured as a Slave port, detect communication loss with the Master port?
Viewed 1 times since Tue, Nov 28, 2006
|

Add Comment