Client-side browsing for data|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
Client-side browsing for data
Avatar
Zbynek Zahradnik
Member
Members
Forum Posts: 62
Member Since:
02/24/2014
sp_UserOfflineSmall Offline
1
09/02/2020 - 12:56
sp_Permalink sp_Print sp_EditHistory

In our UA client toolkit, we have a bunch of UI controls for browsing. 

Recently, a user has complained about the fact that our UI does not show all the nodes. He had provided an example of UaExpert screen where more nodes could be seen – within a Prosys simulation server. Upon investigation, I have found that the nodes in question have a custom “HasSignal” reference, which is a direct subtype of Aggregates reference type.

The purpose of our UI controls is to browse for nodes that are meant by the server vendor to be read from/subscribed to/written to. As such, the browse controls/dialogs do not expose the full content of server’s address space. They are meant to be integrated to apps like HMIs, loggers etc. For that reason, the browsing functionality in these UI controls differs, with some simplification, from the “show everything” approach in following aspects:

1. The browsing starts in the Objects folder, and not in the Root.
2. The only node classes displayed are Objects and Variables.
3. The reference types followed are only: a) “Organizes” and its subtypes, and b) “HasComponent” and its subtypes, c) HasProperty and its subtypes (optionally, if we want to show Properties).

Because the custom “HasSignal” reference type in Prosys simulation server is a subtype of neither Organizes nor HasComponent nor HasProperty, we do not display it in browsing.

Is this behavior on client side correct? In my opinion, for this type of client, it is – but I am seeking some confirmation. I believe that if the server vendor wanted these nodes be shown by clients such as ours, they should have made the reference type a subtype of HasComponent.

Or, should we rather widen our filter by allowing Aggregates and its subtypes?

Thank you

Avatar
Randy Armstrong
Admin
Forum Posts: 1579
Member Since:
05/30/2017
sp_UserOfflineSmall Offline
2
09/02/2020 - 21:00
sp_Permalink sp_Print

UI designs are a decision for client developers and their customers.

I would include at least all sub types of HasChild +Organizes in your default view.

If you have customers that want to see non-hierarchical references then an ‘show all’ toggle would likely address their needs.

There is nothing in the spec that mandates what you do.

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