# How best to optimize for real time jog buttons?

**URL:** <https://forum.inductiveautomation.com/t/how-best-to-optimize-for-real-time-jog-buttons/59518>\
**Category:** General Discussion\
**Tags:** ignition81, perspective\
**Created:** [May 12, 2022, 7:02pm UTC](https://forum.inductiveautomation.com/t/how-best-to-optimize-for-real-time-jog-buttons/59518 "2022-05-12T19:02:32Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![peter](https://avatars.discourse-cdn.com/v4/letter/p/278dde/32.png) [@peter](https://forum.inductiveautomation.com/u/peter)\
**Post date:** [May 13, 2022, 4:24pm UTC](https://forum.inductiveautomation.com/t/how-best-to-optimize-for-real-time-jog-buttons/59518/14 "2022-05-13T16:24:15Z")

</div>

> [@pturmel](#):
>
> Try using `system.opc.write**()` direct to the OPC item paths instead of tag writes. Eliminate the tag system as a source of uncertainty.

I just tried this and the integrity of the system went up significantly. I wasn't able to cause a latch up no matter how fast I clicked the button. And the clock count in the PLC matched my HMI click count.

Now I just need to figure out extracting the server and path from the tag that was bound to the control (because I do not want to be manually configuring that stuff)

---

_[View the full topic](https://forum.inductiveautomation.com/t/how-best-to-optimize-for-real-time-jog-buttons/59518)._