Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: AC on January 14, 2026, 01:56:30 PM
-
Are there plans to allow OPC UA to access UD structures? In my example, I would like to have OPC UA list Pump.Startrequest instead of having to map another bit Say C1-> Pump.StartRequest. This gets REALLY confusing when changes need to be made, not to mention starts to get dangerous, and doubles my overhead in programming. I have therefore refrained from using the OPC UA OR the sparkplug options as its just too cumbersome to remap my entire UD structures to other memory.
-
Are there plans to allow OPC UA to access UD structures? In my example, I would like to have OPC UA list Pump.Startrequest instead of having to map another bit Say C1-> Pump.StartRequest. This gets REALLY confusing when changes need to be made, not to mention starts to get dangerous, and doubles my overhead in programming. I have therefore refrained from using the OPC UA OR the sparkplug options as its just too cumbersome to remap my entire UD structures to other memory.
You can document your existing UDT fields and make them available. Not saying it's the cleanest answer, but there is no need to map them to other memory.
To answer your question specifically, the issue is the memory limits on the POM. To make every field of every UDT available would require far more memory than the micro in the POM has. We could build it as a module, and we've talked about it, we just need to see how well these POMs do before committing to building it.
-
Understood, This actually makes sense and I will give this a spin and see how it goes. Thanks!