# Omron Ethernet driver

**URL:** <https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734>\
**Category:** Ignition\
**Created:** [June 20, 2013, 7:18am UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734 "2013-06-20T07:18:15Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![pat.stave](https://avatars.discourse-cdn.com/v4/letter/p/96bed5/32.png) [@pat.stave](https://forum.inductiveautomation.com/u/pat.stave)\
**Post date:** [June 20, 2013, 7:18am UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/1 "2013-06-20T07:18:15Z")

</div>

Do we need more Ignition drivers?  
[poll]

- Yes
- No  
[/poll]  
Messing with the Omron DCOM OPC-server (and OPC-DCOM in general) is a true pain in the ass 🙂  
Unstable, low performance, and poor UI are some of the keywords.

My biggest wish for Ignition would be an driver for Omron PLCs. These PLCs are vastly popular in Europe, we alone have around 50 CPUs inhouse.  
I think an Omron driver could possibly open up a whole new market in Europe.

Newer Omron PLCs support Ethernet/IP and FINS-TCP. Older PLCs only support FINS-TCP.  
These protocols are very well documented by Omron, and a lot of people have written small PC-programs using FINS (have a look at [MrPLC.com](http://MrPLC.com)).

Is this a driver Inductive Automation would consider to implement? (please ![:thumb_right:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/2026e28c0c425034352c1b75807edf956adc75f4.gif ":thumb\_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:** [June 20, 2013, 2:12pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/2 "2013-06-20T14:12:56Z")

</div>

Noted. It’s been on our some-day list for a while, but the demand hasn’t been high enough yet for anything to happen with it.

I’ve looked at the protocol though, and you’re right, the documentation is great and it doesn’t seem overly complex.

Maybe somebody will develop a driver and put it in the module store? ![8)](https://us1.discourse-cdn.com/inductiveautomation/original/1X/587d7fe0d6822f36e81815ab06aa7164e9d2e057.gif "Cool")

---

<div class="post-metadata">

**Author:** ![dschmidgall](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@dschmidgall](https://forum.inductiveautomation.com/u/dschmidgall)\
**Post date:** [July 22, 2013, 8:21pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/3 "2013-07-22T20:21:26Z")

</div>

Any update on the Omron driver? Omron is the only PLC we install in new applications and we are waiting to try ignition out.  
Just wondering where its at on the “some-day list”.

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:** [July 22, 2013, 8:22pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/4 "2013-07-22T20:22:27Z")

</div>

Things on the ‘some-day’ list aren’t ordered, it’s just on there. Don’t hold your breath on this one though - it’s especially low since there’s a work-around for communicating with Omron stuff via Modbus.

Don’t get me wrong - I’d like to implement it… but there’s a million other things that need implementing as well 😮

---

<div class="post-metadata">

**Author:** ![pat.stave](https://avatars.discourse-cdn.com/v4/letter/p/96bed5/32.png) [@pat.stave](https://forum.inductiveautomation.com/u/pat.stave)\
**Post date:** [July 23, 2013, 1:40pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/5 "2013-07-23T13:40:39Z")

</div>

Just a comment about Modbus on Omron:  
Modbus is only supported using the ETN21 option card, or the OEM CPIL-E PLC.  
The ETN21-card is rarely used, as it is even more expensive than a complete CPU with built in Ethernet. A lot of the Omron PLCs have built in ethernet, but it only supports FINS and Ethernet/IP.

The ETN21 card is used when one of the following is required;

- TCP/UDP socket communications
- FTP / Web-services
- Email services.
- Modbus TCP.

Kevin; we would be happy to donate a Omron PLC if this could help 🙂

---

<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, 2:58pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/6 "2013-07-23T14:58:27Z")

</div>

[quote=“pat.stave”]Just a comment about Modbus on Omron:  
Modbus is only supported using the ETN21 option card, or the OEM CPIL-E PLC.  
The ETN21-card is rarely used, as it is even more expensive than a complete CPU with built in Ethernet.[/quote]

Yuck! Didn’t realize that.

---

<div class="post-metadata">

**Author:** ![Kyle\_Chase](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@Kyle\_Chase](https://forum.inductiveautomation.com/u/Kyle_Chase)\
**Post date:** [August 9, 2013, 6:42am UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/7 "2013-08-09T06:42:46Z")

</div>

We would like to see this driver as well.

---

<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:** [August 9, 2013, 3:48pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/8 "2013-08-09T15:48:57Z")

</div>

Alright alright. Noted guys. Still can’t make any promises. Our development timeline is pretty jam-packed.

---

<div class="post-metadata">

**Author:** ![pat.stave](https://avatars.discourse-cdn.com/v4/letter/p/96bed5/32.png) [@pat.stave](https://forum.inductiveautomation.com/u/pat.stave)\
**Post date:** [August 22, 2013, 7:52pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/9 "2013-08-22T19:52:02Z")

</div>

Just found this jar: [avineas.org/index.php?page=fins](http://www.avineas.org/index.php?page=fins)

Would this be of any help?

---

<div class="post-metadata">

**Author:** ![andor.izsak](https://avatars.discourse-cdn.com/v4/letter/a/ee59a6/32.png) [@andor.izsak](https://forum.inductiveautomation.com/u/andor.izsak)\
**Post date:** [September 30, 2017, 5:49pm UTC](https://forum.inductiveautomation.com/t/omron-ethernet-driver/6734/10 "2017-09-30T17:49:35Z")

</div>

Well, this may be a total deal breaker for us. A fairly large purchase over the next year. We want to avoid any and all sorts of third party or Omron opotions to have our CJ series PLCs connected. And we have a boat load. Kepware is only UDP with FINS. TCP is prefered. Plus, the reason we want to go with IGNITION becuase it wouldnt require the spaghetti of OPC servers to get our sites to work. Please get on topsof this. We need FINS TCP, otherwise we will have to hold off our purchase. In Europe the CJ series PLCS are the most popular at the moment.
