Adding Nodes at Runtime Workflow|OPC UA Standard|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
Adding Nodes at Runtime Workflow
Avatar
Paul Zatschler
Dresden
New Member
Members
Forum Posts: 1
Member Since:
02/07/2025
sp_UserOfflineSmall Offline
1
04/15/2025 - 01:22
sp_Permalink sp_Print

Dear OPC community,

we are currently implementing the functionality to add, edit and remove nodes at runtime for our server. The documentation is very helpful in understanding what needs to happen. However I would like to verify that we understood it correctly/fill in the gaps. So please let me know if I got anything wrong:

1) The server is started and loads its current model.
2) Server state goes to running.
3) Client now connects as the server is “ready”.
4) The server updates (adds, edits, deletes) nodes and sends BaseModelChangeEvent/GeneralModelChangeEvent
5) The server state remains running for the changes (?)
6) The client is subscribed (or not) to the above events and can issue a reconnect or re-read.

I am wondering about the server state when modifying nodes and about the client’s possibilities to detect changes.

Many thanks in advance! Smile

Avatar
Randy Armstrong
Admin
Forum Posts: 1620
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
04/17/2025 - 00:41
sp_Permalink sp_Print

The server state is not related to changing the address space.

lots of servers add/remove nodes in the running state because they front end a dynamic system.

if your server needs to functionality while you are adding/removing nodes then you would choose a non-running state.

if clients are not limited use running.

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 24
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1483
Posts: 5011