Array of UDT inside another UDT

Ignition
1

Hello Everyone,
I know this might be very easy for some of you. How do I create array of UDT inside another UDT? I am able to use UDT inside UDT but not able to create array.

2

Arrays of UDT aren’t a supported tag type, whether embedded inside another UDT or at the top level.

3

Thank you Kevin. I appreciate your quick response.

4

I had actually same question as Urvish_Mehta.
Array of UDTs can be very useful in some cases. Is it on the roadmap?

5

No it’s not on any road map, though I do agree that it could useful in general.

You can make a feature request here: https://ideas.inductiveautomation.com/

6

@petr.sasin @Kevin.Herron

Please vote if you think this can make tagging easier,
Array of UDT Inside tag

7

Is there any update on this from a roadmap perspective? The feature request seems to have gotten some good traction, but I can't find an update anywhere.

Has anyone figured out a good workaround for this?

8

I suspect a factor in the silence from IA on this is that Ignition array types in the tag system are not fixed-length--they adopt the length of the data delivered to them. And there's no mechanism to configure the array value element-by-element.

So UDT arrays would need major infrastructure changes to the tag model to support per-instance config, and would probably therefore need to be fixed length. Someone who wants this feature should elaborate on exactly how they expect this to work.

(Fixed length PLC UDT arrays can easily be modeled with a folder of instances using Ignition's typical numeric names, like _0_, _1_, ...)

9

Might there be a way to script child tag creation on creation of the UDT based on a parameter if the PLC tag structure uses the tagname property as the array index?

Alternatively, the multi-instance tag wizard should help here, right?

10

For those struggling with this in regards to Logix or Omron NJ/NX products, I strongly recommend pointing my alternate EtherNet/IP driver at the target product, and applying the resulting auto-generated JSON for UDTs and tag definitions. Pruned/altered/merged as needed. This can be done in trial mode and the results used with the IA native drivers.