3rd party OPC UA Client failed to reconnect with our server|Product and Service Requests|Forum|OPC Foundation

Avatar
Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
Lost password?
sp_Feed sp_PrintTopic sp_TopicIcon
3rd party OPC UA Client failed to reconnect with our server
Avatar
Wendy Yang
Member
Members
Forum Posts: 4
Member Since:
08/18/2016
sp_UserOfflineSmall Offline
1
08/29/2016 - 00:13
sp_Permalink sp_Print sp_EditHistory

Hello,

we are using OPC UA stack 1.01.

A fact is that we did not register, i.e. we excluded the support of "transfer subscription" service. Now a OPC UA Client is trying to reconnect with our server, Client sent TransferSubscriptionRequest to our server and did not receive any repsonse. Is it a expected behavior of server?

Thank you.

Wendy

Avatar
Guest
Guests
2
08/29/2016 - 06:30
sp_Permalink sp_Print

Hello Wendy,

That TransferSubscription service is not a required feature for UA Servers to implement, at least not for the Standard UA Server profile which is what I'm assumed you've built your product on. This profile is defined here although this is for UA version 1.03.

I would strongly encourage you to upgrade your UA stack to 1.03 so as to maintain interoperability with all the newer applications as they will not be interoperable with you in some situations, such as with insecure connections.

Avatar
Wendy Yang
Member
Members
Forum Posts: 4
Member Since:
08/18/2016
sp_UserOfflineSmall Offline
3
08/30/2016 - 00:30
sp_Permalink sp_Print

Thank you for your quick reply.

Could you help double confirm below two points:

1. For UA stack 1.01 is it an expected behavior that there is no response to Client TransferSubscriptionRequest?

2. I need to upgrade to UA stack to 1.03 to fix this behavior, right?

Wendy

Avatar
Guest
Guests
4
08/30/2016 - 02:58
sp_Permalink sp_Print

Any Service request shall have a response. If a Service is not supported the Server shall respond with "Bad_ServiceUnsupported". This has always been the expected behavior.

Avatar
Guest
Guests
5
08/30/2016 - 06:08
sp_Permalink sp_Print

Karl is right. We even implemented a test in the CTT that invokes ALL of the UA Services sequentially to verify that a response is received that indicates either (a) success, e.g. read, (b) failure (not supported, not implemented, etc.)

Definitely upgrade to UA 1.03 stack version to increase your application's interoperability with other UA applications.

Avatar
Wendy Yang
Member
Members
Forum Posts: 4
Member Since:
08/18/2016
sp_UserOfflineSmall Offline
6
08/30/2016 - 20:02
sp_Permalink sp_Print sp_EditHistory

Hi Nathan,

Thank you for your reply.

Could you help double confirm about this: Is it UA Stack or us that should be responsible for giving the response to any Service request?  Because as I understand we as Server app should not directly process communication with Client.

Wendy

Avatar
Guest
Guests
7
08/31/2016 - 06:46
sp_Permalink sp_Print

Hello Wendy,

The stack is responsible for the communications layer. The SDK is responsible for logic like this, so I would look there first, or contact your toolkit vendor.

Avatar
Wendy Yang
Member
Members
Forum Posts: 4
Member Since:
08/18/2016
sp_UserOfflineSmall Offline
8
09/01/2016 - 22:39
sp_Permalink sp_Print

Hi Nathan,

Thank you for your reply.

Could you confirm below: so now UA stack 1.01 we build our Server application on is not giving response to the Service request. Do we need to upgrade UA stack to 1.03 to fix this issue?

Wendy

Forum Timezone: America/Phoenix
Most Users Ever Online: 510
Currently Online:
Guest(s) 19
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Forum Stats:
Groups: 2
Forums: 10
Topics: 1336
Posts: 4535