# IP to Serial Device - Advice needed

**URL:** <https://forum.inductiveautomation.com/t/ip-to-serial-device-advice-needed/11763>\
**Category:** Ignition\
**Created:** [June 1, 2016, 2:45pm UTC](https://forum.inductiveautomation.com/t/ip-to-serial-device-advice-needed/11763 "2016-06-01T14:45:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tbackus](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tbackus/32/5091_2.png) [@tbackus](https://forum.inductiveautomation.com/u/tbackus)\
**Post date:** [June 1, 2016, 2:45pm UTC](https://forum.inductiveautomation.com/t/ip-to-serial-device-advice-needed/11763/1 "2016-06-01T14:45:16Z")

</div>

Working on a project with some equipment hooked up serially to an Ethernet Enabled com box.  
[comtrol.com/ethernet-device- … ort-db9-1e](http://www.comtrol.com/ethernet-device-servers/devicemaster-rts/devicemaster-rts-2port-db9-1e)

I have done local Serial control on a Client running Ignition, but I need this to be independent of a client.

What’s my path to get Serial Data from the device into Ignition?? TCP or UDP driver? and decode the packet? Load the serial ethernet driver to a client and leave the client up all the time?? (Least Preferred) or is there a component or scripting I can use to grab the data and parse it into tags every few seconds??

Rather than re-invent the wheel, I thought I would post here first to see what others have done.

Thanks.
