The namespace
urn:SIMATIC.S7-1500.OPC-UA.Application:PLC_OPC_Server
is a PLC internal namesapce. Fortunately it is nowhere refrenced in the model. So one could easily create an empty namespace with the same name before importing the model and the dependency is resolved.
The second namespace
http://www.siemens.com/simatic-s7-opcua
is a self referencing namespace from Siemens and its dependency is gone with the first too.

Thank you Matti

If there is a missing dependency, you will most likely need to contact Siemens for support. If you wish, you can send the NodeSet to us using simulation-server-support@prosysopc.com so that we can confirm the error being a missing dependency.

Do I have to get in touch with Siemens or did someone manage to get a Siemens UPC-UA nodeset running on OPC-UA Simulation Server, may be with a work around?

Regards

Thanks for your reply.

The complete nodeset is sent the simulation-server-support@prosysopc.com. On the forum only interesting subset of nodeset was shared.

While importing the nodeset to Simulation Server complete nodeset was used.

Thanks!

This NodeSet is incomplete and invalid XML. It starts with the UANodeSet element as expect, but the element is missing it closing tag. Is this just the sharing site limiting the size of the shared file or is this also the case for the NodeSet file you attempted to import to Simulation Server? If the latter then naturally Simulation Server won't be able to import XML file that is invalid.

If the former, can you send the complete NodeSet to simulation-server-support@prosysopc.com so that we can investigate it?

I have these models in nodeset on this link https://sharetext.io/mvtho539 , when I try to import it I get error from Prosys simulation server "The model could not be loaded to server address space".

Probably there is something missing or wrong with the nodeset.

Please can anyone help to understand what is missing or wrong with the nodeset?

Thanks & regards!  

Matti Siponen said
Hello,

Can you send the NodeSet to simulation-server-support@prosysopc.com so that we can investigate it?  

Thanks for your reply. NodeSet is sent to simulation-server-support@prosysopc.com

Can you send the NodeSet to simulation-server-support@prosysopc.com so that we can investigate it?

I am importing nodeset file in the prosys simulation server. The server reported error: "Invalid string representation of a nodeId: ".

Is possible to find out which nodeId prosys simulation server is refering, so it can be easy to identify the error?

Are there any logs for nodeset import which can be analyzed to find the Invalid string representation of a nodeId?

Thanks !

Matti Siponen said
Hello,

Method Nodes do not have AccessLevel and UserAccessLevel Attributes. Are you referring to Executable and UserExecutable Attributes?

Regardless, Simulation Server doesn't currently allow setting values for AccessLevel and UserAccessLevel Attributes of Variables or Executable and UserExecutable Attributes of Methods.  

Thank you. Would it be possible to request the access control feature for the sim server.

Method Nodes do not have AccessLevel and UserAccessLevel Attributes. Are you referring to Executable and UserExecutable Attributes?

Regardless, Simulation Server doesn't currently allow setting values for AccessLevel and UserAccessLevel Attributes of Variables or Executable and UserExecutable Attributes of Methods.

I am able to add methods in the Object tab to a folder, but I am not unable to add or set attributes like 'AccessLevel' or 'UserAccessLevel' to allow only authorized calls on the method nodes.
Is attributes for methods specified in the protocol?
If so, is this supported by the implementation?
If not, is there a recommended workaround to achieve this?

Thank you!
Mithun,
Tridium Inc.

The certificate and the private key of Simulation Server were updated in version 5.3.0 (see https://downloads.prosysopc.co.....sion-5-3-0). Therefore, updating from 5.0.4 to 5.6.0 would also cause the application to switch its certificate. Please, make sure the the LDS trusts the new certificate and try again.