Value NotReadable in UAExpert

[rittal-beck]

Hello SupportTeam,

I manage starting the OPC UA server finally, I can browse through all objects but when I want to monitor it with the UAExpert I get following error code

UaServer_CreateMonitoredItems: Error adding monitored item [0x803A0000].

I know that this means it is not readable but what can I do? Is it maybe just a configuration?

The Provider code comes from a uastack version before 1.3. And I'm already so happy that it is running with the new 1.8 stack version.

I debugged the error and i know that the error comes from that line of code:

src/uaserver/uaserverc/uaserver_monitoring.c:1742
uStatus = PROV_ADDITEM(pProvider, (UaServer_MonitoredItem*)pMonitoredItem);

Best regards

[rittal-beck]

Hello again.
So I debugged it a little bit further and it seems that it comes from this function

UaServer_UserMgt_PermCheck.

And it seems i get the error from this if clause:

/* check signing / encryption */
if ((pInode->mode & UA_ALL_SIGNING_REQUIRED &&
pUserCtx->messageSecurityMode != OpcUa_MessageSecurityMode_Sign &&
pUserCtx->messageSecurityMode != OpcUa_MessageSecurityMode_SignAndEncrypt) ||
(pInode->mode & UA_ALL_ENCRYPTION_REQUIRED &&
pUserCtx->messageSecurityMode != OpcUa_MessageSecurityMode_SignAndEncrypt))
{
return OpcUa_False;
}

Do I miss something? Where can I set the permissions?

Is it not possible to just copy and paste an older version of a running server to another version of the UAStack? I mean I already changed the server_c_demo to my needs. And in UAExpert I can see all of my possible variables.

Hopefully that makes sense to you and you can help me.

Kind regards

[Support Team]

Hello rittal-beck,

when creating nodes in your provider, default access permissions are being assigned to them. You can change the default permissions using UaServer_UserMgt_SetDefaultPermissions and UaServer_UserMgt_SetDefaultPermissionsAllTypes, see http://documentation.unified-automation ... #usage_sec for more details.

If you don't want to use authorization at all, you can disable it by setting the CMake option BUILD_AUTHORIZATION to OFF when building the SDK.