ticknert
Member
Hi all,
I've been working on a Modbus TCP project using ControlLogix for a few days now and am hitting a wall. Before I start, I would like to say that we've looked into the Prosoft and other 3rd party modules and the client would prefer to keep it all Rockwell for now.
I'm using the Modbus TCP sample code from Rockwell that ships with the default 4 connections. I'm testing on the first connection, 0, but have not been able to pull information out of the device (a GE Multilin 469). It appears that the socket opens and connects successfully, but then resets when the NoReplyCounter[0] reaches 10.
To me, this means that the connection succeeds but the Modbus device is not responding to the request for information from the 'master'. If anyone has some ideas on where to go from here, that would be great. It could be something as little as changing a bit or two, thank you in advance!
I've been working on a Modbus TCP project using ControlLogix for a few days now and am hitting a wall. Before I start, I would like to say that we've looked into the Prosoft and other 3rd party modules and the client would prefer to keep it all Rockwell for now.
I'm using the Modbus TCP sample code from Rockwell that ships with the default 4 connections. I'm testing on the first connection, 0, but have not been able to pull information out of the device (a GE Multilin 469). It appears that the socket opens and connects successfully, but then resets when the NoReplyCounter[0] reaches 10.
To me, this means that the connection succeeds but the Modbus device is not responding to the request for information from the 'master'. If anyone has some ideas on where to go from here, that would be great. It could be something as little as changing a bit or two, thank you in advance!