# Plc update tag late **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [December 17, 2025, 2:47pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868 "2025-12-17T14:47:18Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [December 17, 2025, 2:47pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/1 "2025-12-17T14:47:18Z")
Hi Team, We are experiencing an issue where pressing a button to toggle a motor ON/OFF causes a noticeable delay—sometimes around 2 seconds, and sometimes even longer. The PLC we are using is an **Omron** device. Does anyone have any suggestions for how to reduce this delay or improve the responsiveness? Below is the code currently used on the button’s `onClick` event: ```python def runAction(self, event): tagPath = "[default]_Plc_sch_/Sel_agt_pol_01" currentValue = system.tag.readBlocking([tagPath])[0].value newValue = not currentValue system.tag.writeBlocking([tagPath], [newValue]) ``` Thanks. ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [December 17, 2025, 3:12pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/2 "2025-12-17T15:12:12Z")
Please see [Wiki - how to post code on this forum](https://forum.inductiveautomation.com/t/wiki-how-to-post-code-on-this-forum/77831). You can then edit to fix the code block formatting. Thanks. ---
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [December 17, 2025, 3:15pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/3 "2025-12-17T15:15:13Z")
It is done. Now please answer the real question. ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [December 17, 2025, 3:24pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/4 "2025-12-17T15:24:47Z")
> Blocking tag writes are safe in tag event scripts only for memory tags. Any other kind of tag will delay for confirmation of the write. > [@Best practices and pitfalls with Tag Event Scrips](https://forum.inductiveautomation.com/t/best-practices-and-pitfalls-with-tag-event-scrips/99355): > > In summary, my question is: What is best practices, and what to avoid when writing Tag Event Scripts? Background and more details regarding question: From what I have read, the Tag Event Scripts are running in fixed size thread pool (default 3 threads). This would mean that if you have multiple Tag Event Scripts that does slow/blocking operations, it could block any other tag event scripts from running. This would presumably mean that running e.g. network calls like OPC calls, or other poten… ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [December 17, 2025, 3:28pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/5 "2025-12-17T15:28:55Z")
You should be binding your desired tag instead of using a script to do read/write blocking. This should be more efficient and performant than the way you're doing it. ---
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [December 17, 2025, 3:35pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/6 "2025-12-17T15:35:23Z")
i have tried to bind with toggle switch as you advised but result are same. We have tried updating the Timeout in the Gateway; however, when reducing it from the default 2000 ms to 1000 ms, the PLC did not respond at all. ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [December 17, 2025, 3:36pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/7 "2025-12-17T15:36:28Z")
Go to Gateway webpage, status, devices, your Omron. It sounds like it is overloaded. Post a screenshot. ---
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [December 17, 2025, 3:40pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/8 "2025-12-17T15:40:42Z")
You are right. now what is the solution? ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/6/36c801089e73e56f14868a3fb6851b373b97344f.png) ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [December 17, 2025, 3:41pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/9 "2025-12-17T15:41:44Z")
Reduce the poll rate on tags that don’t need to be fast. Split them into separate groups. However, only 17 items, that is a wimpy CPU, or you have severe network latency issues. I’ve never used Omron with Ignition, so can’t propose much further. Phil Turmel Automation Pro’s has an alternate driver I think, which may yield better performance. ---
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [December 17, 2025, 3:48pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/10 "2025-12-17T15:48:08Z")
@pturmel ”Phil Turmel Automation Pro’s has an alternate driver I think, which may yield better performance.” Could you help us resolve this issue? ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [December 17, 2025, 3:52pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/11 "2025-12-17T15:52:06Z")
> [@Automation Professionals Driver Questions - Omron NJ](https://forum.inductiveautomation.com/t/automation-professionals-driver-questions-omron-nj/89310): > > Alright, so a few questions on this, and I am new to using this driver, and am currently running in trial mode. We are connecting using the Class 3 generic EIP driver. First item, is that it seem like the connection is having trouble from time to time, and I am getting some connection rejection issues intermittently. What CPU are you using? ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [December 17, 2025, 3:57pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/12 "2025-12-17T15:57:18Z")
> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/1): > > - Fixes the near total lack of optimization for Omron NJ/NX processors. Substantial performance gains are likely. > [@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… ---
**Author:** ![TechEnlive](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@TechEnlive](https://forum.inductiveautomation.com/u/TechEnlive)\ **Post date:** [December 17, 2025, 3:57pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/13 "2025-12-17T15:57:43Z")
The CPU of PLC is **NX102-1220** ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/0/908573bce6afe864148113f56e73f9101e4189b9.png) ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [December 17, 2025, 3:58pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/14 "2025-12-17T15:58:41Z")
> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/1): > > Fixes the near total lack of optimization for Omron NJ/_ **NX** _ processors. Substantial performance gains are likely. Then you’re in luck. ---
**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:** [December 17, 2025, 4:00pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/15 "2025-12-17T16:00:07Z")
The NX102 also has onboard OPC UA support, which might be another direction to explore. ---
**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\ **Post date:** [December 17, 2025, 4:56pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/16 "2025-12-17T16:56:00Z")
> [@TechEnlive](#): > > Now please answer the real question. Please remember that we're almost all volunteers on this forum, giving freely of our time and expertise. This sort of post doesn't entice me towards offering support. ---
**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:** [December 17, 2025, 7:27pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/17 "2025-12-17T19:27:55Z")
> [@Kevin.Herron](#): > > onboard OPC UA support From a few reports, it isn't much faster than the IA native driver. I've had difficulties with the NX family reported with my driver, but without any details to poke at. (I do not have an NX in my lab, so a lab rat would be helpful.) Those who have used my driver have reported performance in the 30x to 50x range compared to the IA driver, which correlates well with my experience with the NJ501 in my lab. Also note that my driver auto-browses the PLC--no export from Sysmac Studio required. (With a few nuances described in my user manual.) ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [December 19, 2025, 12:20pm UTC](https://forum.inductiveautomation.com/t/plc-update-tag-late/112868/18 "2025-12-19T12:20:53Z")
This isn’t relevant to button action scripts > [@Matrix\_Engineering](#): > > Blocking tag writes are safe in tag event scripts only for memory tags. Any other kind of tag will delay for confirmation of the write.