I have a project with hundreds of OPC-UA variables available on the network. A lot of these variables are used actively in various scripts that run in background in the OS (Linux).
I'm experimenting with Automation Server and I have a hard time understanding how the web interface populates its parameters list for a given PLC (<plc details="" parameters="" for="" plc="" 'xyz'="">).</plc>
In this page, it looks like the only variables available are the ones that are of a "base" type : bool, TIME, String, INT, etc. All the variables that are nested into function blocks or structures are not available in the web interface, even if they are available to any OPC-UA client.
Is this a limitation of the Automation Server or is there something that can be done in Codesys?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a project with hundreds of OPC-UA variables available on the network. A lot of these variables are used actively in various scripts that run in background in the OS (Linux).
I'm experimenting with Automation Server and I have a hard time understanding how the web interface populates its parameters list for a given PLC (<plc details="" parameters="" for="" plc="" 'xyz'="">).</plc>
In this page, it looks like the only variables available are the ones that are of a "base" type : bool, TIME, String, INT, etc. All the variables that are nested into function blocks or structures are not available in the web interface, even if they are available to any OPC-UA client.
Is this a limitation of the Automation Server or is there something that can be done in Codesys?
yes, but you could use a demo project in the analyzer to check other types:
https://analyzer-eu.automation-server.com/help/en/tags
this should work.
Confirmed. The Data Analyzer tool can indeed access all OPC-UA symbols. Thanks !
Last edit: jbcregen 2025-12-02