Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Support of OPC UA dictionary concept

Support of OPC UA dictionary concept

NoRisk4Project
Long-established Member

Hello,

it seems, that WebIQ only supports structures, based on the OPC UA Spec. 1.04. Some older servers provide structures, defined with OPC UA Spec. 1.04 and the old (meanwhile deprecated) dictionary concept.

For example, the system MTX provides several NC data structures (created before the OPC UA Spec. 1.04 was defined) based on the OPC UA dictionary concept.

2024-03-22_11h53_13.png

Right now, I can’t access/use these structures and the information inside. Are there any plans to support the OPC UA dictionary concept in the future?

Or would it be at least possible, to access the sub elements of these structures? For example the axis position structure contains simple arrays as sub elements (like a double array for the axis positions).

2024-03-22_11h51_04.png

2024-03-22_11h53_36.png

If I would be able to access these sub elements, it would be extremely helpful.

1 REPLY 1

webiq-sk
Frequent Contributor

WebIQ does not support arrays per se as an array structure (data type) and ExtensionObjects in OPC-UA. We have not yet implemented this, but we are aware of it and it is on the roadmap, but I can't give you a date when it will be available.

WebIQ can only work with individually addressable items and does not understand the semantics of an array. Therefore, for WebIQ, a value such as "temperatures[4]" is exactly the same as a value such as "act-value". Each individual data point must be uniquely addressable via an identifier using OPC UA, so in the case of an array, each individual array element must be directly addressable as an individual element using OPC UA and not just via the array type.

Depending on the OPC UA server, this can be achieved by activating an option such as "FolderType" or similar - unfortunately there is no standardized name for this. Each array and structure element must be individually addressable via OPC UA.

You can then use the "Variables" and "Structures" tabs in Process Data Manager to map the structure of your system. WebIQ then generates a flat structure of items from this, which you can find in the "Items" tab - only these can be connected to widgets. You will therefore only find basic data types such as integer, float and string there.

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist