# CompactLogix DINT bits

**URL:** <https://forum.inductiveautomation.com/t/compactlogix-dint-bits/69983>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [February 16, 2023, 11:44pm UTC](https://forum.inductiveautomation.com/t/compactlogix-dint-bits/69983 "2023-02-16T23:44:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarkP](https://avatars.discourse-cdn.com/v4/letter/m/b3f665/32.png) [@MarkP](https://forum.inductiveautomation.com/u/MarkP)\
**Post date:** [February 16, 2023, 11:44pm UTC](https://forum.inductiveautomation.com/t/compactlogix-dint-bits/69983/1 "2023-02-16T23:44:56Z")

</div>

Hello,  
Posting this as I can see there have been many discussions around accessing bit value's of DINT's.  
I am using a Allen-Bradley CompactLogix L32E (v15 f/w) and Ignition 8 to build some an app. I have created dynamic UDT's to access the individual bits of any DINT tags. I noticed however, that if any of the DINT's in my PLC are configured as arrays (even if only 1 array) then I can access/browse the individual bits directly within ignition, no UDT or creation of separate tags required.  
Just wondering if this is by design, bug or whatever may be the case.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/a/da51a4253d543d0a7a212242f911d04f25898dac.png)  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/0/306015a00be1a22a5a6fec39ef0f844deb5c021b.png)

Edit: Moved post to correct Topic

---

<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:** [February 17, 2023, 1:32am UTC](https://forum.inductiveautomation.com/t/compactlogix-dint-bits/69983/2 "2023-02-17T01:32:52Z")

</div>

This purely a browse phenomenon, and intentional. You can always use the bits of DINTs in OPC item paths by appending the dot and bit number to an integer type's item path. The array is confusing the browse operation to show these when it normally would not.

---

<div class="post-metadata">

**Author:** ![MarkP](https://avatars.discourse-cdn.com/v4/letter/m/b3f665/32.png) [@MarkP](https://forum.inductiveautomation.com/u/MarkP)\
**Post date:** [February 17, 2023, 1:40am UTC](https://forum.inductiveautomation.com/t/compactlogix-dint-bits/69983/3 "2023-02-17T01:40:25Z")

</div>

Yes, that is how I've been doing it (thanks to a previous post of yours I found) but was wondering do I need to if I can just add these to my tag group using the browser within the designer.

---

<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:** [February 17, 2023, 1:43am UTC](https://forum.inductiveautomation.com/t/compactlogix-dint-bits/69983/4 "2023-02-17T01:43:31Z")

</div>

I wouldn't make arrays just for this. (Adds a smidgeon of overhead in the driver unless you are going to be using more than 32 bits anyways.)

For any significant quantity of tags in patterns, you should be using Ignition UDTs anyways....

---

<div class="post-metadata">

**Author:** ![MarkP](https://avatars.discourse-cdn.com/v4/letter/m/b3f665/32.png) [@MarkP](https://forum.inductiveautomation.com/u/MarkP)\
**Post date:** [February 17, 2023, 1:46am UTC](https://forum.inductiveautomation.com/t/compactlogix-dint-bits/69983/5 "2023-02-17T01:46:10Z")

</div>

Thank you Phil