Home » Categories » Protocols » Modbus |
Why is the bit or coil level data incorrect? |
Article Number: 56 | Rating: 1/5 from 1 votes | Last Updated: Wed, Feb 25, 2015 at 3:24 PM |
Bit read and write commands are issuing properly, and responses are coming from the slave(s), but the data is not correct. When setting the intaddress field for a bit or coil Modbus command (Modbus function codes 1, 5, and 15), the internal address specified in the command must be at the bit level.
|
Attachments (0)
![]()
There are no attachments for this article.
|
Comments
![]()
There are no comments for this article. Be the first to post a comment.
|
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
What are the causes of a -11 error code using a ProSoft Modbus product?
Viewed 1 times since Mon, May 17, 2010
What Modbus address would we need to put into the MODSIM32 simulator if we specified on the MVI56-MCM device address to 8680HEX (-31104 decimal) when the MVI56-mcm is the slave?
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
What's the difference between Modbus ASCII and Modbus RTU?
Viewed 1 times since Wed, Mar 19, 2008
My RX light is on solid, what might that indicate?
Viewed 1 times since Fri, Jul 17, 2015
How can I detect the feedback status of individual command successful or failed?
Viewed 1 times since Wed, Nov 29, 2006
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 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
Defining the Slave ID when issuing Modbus Broadcast write commands
Viewed 1 times since Tue, Nov 28, 2006
|