Home » Categories » Protocols » Modbus |
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? |
Article Number: 378 | Rating: 3/5 from 1 votes | Last Updated: Wed, Mar 9, 2011 at 2:55 PM |
The Slave Status list is merely a 'scratchpad' area the Modbus Master firmware uses to keep track of its current poll state with respect to a particular Slave. The Slave Status List is not the best place to monitor the health of communications between a ProSoft/ProLinx Modbus Master and the Slaves on the Modbus Serial network. Using the Command Error List is the best way to know if communications to a Slave are working correctly or not. You can use the Command Error Pointer for inRAx solutions or the Data Map for ProLinx solutions to have the Command Error List placed in the User Read Data area. As each command is executed, the firmware places a value into this list for each command. If the value is zero, the slave responded appropriately to the Master command and communications appear to be working normally. If the value is non-zero, this indicates a problem with the communication and the non-zero value can give cues as to what the problem might be. Logic can then be written to monitor the Read Data area used for the Command Error List and alarm on non-zero values, either on a per-command or per-slave basis. Since occasional command failures are not uncommon on a Modbus serial network, it is usually a good idea to include a 5-15 second proving timer in the alarm logic to prevent 'nuisance' alarms. |
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
How can I detect the feedback status of individual command successful or failed?
Viewed 1 times since Wed, Nov 29, 2006
Can Modbus support redundant masters?
Viewed 1 times since Tue, Nov 28, 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
Why is the bit or coil level data incorrect?
Viewed 1 times since Tue, Nov 28, 2006
Defining the Slave ID when issuing Modbus Broadcast write commands
Viewed 1 times since Tue, Nov 28, 2006
My RX light is on solid, what might that indicate?
Viewed 1 times since Fri, Jul 17, 2015
What are the causes of a -11 error code using a ProSoft Modbus product?
Viewed 1 times since Mon, May 17, 2010
How do you detect the individual Slave failure?
Viewed 1 times since Wed, Nov 29, 2006
How do I monitor the health of coms to my slaves when the module is a Master?
Viewed 1 times since Wed, Nov 29, 2006
|