Hello,
I would like use UAmodeler to declare views : view_1, view_2, etc .
Each view will contain specific nodes which are already present in my address space.
I didn't find : How can I set my views and organises them and links nodes with these views ?
Best regards,
JeromeR
creating views within UAModeler
Moderator: Support Team
- Support Team
- Hero Member
- Posts: 3226
- Joined: 18 Mar 2011, 15:09
Re: creating views within UAModeler
Hi,
the UaModeler does not support declaration and/or mmodification of "Views". There is no "generic" way for implementing such feature (same like "query"), which is probably the reason why it is rarely (litterally not) used.
the UaModeler does not support declaration and/or mmodification of "Views". There is no "generic" way for implementing such feature (same like "query"), which is probably the reason why it is rarely (litterally not) used.
Best regards
Unified Automation Support Team
Unified Automation Support Team
-
- Jr. Member
- Posts: 2
- Joined: 03 Feb 2025, 13:32
Re: creating views within UAModeler
Views are a good feature of OPC UA and it would be interesting to be able to create them with Modeler.
Are there other ways to make use of this feature?
Are there other ways to make use of this feature?
- Support Team
- Hero Member
- Posts: 3226
- Joined: 18 Mar 2011, 15:09
Re: creating views within UAModeler
Hi,
the "View" as defined in OPC UA do not tell anything about their implementation. The OPC UA Specification leaves that open for a reason. By this the (filtered) view is always something that needs specific implementation in the server. And most servers just not support any node management services, whatsoever.
In our view the "alias" feature of the OPC UA Specification, has more potential to make in into the market. The concept of "alias" (like sym-link) is more global list of mapping Unique-Identifiers to ServerUrl/NodeId, including the ability to search/query within this list of alias.
the "View" as defined in OPC UA do not tell anything about their implementation. The OPC UA Specification leaves that open for a reason. By this the (filtered) view is always something that needs specific implementation in the server. And most servers just not support any node management services, whatsoever.
In our view the "alias" feature of the OPC UA Specification, has more potential to make in into the market. The concept of "alias" (like sym-link) is more global list of mapping Unique-Identifiers to ServerUrl/NodeId, including the ability to search/query within this list of alias.
Best regards
Unified Automation Support Team
Unified Automation Support Team