# MQTT Client Driver in Kepserver 6.4

**URL:** <https://forum.inductiveautomation.com/t/mqtt-client-driver-in-kepserver-6-4/15930>\
**Category:** General Discussion\
**Created:** [November 8, 2017, 5:37pm UTC](https://forum.inductiveautomation.com/t/mqtt-client-driver-in-kepserver-6-4/15930 "2017-11-08T17:37:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cmisztur2](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/cmisztur2/32/4243_2.png) [@cmisztur2](https://forum.inductiveautomation.com/u/cmisztur2)\
**Post date:** [November 8, 2017, 5:37pm UTC](https://forum.inductiveautomation.com/t/mqtt-client-driver-in-kepserver-6-4/15930/1 "2017-11-08T17:37:21Z")

</div>

Just heard the good news today. Kepware is adding a MQTT driver to their driver suite, which means that ingesting data from MQTT devices will be possible with native Kepware and that data can be then exposed over OPC into Ignition.

---

<div class="post-metadata">

**Author:** ![dcamp](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@dcamp](https://forum.inductiveautomation.com/u/dcamp)\
**Post date:** [November 8, 2017, 6:15pm UTC](https://forum.inductiveautomation.com/t/mqtt-client-driver-in-kepserver-6-4/15930/2 "2017-11-08T18:15:18Z")

</div>

Cirrus Link MQTT engine is a seamless integration with Ignition!

Just so everybody understands the dedication Cirrus Link has with Ignition, I introduced the Maple System Hmi to Mr. Arlen Nippers because even though Maple Systems Hmi is a MQTT Publisher, Ignition did not understand the “Array Format” that Maple System was using to transmit the MQTT Protocol.

Once I was able to provide him with the data structure of the string being transmitted he “Immediately” re-wrote the MQTT driver for Ignition to interpret their MQTT DATA STRING!!

That is way above and beyond the call of duty!!!

---

<div class="post-metadata">

**Author:** ![dcamp](https://avatars.discourse-cdn.com/v4/letter/d/a88e4f/32.png) [@dcamp](https://forum.inductiveautomation.com/u/dcamp)\
**Post date:** [November 8, 2017, 6:24pm UTC](https://forum.inductiveautomation.com/t/mqtt-client-driver-in-kepserver-6-4/15930/3 "2017-11-08T18:24:26Z")

</div>

So if you need an “Edge of the Network” device that really is “Plug and Play” you might want to read on.

[Using Maple System Hmi with Ignition](https://www.maplesystems.com/cgi-bin/beimatdongon/TechNote/09075119.pdf)

---

<div class="post-metadata">

**Author:** ![AlThePal](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/althepal/32/3603_2.png) [@AlThePal](https://forum.inductiveautomation.com/u/AlThePal)\
**Post date:** [November 9, 2017, 7:17pm UTC](https://forum.inductiveautomation.com/t/mqtt-client-driver-in-kepserver-6-4/15930/4 "2017-11-09T19:17:09Z")

</div>

When we created our own edge of network device we linked it back to Ignition using MQTT as the data transmission protocol (the part it’s meant for!) and then wrote an MQTT to OPC bridge which ran on the Ignition server. This allowed us to integrate with Ignition without the hassle of writing drivers or the expense of purchasing an off the shelf solution.

I like MQTT - it’s simple and efficient over the network - but it’s not automatically better than established standards like OPCUA. Current MQTT offerings look too expensive for what they are.