# \[CHI\] TCP Binary Driver - A binary mode TCP OPC-UA driver

**URL:** <https://forum.inductiveautomation.com/t/chi-tcp-binary-driver-a-binary-mode-tcp-opc-ua-driver/6226>\
**Category:** 3rd Party Modules\
**Created:** [April 14, 2013, 7:34pm UTC](https://forum.inductiveautomation.com/t/chi-tcp-binary-driver-a-binary-mode-tcp-opc-ua-driver/6226 "2013-04-14T19:34:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [April 14, 2013, 7:34pm UTC](https://forum.inductiveautomation.com/t/chi-tcp-binary-driver-a-binary-mode-tcp-opc-ua-driver/6226/1 "2013-04-14T19:34:33Z")

</div>

I created a little (at least it startet little) OPC-UA driver module.

This driver connects to devices that send messages with binary data. The message format is configurable for each device.  
This driver does not poll data but expects the connected device to send messages on its own.

Possible applications are:  
-Connect devices that are not supported by default drivers but allow custom TCP-IP connection.  
-Log data from devices when an exact source timestamp is needed.  
-Log data from devices that use internal data buffering.

I actually like the idea of IA’s free OPC-UA server, so this module is also free.

Though this module has been tested, i can not guarantee that it will work as expected in yout application. Feel free to post problems to the feedback forum.  
[TCP Binary Driver-module-1.6.0.modl](https://us1.discourse-cdn.com/inductiveautomation/original/2X/2/22148edd13ea0b6c30ef5040565c3383212dc55f.modl) (231 KB)  
[TCP Binary Driver-module-1.5.0.modl](https://us1.discourse-cdn.com/inductiveautomation/original/2X/7/74cda6ccf65bb9f6eecfea13712cc0f43d69398e.modl) (229 KB)  
[TCPBinaryDriver-Help.pdf](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d45b5371935200230d8bef6f188d5b39e4cc6ff8.pdf) (128 KB)

---

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [July 21, 2013, 2:34pm UTC](https://forum.inductiveautomation.com/t/chi-tcp-binary-driver-a-binary-mode-tcp-opc-ua-driver/6226/2 "2013-07-21T14:34:18Z")

</div>

New module version 1.6.0 for Ignition 7.6.

---

<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:** [July 23, 2013, 3:10pm UTC](https://forum.inductiveautomation.com/t/chi-tcp-binary-driver-a-binary-mode-tcp-opc-ua-driver/6226/3 "2013-07-23T15:10:32Z")

</div>

Did you have any problems modifying your driver(s) to accommodate the driver API changes in the UA module between 1.5 and 1.6?

---

<div class="post-metadata">

**Author:** ![chi](https://avatars.discourse-cdn.com/v4/letter/c/0ea827/32.png) [@chi](https://forum.inductiveautomation.com/u/chi)\
**Post date:** [July 23, 2013, 6:49pm UTC](https://forum.inductiveautomation.com/t/chi-tcp-binary-driver-a-binary-mode-tcp-opc-ua-driver/6226/4 "2013-07-23T18:49:50Z")

</div>

> [@Kevin.Herron](#):
>
> Did you have any problems modifying your driver(s) to accommodate the driver API changes in the UA module between 1.5 and 1.6?

No, the new API is nice. The new subscription and driver state systems actually make things easier. In the old API i had to fake a connection to get my subscriptions.  
Only the hidden update to Wicket 6 caused some trouble, as i use a quite heavy configuration interface. It would be helpful if the Wicket javadocs could be merged with the API's javadoc.