View Issue Details

IDProjectCategoryView StatusLast Update
000857010000-003: Address SpaceSpecpublic2023-04-18 19:19
ReporterThomas Steiner Assigned ToJim Luth  
PriorityhighSeverityfeatureReproducibilityN/A
Status closedResolutionwon't fix 
Summary0008570: Namespace-Ready indicator for OPC UA Clients
Description

Currently OPC UA Clients do not know if a OPC UA Server has finished inserting nodes into a Namespace. This leads to different Client implementations for waiting until a Namespace is ready (try to browse or read a node until its possible, ...).

Proposal:
Additionally to the NamespaceArray Property a NamespaceReadyArray Boolean-Property could be added, which indicates if all nodes of this Namespace are present in the Information Model. It could also be represented via a Integer-Property which shows the progress in percent.

Also an OPC UA Event, that the Server finished building a Namespace should be sent.

Its not possible to put this information into the Namespace-Metadata, because it could be possible that not even this nodes are available yet!

Additional Information

See this topic in the opcfoundation Forum: https://opcfoundation.org/forum/opc-ua-standard/namespace-ready-to-use-for-client/#p4348

TagsInfoModel
Commit Version
Fix Due Date

Activities

Jim Luth

2023-04-18 19:19

administrator   ~0019213

Discussed in UA meeting today.

The Nodes in a UA Address Space are considered dynamic (no matter what the Namepace is) and hence a Client can never be sure all the Nodes of a given Namespace are present. If a Server loads some known subset of Nodes on startup (for example from a configuration file) then the Server should set the state in the ServerObject to something other than RUNNING_0 (e.g, NO_CONFIGURATION_2 or SUSPENDED_3) until all of the known Nodes are loaded.

Issue History

Date Modified Username Field Change
2023-01-04 17:04 Thomas Steiner New Issue
2023-01-04 17:04 Thomas Steiner Tag Attached: InfoModel
2023-04-18 19:19 Jim Luth Assigned To => Jim Luth
2023-04-18 19:19 Jim Luth Status new => closed
2023-04-18 19:19 Jim Luth Resolution open => won't fix
2023-04-18 19:19 Jim Luth Note Added: 0019213