# Best way to turn boolean tag value high every 5 seconds?

**URL:** <https://forum.inductiveautomation.com/t/best-way-to-turn-boolean-tag-value-high-every-5-seconds/50123>\
**Category:** Ignition\
**Created:** [August 19, 2021, 8:05pm UTC](https://forum.inductiveautomation.com/t/best-way-to-turn-boolean-tag-value-high-every-5-seconds/50123 "2021-08-19T20:05:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![zacht](https://avatars.discourse-cdn.com/v4/letter/z/ea5d25/32.png) [@zacht](https://forum.inductiveautomation.com/u/zacht)\
**Post date:** [August 19, 2021, 8:16pm UTC](https://forum.inductiveautomation.com/t/best-way-to-turn-boolean-tag-value-high-every-5-seconds/50123/2 "2021-08-19T20:16:52Z")

</div>

Smart people suggest that it's good practice not to write to one tag from two sources (Ignition and PLC). Example:

> [@Heartbeat script having effects system wide](https://forum.inductiveautomation.com/t/heartbeat-script-having-affects-system-wide/21689/10):
>
> Eeek! No. Don’t write from two directions. PLC should count and roll over. The low word of a PLC clock is fine. Ignition should count and roll over in its own timer event, writing to the appropriate OPC tag. Or write the low bits of Ignition’s millisecond time to the OPC tag. It isn’t important what the value is, just that it changes regularly. Neither the OP nor @jdrichards70 shared their actual scripts, so there’s no telling what the real problem is. Non-blocking writes should be use…

I know that doesn't answer your question, but I think you could benefit from searching "handshake" on the forum and seeing how others have implemented.

---

_[View the full topic](https://forum.inductiveautomation.com/t/best-way-to-turn-boolean-tag-value-high-every-5-seconds/50123)._