# TCP/IP Driver IFM 3D Sensor

**URL:** <https://forum.inductiveautomation.com/t/tcp-ip-driver-ifm-3d-sensor/99130>\
**Category:** Ignition\
**Tags:** perspective\
**Created:** [November 26, 2024, 3:54pm UTC](https://forum.inductiveautomation.com/t/tcp-ip-driver-ifm-3d-sensor/99130 "2024-11-26T15:54:14Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zachary\_Kacel1](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@Zachary\_Kacel1](https://forum.inductiveautomation.com/u/Zachary_Kacel1)\
**Post date:** [November 26, 2024, 3:54pm UTC](https://forum.inductiveautomation.com/t/tcp-ip-driver-ifm-3d-sensor/99130/1 "2024-11-26T15:54:14Z")

</div>

I have a question regarding Ignitions TCP/IP driver.

I am trying to connect IFM's 00D303 3D Sensor directly to Ignition via the TCP/IP drive, and I was finally able to get data. I noticed when I run the sensor in continuous mode the tag value will bounce from my good data to a long string **0000L0000000310000** what is this string and why does my tag value flip to this?

Also what would be the best way to parse out my data to be used? I was thinking about putting a change script on that tag and whenever it changes and sees **star;** and **;stop** I just write what is in between to another tag.  
**star;0.711;0.921;stop**

Thanks,

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [November 26, 2024, 3:56pm UTC](https://forum.inductiveautomation.com/t/tcp-ip-driver-ifm-3d-sensor/99130/2 "2024-11-26T15:56:18Z")

</div>

You probably have the message framing (delimiter) set up incorrectly. "Packet Based" for TCP is a meaningless option, and it ends up just dumping whatever happens to come back from a Socket read call into the tag.

The other possibility is the data is changing too fast for the TCP driver, or some combination of both.

---

<div class="post-metadata">

**Author:** ![Zachary\_Kacel1](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@Zachary\_Kacel1](https://forum.inductiveautomation.com/u/Zachary_Kacel1)\
**Post date:** [November 26, 2024, 3:59pm UTC](https://forum.inductiveautomation.com/t/tcp-ip-driver-ifm-3d-sensor/99130/3 "2024-11-26T15:59:00Z")

</div>

Packet Based is the only one I was able to get data out of the device.

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

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [November 26, 2024, 4:02pm UTC](https://forum.inductiveautomation.com/t/tcp-ip-driver-ifm-3d-sensor/99130/4 "2024-11-26T16:02:52Z")

</div>

This driver is only suitable for simple TCP data sources that sends ASCII/text messages where a frame can be determined by a fixed length or a fixed delimiter.

---

<div class="post-metadata">

**Author:** ![Zachary\_Kacel1](https://avatars.discourse-cdn.com/v4/letter/z/ea666f/32.png) [@Zachary\_Kacel1](https://forum.inductiveautomation.com/u/Zachary_Kacel1)\
**Post date:** [November 26, 2024, 4:03pm UTC](https://forum.inductiveautomation.com/t/tcp-ip-driver-ifm-3d-sensor/99130/5 "2024-11-26T16:03:56Z")

</div>

Ok so I can get data if I use the character Delimiter Type and **star** as my Message Delimiter, but now that random string is at the end of my value. I should be able to use this though, and parse out what I need from the string.  
**;0.711;0.921;stop0000L0000000270000**

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/f/5f3232e82b4a4175122598aa8bab498db39c71d2.png)

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