# M580 NUA0100 Module OPC Path

**URL:** <https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [March 14, 2023, 3:15pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032 "2023-03-14T15:15:47Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [March 14, 2023, 3:15pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/1 "2023-03-14T15:15:47Z")

</div>

Hey everyone,

Does anyone know of a way to alias the OPC Path browsed from a M580 NUA Module?

Right now the path is very long: EG

> nsu=[http://www.unifiedautomation.com/CustomServer/;s=0:TestTag](http://www.unifiedautomation.com/CustomServer/;s=0:TestTag)

Does Ignition have a way to alias or is there a way to change this in the settings of the M580?

Thanks

---

<div class="post-metadata">

**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:** [March 14, 2023, 4:01pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/2 "2023-03-14T16:01:23Z")

</div>

You can't alias it in Ignition but you could probably parameterize a UDT or something...

Why are you concerned about it?

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [March 14, 2023, 4:16pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/3 "2023-03-14T16:16:14Z")

</div>

Functionally it works. It just seemed like a long path to me compared to how OPC-UA paths via Igniton's OPC-UA server are formatted.

---

<div class="post-metadata">

**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:** [March 14, 2023, 4:19pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/4 "2023-03-14T16:19:46Z")

</div>

Any tags from any server that come from a namespace at index 2 or above in the namespace table will use the namespace URI instead of namespace index.

Indices in the NodeId (OPC Item Path) are relative and some servers will change which tags belong to which namespace after a restart, so any index 2+ has to be explicitly specified so the client can resolve the proper index upon connecting. Index 0 and 1 have special treatment and are not expected to change.

---

<div class="post-metadata">

**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:** [March 14, 2023, 4:24pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/5 "2023-03-14T16:24:31Z")

</div>

Also worth noting, if you know the index, you can manually type in the OPC Item Path using the index instead (e.g. `ns=2;s=Foo`), but if you drag and drop from the OPC Browser it will use the URI for index 2+ instead.

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [March 14, 2023, 4:25pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/6 "2023-03-14T16:25:15Z")

</div>

> [@Kevin.Herron](#):
>
> Also worth noting, if you know the index,

How can I find that index?

---

<div class="post-metadata">

**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:** [March 14, 2023, 4:26pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/7 "2023-03-14T16:26:06Z")

</div>

Read the server's NamespaceArray variable and find the index of the corresponding URI, use a 3rd party UA client, or by some other out of bands means - maybe the software you use to configure this server can tell you.

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [March 14, 2023, 4:31pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/8 "2023-03-14T16:31:36Z")

</div>

I'll do some looking and report back! Thanks Kevin!

---

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [March 14, 2023, 6:38pm UTC](https://forum.inductiveautomation.com/t/m580-nua0100-module-opc-path/71032/9 "2023-03-14T18:38:05Z")

</div>

I tried different indexes, and it seems to be at index 2. I'll see if I can find a third party OPC-UA client that can confirm that.
