Dataman 360 series over Ethernet

I didn't see anything that would help with this, so I wanted to post in case it may help someone down the road.
Previously, I had seen several topics related to capturing a dataman scanner output using Modbus TCP.

Went to config; OPCUA; Devices; Create new device.
TCP Driver; Next

Give it a name, IP, and Port; next.

Open the designer.
Under tag browser hit the drop down;

Under the tag editor set the Name, Data type needed, OPC server, and correct item path. Scan data on mine was under 23_ Message

Once complete you can verify with the OPC quick client.

Sorry it's very picture heavy, but I thought it may prove useful as I didn't see a lot of information on the subject without going through Modbus TCP.

1 Like

I edited your title slightly, Ethernet/IP is a completely different driver system to TCP on ethernet.

Sorry it's very picture heavy, but I thought it may prove useful as I didn't see a lot of information on the subject without going through Modbus TCP.

I think it's easy to follow with the images, there are a large range of skill levels using Ignition, so the easier the better.

Thanks for the catch. Should have labeled it over TCP Driver or as TCP device. Multi-tasking in too many directions :slight_smile:

1 Like

Update;
While the Device still shows connected I wasn't receiving anything to the memory tag I setup.
I played around with the gateway script- tag change event's logging functions and couldn't tell that the tag was ever changing.
Played with system.opc.readValues vs system.tag.read as well.
Solution included modifying the OPCUA device inactivity timeout. Once I did this, if it didn't see a change for X amount of time it would reconnect.

Never saw an error on the wrapper or dashboard. Device remained connected and "good" by all accounts. The only way I could tell it wasn't running was to putty into the scanner and watch the output while the tag in Ignition did not update. If I find any additional info I will post it.