ModbusTCP OPC/UA Driver - ADAM-4572 ModbusRTU Gateway Connection Issues

Ignition
, ,
1

Hello,

I am attempting to read holding registers from an Advantech ADAM-4572 using the OPC/UA ModbusTCP driver to no avail. I am trying to establish a test setup before attempting field work, and I am not sure if my ADAM configuration, Ignition ModbusTCP driver configuration, or both are wrong.

Virtual Testing

ADAM-4572 Settings

Ignition OPC/UA ModbusTCP Driver Settings

Ignition OPC Tags

Wireshark diagnostics

  • ADAM is configured configured with static IP (.240). Wireshark indicates that communication is occurring between the Ignition server (.31) and ADAM (.240). Interestingly, Ignition sends ModbusTCP requests, and the ADAM returns TCP (not ModbusTCP) responses.

    image
    image1229×1086 165 KB

  • I used ModbusMaster to create a virtual ModbusTCP master to try to connect to the ADAM and got similar Wireshark results as above.

Does anyone have any ideas? Please let me know if you need more information or screenshots. Thank you.

1 Like
2

Start by modifying all of your tags' OPC Item Paths so the include a prefix of 1.. This sets the unit/slave id to 1, instead of the default of 0, which is virtually never correct when you're talking to a Modbus TCP to RTU Gateway.

e.g. [MyDevice]1.HR1

edit: 1, or whatever the actual slave address is supposed to be. Depends on how the serial device is configured.

3

I am on it! I will let you know what happens.

4

I set all of the tags with the format you mentioned ([ADAM]1.HR1). Example:

image
image1183×642 65.3 KB

Also, I double checked that my virtual ModbusSlave is set for ID: 1.

image
image1273×1368 190 KB

My tags are reading are still 'Bad' after the change. Since the virtual ModbusTCP master program is having similar issues, I think this is pointing to a configuration issue with my ADAM module, unless you see something else off with my Ignition settings.

5

Ignition settings look fine, if other masters also can't read it's probably a problem with the ADAM like you suggest.

I'll leave you with 2 other pieces of advice for the Ignition side:

  • don't be tempted to use the Address Map page, just define the tags like you're already doing
  • disable all but 1 tag you know exists until you have established comms and a successful read
1 Like
6

Thanks for the advice and immediate response! I will disable all but one tag and diagnose the ADAM settings from here and report back if I find anything.

7

This is just a follow-up for anyone else trying to get the ADAM-4572 working.

I was unable to get the ADAM-4572 to communicate to the Ignition ModbusTCP OPC/UA driver after many attempts. However, after configuring a Prosoft PLX31-MBTCP-MBS Modbus Gateway, the only setting that I had to change on the Ignition ModbusTCP driver was the IP address. The Prosoft module connected immediately, and it stayed connected.

I have seen other Advantech Modbus modules successfully connected to Ignition in some facilities, but I was unable to get the ADAM-4572 to work.

8

Looks the device is passing the rtu data over tcp. The documentation of the device doesn't look like its actually implementing a modbus server where you can map register over tcp. You mentioned that you were trying the modbus Tcp driver. The wire shark indicates tcp messages and the manual only lets you dedicate a port for tcp messages for that device. Did you try the Modbus RTU over TCP driver? I know this is a little late but I would give that driver a try.

1 Like