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

Importing Structures

Importing Structures

NickOS
Member

Using the OPC-UA Browser reading an MLC75 on IW14v22, I cannot import a structure as a structure, only create child variables. So for this structure:

NickOS_0-1669801832807.png
I would get these variables:

NickOS_4-1669802744249.png
I found that if I manually created a corresponding structure with WEBIQ...:

NickOS_1-1669801924483.png
..then create a mapping like this, making the basename the PLC structure name..:

NickOS_2-1669802196885.png
..then things seems to communicate properly:

NickOS_3-1669802253183.png
The benefit here is the variables list isn't cluttered. I have tried this with a mismatch in ordering of elements, seems okay. Misnaming obviously doesn't work. So it seems to hold up. The questions then are: Is there a more succint way of doing this - either by using the browser or via the import feature of the structures? Also is this implied mapping (the strucutre element name must be appended to my base name somehow) the intended use of communicating structures via WebIQ/OPC-UA or is explicit mapping deemed more robust?

I ask because, if we decide to switch to WebIQ, I've thousands of variables to accomodate.

5 REPLIES 5

HmiGuide
Community Moderator
Community Moderator

The issue you are describing is known. SmartHMI is currently investigating a way how to import structures as structures.

Thanks @HmiGuide , and in the meantime, creating manually as I described should be ok? I appreciate it takes me longer than simply creating all the child variables, but it makes it much more manageable thereafter, for example if I add an element or expand an array.

HmiGuide
Community Moderator
Community Moderator

Creating structures and variables can be automated with the WebIQ API, but it needs some time to get familiar with the API.

Hemingway
Established Member

Hi, do we have any update on this?

webiq-sk
Frequent Contributor

No, this has not been implemented yet. Please note that this is a large task because it involves all components of WebIQ (all widgets, server, API, WebIQ Designer) that have to learn the concept of structures.

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