# Siemens OPC server addressing

**URL:** <https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [February 22, 2024, 6:05pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205 "2024-02-22T18:05:22Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![rfolkes](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rfolkes](https://forum.inductiveautomation.com/u/rfolkes)\
**Post date:** [February 22, 2024, 6:05pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/1 "2024-02-22T18:05:22Z")

</div>

I am using the Siemens PLC OPC server.  
Connection to OPC server is ok but having trouble figuring out how to configure the OPC item path for tags or structures inside of Data Blocks

tried using this + a few other variations  
ns=3;s="TGMS\_INPUT\_002"."Cfg\_Point"

I am not able to get any of the DB in the OPC browser but if I add a OPC UA Server interface in siemens I can find in the browser but it uses a reference like nsu=[http://Server](http://Server) interface\_1;i=82 and I would like to be able to reference with "TGMS\_INPUT\_{IDNum}"."Cfg\_Point"

![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/2/92f91f30839c667aeb3a59ecf1c912eae9b11126.png)

---

<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:** [February 22, 2024, 6:14pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/2 "2024-02-22T18:14:26Z")

</div>

Is this a 1200 or 1500?

AFAIK you can't configure or otherwise influence the NodeIds used when you add custom "server interfaces", and I _think_ in the 1200 server interfaces are all you get...

---

<div class="post-metadata">

**Author:** ![rfolkes](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rfolkes](https://forum.inductiveautomation.com/u/rfolkes)\
**Post date:** [February 22, 2024, 6:15pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/3 "2024-02-22T18:15:11Z")

</div>

> [@Kevin.Herron](#):
>
> terface

1500

---

<div class="post-metadata">

**Author:** ![rfolkes](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rfolkes](https://forum.inductiveautomation.com/u/rfolkes)\
**Post date:** [February 22, 2024, 6:15pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/4 "2024-02-22T18:15:55Z")

</div>

That will really suck for me if I can only do it through server interfaces

---

<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:** [February 22, 2024, 6:17pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/5 "2024-02-22T18:17:01Z")

</div>

You must be missing a configuration setting, I can see and access DBs in the 1500 we have.

---

<div class="post-metadata">

**Author:** ![rfolkes](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rfolkes](https://forum.inductiveautomation.com/u/rfolkes)\
**Post date:** [February 22, 2024, 6:17pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/6 "2024-02-22T18:17:46Z")

</div>

ok will keep looking for that setting then

---

<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:** [February 22, 2024, 6:23pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/7 "2024-02-22T18:23:35Z")

</div>

Here's where they show up on ours:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/4/44474581fd895a6cf39263e74c8a371cd84ddb70.png)

---

<div class="post-metadata">

**Author:** ![rfolkes](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rfolkes](https://forum.inductiveautomation.com/u/rfolkes)\
**Post date:** [February 22, 2024, 6:55pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/8 "2024-02-22T18:55:16Z")

</div>

Digging into it more myself, but it appears that that is not available yet on the 1500 HA PLC "yet". 3.1 firmware update for TIA V19 added the OPC UA server for 1500 HA (redundant) PLC but looks like they didn't include the Simatic Server Interface which is what you are looking at there.

When you select something from there can you give an example of the OPC Item path it gives you?

---

<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:** [February 22, 2024, 6:59pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/9 "2024-02-22T18:59:44Z")

</div>

These Nodes have verbose but predictable NodeIds that you can build UDTs against: `ns=3;s="SymbolicTest_Unoptimized"."instance_ScalarTypes"."DWORD" `

---

<div class="post-metadata">

**Author:** ![automatisation](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@automatisation](https://forum.inductiveautomation.com/u/automatisation)\
**Post date:** [February 22, 2024, 8:06pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/10 "2024-02-22T20:06:59Z")

</div>

Maybe you can have some luck with SiOME ([https://support.industry.siemens.com/cs/document/109755133/siemens-opc-ua-modeling-editor-(siome)](https://support.industry.siemens.com/cs/document/109755133/siemens-opc-ua-modeling-editor-(siome)))  
It works for s7-1200 so maybe it will help on s7-1500 HA  
We're using it for some of our 1200 that we want to access with symbolic names instead of the node ids.  
A bit of a pain to use when showing arrays but it does the work

---

<div class="post-metadata">

**Author:** ![rfolkes](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rfolkes](https://forum.inductiveautomation.com/u/rfolkes)\
**Post date:** [February 26, 2024, 8:28pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/11 "2024-02-26T20:28:11Z")

</div>

Ok I was able to setup something with SiOME, but based on what I am reading elsewhere in this forum is I should try to grab the UDT as a document / structure. I believe this is built into the standard siemens OPC interface but that doesn't exist on the 1500 RH OPC yet.

Does anyone know how I can change this setup so that Ignition can pull the full structure as a single JSON?

I believe I need to change the node class... But not sure what to change it to.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/d/fd3022e0a648903c3e16aeb4cc39ba848fc80aaf.png)

---

<div class="post-metadata">

**Author:** ![Ian\_Cottengim](https://avatars.discourse-cdn.com/v4/letter/i/48db29/32.png) [@Ian\_Cottengim](https://forum.inductiveautomation.com/u/Ian_Cottengim)\
**Post date:** [December 4, 2024, 5:01pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/12 "2024-12-04T17:01:01Z")

</div>

Reviving this topic to ask if you ever found how to pull full structures as JSON.  
We just bought a 1500 RH and I REALLY don't want to address and poll all these tags individually.  
I hope Siemens adds support for this soon.

---

<div class="post-metadata">

**Author:** ![rfolkes](https://avatars.discourse-cdn.com/v4/letter/r/e95f7d/32.png) [@rfolkes](https://forum.inductiveautomation.com/u/rfolkes)\
**Post date:** [December 4, 2024, 5:06pm UTC](https://forum.inductiveautomation.com/t/siemens-opc-server-addressing/86205/13 "2024-12-04T17:06:04Z")

</div>

I gave up trying to get it to work. With the quantity of tags we had in our system and expected changes over time it wasn't feasible to use direct Ignition -- siemens redundancy system. Non redundancy can auto build the OPC tags in siemens but that isn't developed yet on siemens for redundancy.

We went with kepware in the middle.
