| 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.
|
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
Do any Prosoft modules support Modbus UDP?
Viewed 1 times since Mon, Aug 24, 2015
How do I read/write Modbus binary data?
Viewed 1 times since Wed, Nov 29, 2006
How can I detect the feedback status of individual command successful or failed?
Viewed 1 times since Wed, Nov 29, 2006
Why are my PLX gateway modbus serial commands not executing despite being enabled?
Viewed 1 times since Wed, Aug 12, 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
Defining the Slave ID when issuing Modbus Broadcast write commands
Viewed 1 times since Tue, Nov 28, 2006
How do you detect the individual Slave failure?
Viewed 1 times since Wed, Nov 29, 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
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
|

Add Comment