dynamically added nodes disapears after reboot in UaExpert
Posted: 22 Mar 2021, 14:35
Environment
Using C++ OPCUA SDK V1.7.4
OPCUA Server as Windows application
UaExpert as OPCUA Client
Task
Adding additional OPCUA nodes or namespace after starting the OPCUA server via UaServerApplication->start()
How to reproduce
- Starting OPCUA server an wait until all nodes are added
- Start UaExpert and connect to the OPCUA server
- Add OPCUA nodes or add a node manager after you have called UaServerApplication->start()
- use one of the added nodes in UaExpert in "Data Access View"
- Reboot the OPCUA server
- in the moment when UaServerApplication->start() is called the variable disapears in UaExpert
- in the UaExpert and Wireshark you can see BadNodeIdUnknown
Remarks
- Other OPCUA Clients shows the same behaviour.
Questions
- Is it really necessary to have all OPCUA nodes created before UaServerApplication->start() is called?
- Is there any way to avoid blocking the dynamically added OPCUA nodes by OPCUA clients?
Thanks
Sven
Using C++ OPCUA SDK V1.7.4
OPCUA Server as Windows application
UaExpert as OPCUA Client
Task
Adding additional OPCUA nodes or namespace after starting the OPCUA server via UaServerApplication->start()
How to reproduce
- Starting OPCUA server an wait until all nodes are added
- Start UaExpert and connect to the OPCUA server
- Add OPCUA nodes or add a node manager after you have called UaServerApplication->start()
- use one of the added nodes in UaExpert in "Data Access View"
- Reboot the OPCUA server
- in the moment when UaServerApplication->start() is called the variable disapears in UaExpert
- in the UaExpert and Wireshark you can see BadNodeIdUnknown
Remarks
- Other OPCUA Clients shows the same behaviour.
Questions
- Is it really necessary to have all OPCUA nodes created before UaServerApplication->start() is called?
- Is there any way to avoid blocking the dynamically added OPCUA nodes by OPCUA clients?
Thanks
Sven