# Problem on Allen-Bradley Logix Driver array of bit

**URL:** <https://forum.inductiveautomation.com/t/problem-on-allen-bradley-logix-driver-array-of-bit/73587>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 11, 2023, 12:30pm UTC](https://forum.inductiveautomation.com/t/problem-on-allen-bradley-logix-driver-array-of-bit/73587 "2023-05-11T12:30:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [May 11, 2023, 12:49pm UTC](https://forum.inductiveautomation.com/t/problem-on-allen-bradley-logix-driver-array-of-bit/73587/2 "2023-05-11T12:49:12Z")

</div>

Logix boolean arrays are really DWORD arrays, where each dword supplies 32 of the booleans. Drill in deeper. Your original boolean address of `somebooltag[B]` translates to an OPC Item Path of `somebooltag[J].K` where J=B/32 and K=B%32.

And no, this is not a bug. The logix processor really does tell a connected system that these are DWORDs. The only booleans that are actually reported as true booleans are stand-alone boolean tags (non-array). Even booleans within UDTs aren't "real" booleans, as they are hosted in some other integer type (hidden SINTs, typically).

---

_[View the full topic](https://forum.inductiveautomation.com/t/problem-on-allen-bradley-logix-driver-array-of-bit/73587)._