# Set bit in PLC tag with Indirect Tag

**URL:** <https://forum.inductiveautomation.com/t/set-bit-in-plc-tag-with-indirect-tag/11183>\
**Category:** Ignition\
**Created:** [February 9, 2016, 4:55pm UTC](https://forum.inductiveautomation.com/t/set-bit-in-plc-tag-with-indirect-tag/11183 "2016-02-09T16:55:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [February 9, 2016, 4:55pm UTC](https://forum.inductiveautomation.com/t/set-bit-in-plc-tag-with-indirect-tag/11183/1 "2016-02-09T16:55:00Z")

</div>

having trouble setting a particular bit in PLC using an indirect tag. Ignition V7.8.1 , Clgx V24

Interlock\_Bypass is an INT in the PLC that I have created as a BOOL ARRAY to get access to each bit  
[attachment=1]2016-02-09 11\_46\_29-Program Manager.png[/attachment]

Trying to use SELECTED to toggle specific bit in PLC, but tag write does not make it to PLC. I I force force BITS in PLC, status of SELECTED will follow PLC bit. Appears if the tag is READ ONLY even though Indirect is set to Bi-Directional and tag in PLC is READ/WRITE.  
What is the proper way to set an Indirect Bit?  
[attachment=0]2016-02-09 11\_47\_51-Program Manager.png[/attachment]

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [February 9, 2016, 5:01pm UTC](https://forum.inductiveautomation.com/t/set-bit-in-plc-tag-with-indirect-tag/11183/2 "2016-02-09T17:01:33Z")

</div>

You are not using an indirect there.  
You need to replace the 0 with {1} and then set the property that sets the value for the indirect.  
So your address should be

PC11/Alim/Receiving1/interlock\_Bypass[{1}]

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [February 9, 2016, 5:28pm UTC](https://forum.inductiveautomation.com/t/set-bit-in-plc-tag-with-indirect-tag/11183/3 "2016-02-09T17:28:05Z")

</div>

Thanks,

already tried that.

This just popped up, did not see this before, so issue may be with PLC tag

[attachment=0]2016-02-09 12\_29\_10-192.168.24.233 - Remote Desktop Connection.png[/attachment]

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [February 10, 2016, 4:22am UTC](https://forum.inductiveautomation.com/t/set-bit-in-plc-tag-with-indirect-tag/11183/4 "2016-02-10T04:22:47Z")

</div>

OK, it is not the PLC as I can write INTEGERS to the BOOL ARRAY tag:

Here I have a duplicate tag pointing to the same INT in the PLC. Set PLC INT to 7 and the first 3 BOOLs SET  
[attachment=3]2016-02-09 23\_09\_56-192.168.24.233 - Remote Desktop Connection.png[/attachment]  
[attachment=2]2016-02-09 23\_08\_13-Program Manager.png[/attachment]d

Notice this warning as well after configuring the BOOL as a TAG and try to edit again.

[attachment=0]2016-02-09 23\_11\_30-192.168.24.233 - Remote Desktop Connection.png[/attachment]

Configuration  
[attachment=1]2016-02-09 23\_15\_36-192.168.24.233 - Remote Desktop Connection.png[/attachment]

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [February 15, 2016, 7:32pm UTC](https://forum.inductiveautomation.com/t/set-bit-in-plc-tag-with-indirect-tag/11183/5 "2016-02-15T19:32:10Z")

</div>

guess this answer’s my question:

[inductiveautomation.com/forum/v … 50&t=15150](https://inductiveautomation.com/forum/viewtopic.php?f=50&t=15150)

currently cannot done be done 😮
