# Ignition uses the NJ Driver and FINS/TCP to read Omron PLC's tags, which are slow to read

**URL:** <https://forum.inductiveautomation.com/t/ignition-uses-the-nj-driver-and-fins-tcp-to-read-omron-plcs-tags-which-are-slow-to-read/92072>\
**Category:** Ignition\
**Created:** [June 19, 2024, 10:17am UTC](https://forum.inductiveautomation.com/t/ignition-uses-the-nj-driver-and-fins-tcp-to-read-omron-plcs-tags-which-are-slow-to-read/92072 "2024-06-19T10:17:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![NobleFox](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/noblefox/32/63982_2.png) [@NobleFox](https://forum.inductiveautomation.com/u/NobleFox)\
**Post date:** [June 19, 2024, 10:17am UTC](https://forum.inductiveautomation.com/t/ignition-uses-the-nj-driver-and-fins-tcp-to-read-omron-plcs-tags-which-are-slow-to-read/92072/1 "2024-06-19T10:17:21Z")

</div>

Hello sir~~  
when I use ignition NJ Driver or FINS/TCP to read Omron PLC tags, the reading speed is very slow. When values of tags in PLC change, it takes 2-3s for ignition to refresh the latest values of tags. Is there any solution to this problem? The following figures show ignition gateway information when using NJ Driver and FINS/TCP to read Omron PLC tags respectively

 ![nj](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/2/b2ec09529634f38ef1adfc9b09d80947d34c6e38.png)  
 ![fins](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/b/9b1c84e477911aae1a2cf54503d4a2e46fc19e8a.png)

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [June 19, 2024, 10:43am UTC](https://forum.inductiveautomation.com/t/ignition-uses-the-nj-driver-and-fins-tcp-to-read-omron-plcs-tags-which-are-slow-to-read/92072/2 "2024-06-19T10:43:39Z")

</div>

thats some high overload. **reduce** the polling speed/ amount of stuff monitor, 1700/2000 seems way to much...

anything above 100% is bad, and you are at 700% xd Your plc/connection cant handle this much requests at this speed

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 19, 2024, 11:29am UTC](https://forum.inductiveautomation.com/t/ignition-uses-the-nj-driver-and-fins-tcp-to-read-omron-plcs-tags-which-are-slow-to-read/92072/3 "2024-06-19T11:29:56Z")

</div>

> [@NobleFox](#):
>
> Is there any solution to this problem?

Yes, this:

> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190):
>
> Automation Professionals is pleased to announce its latest EtherNet/IP Communications Suite driver module, a major upgrade to its EtherNet/IP Class1 Communications module, as a Public Beta. As of April 15, 2023, this is now a Production Release. The primary new feature is its new Generic EtherNet/IP Client Driver, a drop-in replacement for IA's Logix V21+ driver and its Omron NJ/NX driver. It does work with older Logix processors, and also works with Rockwell's MicroLogix 8xx family (ethernet…

One of my clients' miseries with the performance of the native driver was the motivation to figure out how to do better.

> [@victordcq](#):
>
> 1700/2000 seems way to much...

Tens of thousands is usually fine with my alternate driver.

---

<div class="post-metadata">

**Author:** ![victordcq](https://avatars.discourse-cdn.com/v4/letter/v/f6c823/32.png) [@victordcq](https://forum.inductiveautomation.com/u/victordcq)\
**Post date:** [June 19, 2024, 12:35pm UTC](https://forum.inductiveautomation.com/t/ignition-uses-the-nj-driver-and-fins-tcp-to-read-omron-plcs-tags-which-are-slow-to-read/92072/4 "2024-06-19T12:35:12Z")

</div>

Woh those are some impressive number improvments

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [June 19, 2024, 12:37pm UTC](https://forum.inductiveautomation.com/t/ignition-uses-the-nj-driver-and-fins-tcp-to-read-omron-plcs-tags-which-are-slow-to-read/92072/5 "2024-06-19T12:37:58Z")

</div>

> [@victordcq](#):
>
> improvments

This user report is gratifying:

> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/19):
>
> Tested driver with Omron NX102-1100, almost 4000 tags: Ignition NX driver: Sampling interval 13 600 ms This driver v2 (EthernetIP Class 1 Communications-2.0.1.230022328-v81), sampling interval less than 1000 ms, load factor 21%
