# AB Compact Logix Boolean Array not showing full array size in UDT **URL:** \ **Category:** Ignition\ **Tags:** vision\ **Created:** [August 8, 2025, 5:30pm UTC](https://forum.inductiveautomation.com/t/ab-compact-logix-boolean-array-not-showing-full-array-size-in-udt/109544 "2025-08-08T17:30:11Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [August 8, 2025, 5:39pm UTC](https://forum.inductiveautomation.com/t/ab-compact-logix-boolean-array-not-showing-full-array-size-in-udt/109544/3 "2025-08-08T17:39:50Z")
Logix BOOL arrays are actually packed into DWORD arrays with nothing visible to external connections to indicate they’re actually a BOOL array. > [@Problem on Allen-Bradley Logix Driver array of bit](https://forum.inductiveautomation.com/t/problem-on-allen-bradley-logix-driver-array-of-bit/73587/2): > > 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, a… --- _[View the full topic](https://forum.inductiveautomation.com/t/ab-compact-logix-boolean-array-not-showing-full-array-size-in-udt/109544)._