Log In
Register
Forum
Topic RSS
21:04, EEST
May 10, 2018
Offline
I’m dealing with some inconsistent publish response behavior. Our subscription is setup for Publish responses to come in at 1 minute intervals, which we’ve verified is what the UA server (kepware running on a different computer) is doing. Instead the subscription listener is receiving several publish responses at once every few minutes, followed sometimes by a regularly scheduled 1 minute publish response, then another gap of 3 to 4 minutes. Eventually the subscription listener stops receiving anything at all. This behavior only happens on a test environment running 14.04 ubuntu in an isolated network environment, and I noticed recently that the RTC on the linux box is terribly inaccurate running a few minutes ahead, and manually corrected the time (the kepware server had an accurate time). This resolved all issues and published responses came in on 1-minute intervals like clockwork. Does anyone know if system time inconsistencies could cause issues with subscription publish reponses?
15:52, EEST
April 17, 2013
Offline
Hi,
System time being slightly ahead should not cause problems in subscriptions.
Basically the OPC UA subscriptions work so that notification messages are only sent when there’s data changes to notify (there’s also a mechanism for sending an empty message once in a while as a keep-alive). So the most straightforward explanation would be that the server just doesn’t have anything to report and for this reason it doesn’t send notifications for some time.
So, the question is: how did you verify that the server is sending the publish responses every minute?
To proceed further, it would be beneficial to see a log file which shows the incoming publish responses as well as the evidence that SubscriptionNotificationListeners are not called for these value changes. The log file of incoming OPC UA messages can be prepared with Wirehark (https://prosysopc.com/blog/opc-ua-wireshark/) and your application level log showing the inconsistent listener calls should provide enough information. Files cannot be attached here to the forum, so please send these files to us by email at uajava-support prosysopc.com
18:07, EEST
May 10, 2018
Offline
I’ll send the wireshark logs, but I can confirm that the publish responses are firing off every minute. The UA server is a kepware installation connecting to an OPC classic simulator which is updating it’s values at a predetermined interval. In short, there is no 1-minute interval where there isn’t an update to the subscribed nodes and I have confirmed that publish requests are being sent to the ua client (with the prosys sdk) on schedule. Changing the system clock does have an effect on the processing of publish requests, I’ve been able to reproduce the effect by changing the system clock on the client by as little as one second.
Most Users Ever Online: 1919
Currently Online:
12 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 88
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 730
Moderators: 7
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1529
Posts: 6471
Newest Members:
rondawolinski7, Marypof5711, roycedelargie91, kourtneyquisenbe, ellis87832073466, zkxwilliemae, gabriellabachus, Deakin, KTP25Zof, Wojciech KubalaModerators: Jouni Aro: 1026, Pyry: 1, Petri: 0, Bjarne Boström: 1032, Jimmy Ni: 26, Matti Siponen: 349, Lusetti: 0
Administrators: admin: 1
