Hello All,
There is this always one last issue before getting everything to work and I am having a similar scenario.
So I got this module from GridConnect (Xport-EIP-MB), this is a EtherNet/IP to Modbus converter. We have designed a Circuit to implement this adaptor and our Modbus Slave device is a Modbus RTU. Xport module has a config file where you can set the following parameters and I have assigned them correctly to match the Slave ;
Modbus Type : RTU
Modbus Slave Address : 1
Modbus Baud Rate : 9600
Modbus Data Bits : 8
Modbus Stop Bits : 1
Modbus Parity :Even
I have confirmed that when mapping the Modbus to EtherNet/IP mapping through explicit messaging, the Slave responds with a EtherNet/IP success response . This confirms that the Modbus master in the Xport queries the slave and the slave responds.
This is all good, now finally I was to read the modbus slave register values through EtherNet/IP (What this module supposed to do). I sets up a EtherNet/IP connection originator (ControlLogix5561 PLC) and adds the Xport module as a generic EtherNet/IP module. The PLC establishes a connection to the Xport module and I can't see any register data on the Input control Tags.
I verified that the Modbus slave has vaild data by polling the slave with a serial Modbus master, so there is no issues in the slave register end.
With the active connection (ControlLogix5561) on to the Xport we observed the link (Data Out pin of the Xport) to the Modbus slave through a Oscilloscope to see any Modbus slave polling and we are not seeing the Xport polling the Modbus slave or sending any queries. According to the Xport manual once a EtherNet/IP connection is established the modbus master within the Xport will poll the slave every 100mS, but we are not seeing any activity.
So this can be two issues, there is a compatibility issue between ControlLogix5561 and the Xport (Could be firmware, etc) even though there is an active connection to Xport in the IO branch, but the Xport does not see a valid EtherNet/IP connection. The second issue could be there is a firmware error within the Xport for not polling the slave (Xport is 3.3V TTL and we have pulled this to 5V TTL to the Modbus Slave, because Modbus slave end had a 5V RS485 serial connection for Modbus Serial )
it is much appreciated if anyone who has encountered a similar issues, put a helping hand out
Thank you very much
There is this always one last issue before getting everything to work and I am having a similar scenario.
So I got this module from GridConnect (Xport-EIP-MB), this is a EtherNet/IP to Modbus converter. We have designed a Circuit to implement this adaptor and our Modbus Slave device is a Modbus RTU. Xport module has a config file where you can set the following parameters and I have assigned them correctly to match the Slave ;
Modbus Type : RTU
Modbus Slave Address : 1
Modbus Baud Rate : 9600
Modbus Data Bits : 8
Modbus Stop Bits : 1
Modbus Parity :Even
I have confirmed that when mapping the Modbus to EtherNet/IP mapping through explicit messaging, the Slave responds with a EtherNet/IP success response . This confirms that the Modbus master in the Xport queries the slave and the slave responds.
This is all good, now finally I was to read the modbus slave register values through EtherNet/IP (What this module supposed to do). I sets up a EtherNet/IP connection originator (ControlLogix5561 PLC) and adds the Xport module as a generic EtherNet/IP module. The PLC establishes a connection to the Xport module and I can't see any register data on the Input control Tags.
I verified that the Modbus slave has vaild data by polling the slave with a serial Modbus master, so there is no issues in the slave register end.
With the active connection (ControlLogix5561) on to the Xport we observed the link (Data Out pin of the Xport) to the Modbus slave through a Oscilloscope to see any Modbus slave polling and we are not seeing the Xport polling the Modbus slave or sending any queries. According to the Xport manual once a EtherNet/IP connection is established the modbus master within the Xport will poll the slave every 100mS, but we are not seeing any activity.
So this can be two issues, there is a compatibility issue between ControlLogix5561 and the Xport (Could be firmware, etc) even though there is an active connection to Xport in the IO branch, but the Xport does not see a valid EtherNet/IP connection. The second issue could be there is a firmware error within the Xport for not polling the slave (Xport is 3.3V TTL and we have pulled this to 5V TTL to the Modbus Slave, because Modbus slave end had a 5V RS485 serial connection for Modbus Serial )
it is much appreciated if anyone who has encountered a similar issues, put a helping hand out
Thank you very much