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.
|
Do any Prosoft modules support Modbus UDP?
Viewed 1 times since Mon, Aug 24, 2015
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
Defining the Slave ID when issuing Modbus Broadcast write commands
Viewed 1 times since Tue, Nov 28, 2006
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
Why are my PLX gateway modbus serial commands not executing despite being enabled?
Viewed 1 times since Wed, Aug 12, 2015
My RX light is on solid, what might that indicate?
Viewed 1 times since Fri, Jul 17, 2015
Can Modbus support redundant masters?
Viewed 1 times since Tue, Nov 28, 2006
How do I read/write Modbus binary data?
Viewed 1 times since Wed, Nov 29, 2006
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
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
|