# Tag address at OPC UA vs OPC Item Path at Ignition 8.1.47 **URL:** \ **Category:** Ignition\ **Created:** [May 5, 2025, 3:38am UTC](https://forum.inductiveautomation.com/t/tag-address-at-opc-ua-vs-opc-item-path-at-ignition-8-1-47/105864 "2025-05-05T03:38:26Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![matt.taheri.ca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.taheri.ca/32/73540_2.png) [@matt.taheri.ca](https://forum.inductiveautomation.com/u/matt.taheri.ca)\ **Post date:** [May 5, 2025, 3:38am UTC](https://forum.inductiveautomation.com/t/tag-address-at-opc-ua-vs-opc-item-path-at-ignition-8-1-47/105864/1 "2025-05-05T03:38:26Z")
I have a tag in OPC UA with the type 'word array' and the address R00006[1][6]. I'm trying to read this tag from Ignition Designer. Here's what I did: 1. Created a tag of type integer (since I can't create a word array tag). 2. Set the OPC Item Path to [DeviceName]R00006[1,6]. However, I'm getting an error: 'Error\_Configuration: Bad\_NodeIdUnknown - The node ID refers to a node that does not exist in the server address space.' When I changed the OPC Item Path to [DeviceName]R00006 with the tag data type set to integer, I could only read the value of the first element in the word array. Is there any way I can read the entire array, and what data type should I use to read the tag data?" ---
**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\ **Post date:** [May 5, 2025, 4:36am UTC](https://forum.inductiveautomation.com/t/tag-address-at-opc-ua-vs-opc-item-path-at-ignition-8-1-47/105864/2 "2025-05-05T04:36:33Z")
Did you try Integer Array for the type? Also can you browse for the tag and add it that way? Ignition will normally put its best option in automatically. ---
**Author:** ![matt.taheri.ca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.taheri.ca/32/73540_2.png) [@matt.taheri.ca](https://forum.inductiveautomation.com/u/matt.taheri.ca)\ **Post date:** [May 5, 2025, 2:27pm UTC](https://forum.inductiveautomation.com/t/tag-address-at-opc-ua-vs-opc-item-path-at-ignition-8-1-47/105864/3 "2025-05-05T14:27:16Z")
The integer array didn't work because Ignition converted the data into an array of 16 elements consisting of 1s and 0s, which only translates to the value of the first element. The import tag didn't work either, as Ignition didn't recognize the 'word array' datatype and instead converted it to a string, which also resulted in just the value of the first element, seems like ignition isn't exposing the entire dataset, ---
**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:** [May 5, 2025, 2:42pm UTC](https://forum.inductiveautomation.com/t/tag-address-at-opc-ua-vs-opc-item-path-at-ignition-8-1-47/105864/4 "2025-05-05T14:42:47Z")
It would be helpful if you could use UaExpert to browse to this tag and show us the structure and value of its attributes. ---
**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\ **Post date:** [May 6, 2025, 2:52pm UTC](https://forum.inductiveautomation.com/t/tag-address-at-opc-ua-vs-opc-item-path-at-ignition-8-1-47/105864/5 "2025-05-06T14:52:20Z")
> [@matt.taheri.ca](#): > > DeviceName]R00006[1,6] Should that not be [1][6]? ---
**Author:** ![matt.taheri.ca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.taheri.ca/32/73540_2.png) [@matt.taheri.ca](https://forum.inductiveautomation.com/u/matt.taheri.ca)\ **Post date:** [May 6, 2025, 5:21pm UTC](https://forum.inductiveautomation.com/t/tag-address-at-opc-ua-vs-opc-item-path-at-ignition-8-1-47/105864/6 "2025-05-06T17:21:41Z")
**What worked for me was creating six different tags and configuring the OPC Item Path like this:** `[DeviceName]R00006`, `[DeviceName]R00007`, `[DeviceName]R00008`, `[DeviceName]R00009`, `[DeviceName]R000010`, `[DeviceName]R000011`. Apparently, Mitsubishi devices expose data this way. None of the other formats worked—such as `[DeviceName][1][6]`, `[DeviceName][1,6]`, or even `[DeviceName][0:5]`.