# The right drivers / OPC for Ignition sw

**URL:** <https://forum.inductiveautomation.com/t/the-right-drivers-opc-for-ignition-sw/17712>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [April 13, 2018, 7:25pm UTC](https://forum.inductiveautomation.com/t/the-right-drivers-opc-for-ignition-sw/17712 "2018-04-13T19:25:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Opillar](https://avatars.discourse-cdn.com/v4/letter/o/bbe5ce/32.png) [@Opillar](https://forum.inductiveautomation.com/u/Opillar)\
**Post date:** [April 13, 2018, 7:25pm UTC](https://forum.inductiveautomation.com/t/the-right-drivers-opc-for-ignition-sw/17712/1 "2018-04-13T19:25:03Z")

</div>

Hello, first of all please apologize mine english, I’m from Czech 🙂  
In our company we have a lot if different brands of PLC’s (S7-200, S7-300, S7-1200, S7-1500, Mitsch, AB RS 500, AB RS 5000, Omron, Beckhoff) - very very difficult situation.  
But … we would like to start with Ignition sw in order to provide remote monitoring, historian and all other add-ons of that sw.  
The very first issue comes with S7-200 because as far as I know Ignition has not direct driver and I think with Beckhoff it will be same story.  
The question is: Ignition can connect any 3rd party OPC-DA / UP server, and I found KepServerEx and Matrikon OPC supports all of your PLC’s brand.  
I alson found lot of tutorials how to connect KepServerEx with Ignition - is this kind of connection really better and seamless than Matrikon (for example). I would like to say that I’m in “looking around” phase, so if there is any better solution - I will appreciate that!! Thank!

---

<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:** [April 13, 2018, 7:27pm UTC](https://forum.inductiveautomation.com/t/the-right-drivers-opc-for-ignition-sw/17712/2 "2018-04-13T19:27:23Z")

</div>

You should be able to use some combination of our own drivers and Kepware to fill the gaps (S7-200, Mitsch?, older Beckhoff stuff that doesn’t have UA).

Technically any 3rd party OPC server that has a driver you need should work but Kepware would be my first choice.

---

<div class="post-metadata">

**Author:** ![Opillar](https://avatars.discourse-cdn.com/v4/letter/o/bbe5ce/32.png) [@Opillar](https://forum.inductiveautomation.com/u/Opillar)\
**Post date:** [April 13, 2018, 7:48pm UTC](https://forum.inductiveautomation.com/t/the-right-drivers-opc-for-ignition-sw/17712/3 "2018-04-13T19:48:03Z")

</div>

Hey Kevin, thanks for quick answer.

Assuming KepServerEx … they also offer separate driver for each brand of PLC. So then I probably have to make **some comparion** which scenario is better an makes better economic sense:

1. Ignition \<-\> KepserverEx \<-\> for each vendor separate driver
2. Ignition \<-\> use available vendor’s driver + use KepServerEx for fill gap as you suggested

right?

---

<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:** [April 13, 2018, 7:54pm UTC](https://forum.inductiveautomation.com/t/the-right-drivers-opc-for-ignition-sw/17712/4 "2018-04-13T19:54:57Z")

</div>

Yes you’ll have to do some accounting and testing to see what works best for you.