# Dataman 360 series over Ethernet

**URL:** <https://forum.inductiveautomation.com/t/dataman-360-series-over-ethernet/101646>\
**Category:** Ignition\
**Created:** [January 30, 2025, 8:30pm UTC](https://forum.inductiveautomation.com/t/dataman-360-series-over-ethernet/101646 "2025-01-30T20:30:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![RonB](https://avatars.discourse-cdn.com/v4/letter/r/ce73a5/32.png) [@RonB](https://forum.inductiveautomation.com/u/RonB)\
**Post date:** [January 30, 2025, 8:30pm UTC](https://forum.inductiveautomation.com/t/dataman-360-series-over-ethernet/101646/1 "2025-01-30T20:30:17Z")

</div>

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.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/6/46a6274e857996a055ccb597fbfa0114afe48254.png)

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

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/0/d033e58dbce25aae83b129a8a62ecf00d3425595.png)

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

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/b/ebe9ab60735cbf09626fbb426638ae1c7f6748af.png)

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

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/0/e0d3f8892ac73725a35929e7495ff5da3beb9892.png)

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

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/7/3708176f9c631f4dcda0840a1a57b408fb7922c6.png)

Once complete you can verify with the OPC quick client.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/3/8377277cfce9098e1573fe3d9dc944c33612162a.png)

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.

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [January 30, 2025, 8:34pm UTC](https://forum.inductiveautomation.com/t/dataman-360-series-over-ethernet/101646/2 "2025-01-30T20:34:48Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![RonB](https://avatars.discourse-cdn.com/v4/letter/r/ce73a5/32.png) [@RonB](https://forum.inductiveautomation.com/u/RonB)\
**Post date:** [January 30, 2025, 8:36pm UTC](https://forum.inductiveautomation.com/t/dataman-360-series-over-ethernet/101646/3 "2025-01-30T20:36:55Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![RonB](https://avatars.discourse-cdn.com/v4/letter/r/ce73a5/32.png) [@RonB](https://forum.inductiveautomation.com/u/RonB)\
**Post date:** [February 4, 2025, 4:14pm UTC](https://forum.inductiveautomation.com/t/dataman-360-series-over-ethernet/101646/4 "2025-02-04T16:14:17Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [February 4, 2025, 9:36pm UTC](https://forum.inductiveautomation.com/t/dataman-360-series-over-ethernet/101646/5 "2025-02-04T21:36:26Z")

</div>

This is definitely the issue with the TCP driver, there is no connection monitoring, so the only way to validate the connection is even working is to wait for periodic data or restart the connection regularly.
