Dear Community User! We are updating our platform to a new system.
Read more: Important information on the platform change.

cancel
Showing results for 
Search instead for 
Did you mean: 

Large tag subscription fails to update

Large tag subscription fails to update

Sgilk
Frequent Contributor

I have a 1000 tag license for the WebIQ runtime on ctrlX OS. I am able to deploy my 1000 tag project to the runtime, but OPC UA subscription updates are only firing for the first 500 tags.

I am subscribing to the items in a local-script and checking for their updates in a boolean array. As you can see below, indices 0-499 update from the subscription, but 500-999 never update. Any idea what is happening here?

Sgilk_0-1713990694865.png

 

5 REPLIES 5

webiq-sk
Frequent Contributor

Please provide the connect.log from the affected system (optimally in trace mode) so we can look into this. Without the log no analysis is possible.

Sgilk
Frequent Contributor

I solved the problem here after reviewing the connect.log. 

[     warning |      io_extension_item]   error_code(): opcua:-2133131264:BadTooManyMonitoredItems

On the OPC UA server side, there was a limit of 500 monitored items per subscription.

There is one other piece of strange behavior. I am seeing that subscribed items often update multiple times before the entire set of items updates once. For example, if I have an array of 1000 items, item 1 may update twice before item 1000 updates once. There is nothing in the trace logs that indicates a related problem.

webiq-sk
Frequent Contributor

You can create a Wireshark log (when not using OPC-UA encryption) and investigate if your OPC UA server is the reason or WebIQ server. Please note that in OPC UA the OPC-UA server always sends updates as it's not a pull meachanism, but a subscription mechanism where the server sends the data to the client.

Sgilk
Frequent Contributor

Is this possible when the OPC UA server and WebIQ server are both running on the ctrlX CORE? The wireshark traffic I see to my PC WebIQ client is all TCP and TLS.

webiq-sk
Frequent Contributor

Probably not, then simply switch to unencrypted traffic and use WebIQ on a local system on the network - then you should be able to diagnose this.

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