Aggregating Server in terms of address space and namespace indexes|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
Aggregating Server in terms of address space and namespace indexes
Avatar
Rudolf
Slovakia
Member
Members
Forum Posts: 19
Member Since:
07/13/2018
sp_UserOfflineSmall Offline
1
07/03/2020 - 04:48
sp_Permalink sp_Print sp_EditHistory

Hello,

I have a conceptual question about an aggregating of servers:

Lets assume that we have an aggregating server to which I added namespaces with indexes 4 and 5:

[0] https://opcfoundation.org/UA/
[1] urn:vm-win16-fei:UA:TestServer
[2] http://phi-ware.com/AggregatingServer
[3] https://opcfoundation.org/UA/Diagnostics
[4]ns0:https://opcfoundation.org/UA/
[5]ns1:urn:phi-ware.OPCUA-ICP.IOT2040

I added a ServerAS object [ns=5] of aggregated server under the ObjectIds.ObjectsFolder [ns=2]. I added other nodes of ServerAS all to ns=5.

An OPC UA client cannot browse ServerAS. I assume it is because Browse request (at aggregating server side) tries to find nodeid in server’s nodemanager[5] which does not exists. Is it correct?

Do I need to add a nodemanager for added ServerAS? In other words do I need for each aggregated server create an address space in separate nodemanager?

Or MasterNodeManager.RegisterNamespaceManager could be a good point to add namespace and nodemanager?

Thank you

BR Rudo

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