Access Level Mismatch of Nodes After Migration from AS 4.12 to 6.0

Ask Questions B&R Software & Runtime
1

After migrating a project from Automation Studio 4.12 to 6.0, I noticed a change in how OPC UA node access levels are handled in the .uad file.

In Unified Automation Modeler, certain nodes were explicitly set with CurrentRead access. However, after migration, the generated .uad file shows both CurrentRead and CurrentWrite enabled by default, making these nodes writable in UA clients like UA Expert — even though they were intended to be read-only.

image
image612×488 54.2 KB

But via UaExpert, those nodes can be written even though access level is CurrentRead

This behavior was not present in AS 4.12, where the access levels from the UA Modeler were correctly reflected in the .uad file. It seems that AS 6.0 does not automatically preserve the modeled access levels during migration.

Is there a known change in how access levels are handled in AS 6.0? Or is there a step missing during migration to ensure the .uad file respects the original access level definitions?

Any insights or recommended practices would be appreciated.

2

As a new user, I can’t add more than one embedded media, so I am attaching the images here.

In AS6, the Authorization and Roles are set as follows:

image
image1282×124 11.7 KB

3

Roles Permissions are as follows

image
image1308×282 24.8 KB

4

Hi @gafoor, since there has been no reply to your issue, I think the best way forward is to get in contact with the support team at your local office. Please update us with the solution. Thanks.

1 Like