You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we restart the UA COM Server Wrapper with the underlying DA server that contains bulk tags(up to 10k subscribed), the subscription is not bring recreated in the UA client (UA expert).
Configuration Details:
DA Server name : KepServer OPC UA client: UA Expert configuration :1 channel, 5 device, each device having 4k tags, total tags 20k.
Current Behaviour: the subscription is not being recreated when the server is restarted & the items are getting removed from Data Access view.
Expected Behaviour: In the UA client's data access view, all subscribed tags should be recreated once UA COM Server Wrapper is Restarted and their values should start updating.
Steps to reproduce:
Start UA COM Server Wrapper & Connect Using UA client. (UA Expert)
In the UA client, creating four data access instances and subscribing the bulk tags to the four data access views.
Restart the UA COM Server Wrapper
Environment:
Windows: Windows 10 Pro Installed RAM: 16 GB System Type: 64 bit
The text was updated successfully, but these errors were encountered:
When we restart the UA COM Server Wrapper with the underlying DA server that contains bulk tags(up to 10k subscribed), the subscription is not bring recreated in the UA client (UA expert).
Configuration Details:
DA Server name : KepServer
OPC UA client: UA Expert
configuration :1 channel, 5 device, each device having 4k tags, total tags 20k.
Current Behaviour: the subscription is not being recreated when the server is restarted & the items are getting removed from Data Access view.
Expected Behaviour: In the UA client's data access view, all subscribed tags should be recreated once UA COM Server Wrapper is Restarted and their values should start updating.
Steps to reproduce:
Environment:
Windows: Windows 10 Pro
Installed RAM: 16 GB
System Type: 64 bit
The text was updated successfully, but these errors were encountered: