# Schneider OFS OPC UA - Problem in Tag Browsing

**URL:** <https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 30, 2022, 7:30am UTC](https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165 "2022-05-30T07:30:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kottamalai](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kottamalai/32/35154_2.png) [@Kottamalai](https://forum.inductiveautomation.com/u/Kottamalai)\
**Post date:** [May 30, 2022, 7:30am UTC](https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165/1 "2022-05-30T07:30:04Z")

</div>

Hi,

I am using Schneider’s Unity Pro for one of my M580 application. In this, I have some DDT (Derived Data Type) tags. In Ignition, for tag browsing I am using Schneider’s OFS OPC Server. I can be able to see all the Tags in OPC Browser. After importing the DDT, that is automatically assigned as a short array under the **value** as shown below. In my DDT, I have “REAL” Datatype also. I am unable to use that “REAL” as all the tags are assigned as “BYTE” type. Kindly suggest me a solution, as I have tried a lot.

 ![OPC Browser](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/8/58d90b81afe025ae56c572703d37736c2988b4ee.png)  
 ![Tag Browser](https://us1.discourse-cdn.com/inductiveautomation/original/3X/3/b/3bef99e5d747576070d6eee65adb2c7241c17404.png)

Thanks & Regards,

Kottamalai

---

<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:** [May 30, 2022, 1:18pm UTC](https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165/2 "2022-05-30T13:18:50Z")

</div>

Can you connect to this server with a 3rd party client like UaExpert and see what the Value and DataType attributes for this Node are?

---

<div class="post-metadata">

**Author:** ![Kottamalai](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kottamalai/32/35154_2.png) [@Kottamalai](https://forum.inductiveautomation.com/u/Kottamalai)\
**Post date:** [May 31, 2022, 4:58am UTC](https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165/3 "2022-05-31T04:58:19Z")

</div>

Hi,

Thank you for your reply. Please find the below screenshot from UaExpert client. All the data types and values are seems OK.

 ![UaExpert](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/0/b092f919d91335675eff7c4d37cc15ccc785219b.png)

One more thing, I have tried with OPC DA for the same server. It perfectly works. I think the problem is solved.

Thank you for the support…!

---

<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:** [May 31, 2022, 1:01pm UTC](https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165/4 "2022-05-31T13:01:34Z")

</div>

Can you expand the attributes pane so that the Value and DataType attributes are fully visible?

Also, it looks like in UaExpert you just subscribed to all the tags _underneath_ `L2FN101I01_FP` - why didn’t you do the same in Ignition if that’s what you’re after?

---

<div class="post-metadata">

**Author:** ![Kottamalai](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kottamalai/32/35154_2.png) [@Kottamalai](https://forum.inductiveautomation.com/u/Kottamalai)\
**Post date:** [June 1, 2022, 4:35am UTC](https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165/5 "2022-06-01T04:35:36Z")

</div>

Hi,

Please find the below screenshot for attributes expanded.

 ![Attributes](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/3/a3717f35d686b6c939825d4efbef6666534fb6df.png)

In Ignition, as stated above browsing the tags or expanding the datatype from OPC Browser is fine. After transferred the datatype into the Tag Browser only it changed as “Short Array”.

 ![OPC Browser_Expanded](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/c/8cb7eb42a4a6c06a15556241642c333a2a129158.png)

 ![For Provider default- Tags](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/f/ef1a0d5e701bd3caee209469e9611a33d42ccb5d.png)

I can be able to browse the tags individually. But I need to use the entire DDT. So that, I can assign the UDT’s easily in Ignition. “DDT (Derived Data Type) is nothing but, it’s like a UDT”.

If I am browsing the tags from my DA Server, all the DDT’s are showing as a folder and I am able to use the tags for my UDT assignment in Ignition.

 ![OPC Browser - DA Server](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/e/2ef8680df85f92d3d6fd66cd35baf4e673a109b9.png)

 ![Tag Browser - DA Server](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/1/711de287349251da5af7ddf4560ba44414060c4b.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:** [June 1, 2022, 12:45pm UTC](https://forum.inductiveautomation.com/t/schneider-ofs-opc-ua-problem-in-tag-browsing/60165/6 "2022-06-01T12:45:45Z")

</div>

You didn’t highlight the right tag in UaExpert this time, but it’s not that important.

When you connect to the server using OPC Classic the server is putting all thetags from that DDT into a folder.

When you connect to the server using OPC UA the server is using a Variable Node to organize all the tags instead, but all the member tags are still underneath. The problem is that Variable Node itself has a value (though it seems to be a non-sense short array you can’t do anything with).

Stop selecting that Variable Node in the Ignition UI and just select _all_ the Nodes beneath it and move those over instead.
