OPCUA Subscription with Kepware lost after few days #1647
Replies: 1 comment 6 replies
-
Beta Was this translation helpful? Give feedback.
-
|
the status of your subscription changes and i assume your SubHandler has no method status_change_notification !? opcua-asyncio/asyncua/common/subscription.py Line 100 in 1fe61df |
Beta Was this translation helpful? Give feedback.
-
|
it starts from error in watch dog loop- more infor.. |
Beta Was this translation helpful? Give feedback.
-
|
again you need to implement a method "status_change_notification" in you SubscriptionHandler! this is the line where the error is created: opcua-asyncio/asyncua/common/subscription.py Line 232 in 1fe61df e.g. class SubscriptionHandler:
"""
The SubscriptionHandler is used to handle the data that is received for the subscription.
"""
def datachange_notification(self, node: Node, val, data):
return
def status_change_notification(self, status: ua.StatusChangeNotification): #<--- this is missing in your handler
return |
Beta Was this translation helpful? Give feedback.
-
|
thank you, let me add and try , thanks for reply and support |
Beta Was this translation helpful? Give feedback.
-
|
you should consider logging the "status" to the console in order to see what has happend ;) |
Beta Was this translation helpful? Give feedback.
-
We have subscribing to the kepware tags using the library and it is working fine for few days, then after few days - batch subscription is lost and data change event is not working, and this happens to loss in the data
Kepware is configured with boolean tag and it goes from false to true and stays in true for 5 seconds and goes to false , depending on the process completion and this tag is subscribed for notification
Another heart beat tag which increases every one second from value 0 to 10 by incremental value one using kepware simulator ramp function, and python is subscribed to this tag for monitoring any issue with kepware.
Above tags are working perfectly fine for some time > 1 day, 7 days, 3 days, but randomly heartbeat monitoring batch event change is not working, and after reconnecting through script it works fine.
is there any setting we need to do in the library or in kepware to avoid this false disconnect issue?
from asyncua import Client, Node, ua
.....
heart_beat_tag = connection_configs.get("heart_beat_tag", "ns=2;s=Heartbeatsim.Heartbeatsim.tag.Heartbeat")
.....
nodes.append(client.get_node(heart_beat_tag))
# Create Subscription Handler class object
handler = SubscriptionHandler(client)
subscription = await client.create_subscription(2000, handler)
await subscription.subscribe_data_change(nodes)
....
class SubscriptionHandler:
client: Client = None
def init(self, c):
self.client = c
_logger.info("Client attribute set in the SubscriptionHandler class")
"""
The SubscriptionHandler is used to handle the data that is received for the subscription.
"""
async def datachange_notification(self, node: Node, val, data):
if str(node) == heart_beat_tag:
# update heart beat timestamp
global heart_beat_timestamp
heart_beat_timestamp = datetime.now()
Beta Was this translation helpful? Give feedback.
All reactions