Professional OPC
Development Tools

logos

Online Forums

Technical support is provided through Support Forums below. Anybody can view them; you need to Register/Login to our site (see links in upper right corner) in order to Post questions. You do not have to be a licensed user of our product.

Please read Rules for forum posts before reporting your issue or asking a question. OPC Labs team is actively monitoring the forums, and replies as soon as possible. Various technical information can also be found in our Knowledge Base. For your convenience, we have also assembled a Frequently Asked Questions page.

Do not use the Contact page for technical issues.

opcUaClient.WriteValues() success=true ,Unable to receive notification of point

More
07 Nov 2023 15:22 #12339 by support
Hello.

Yes, 0x800A0000 is for BadTimeout. Unless you have an indication to the contrary, it means what it says in the log message. I.e. the server has not responded soon enough to the Publish or Republish service call.

It would only be possible to tell more if we had a network capture (Wireshark) with the actual communication during that session. However, most likely outcome of such analysis is simply that the server has not responded soon enough to the service call. Less likely, but of course still possible, is that the server has responded in time, but somehow the client did not interpret the response correctly.

Best regards
The following user(s) said Thank You: xpycy001

Please Log in or Create an account to join the conversation.

More
07 Nov 2023 15:05 #12338 by xpycy001
"trace sequence number 5699 "
The disconnect log is different from other logs in that it shows connection timeout. There is a detailed tracking process in the attachment log. Can you help analyze why TimeOut occurred

Please Log in or Create an account to join the conversation.

More
07 Nov 2023 10:45 #12336 by support
Hello,
I do not quite understand the nature of your issue. So I will start with the part that seems clear. You wrote

"30 attempts were made to write values to the point, and each write operation returned success, but the point was not actually successful".

If the value was not actually written, but the Write call succeeded, you have a faulty server. You need to fix the server. There is no way this can be fixed on the client side.

Regards

Please Log in or Create an account to join the conversation.

More
07 Nov 2023 10:25 #12335 by xpycy001
Supplementary description

1. There are no write failures at other points on the target machine

2. For machines of the same brand at the same process section location, there will be daily Write fail

3. The target point will become true every 15 seconds, opcUaClient. writeValue() false

4. The total number of machines is about 90, among which 30 machines have problems, and write failures occur approximately 5-10 times a day

5. I am not sure how to solve this thorny problem, here is my attempt

6. Adjust HoldPeriod==SessionTimeOut=120 seconds

7. retryDelay=6s, SessionConnectionTimeOut=6s

Please Log in or Create an account to join the conversation.

More
07 Nov 2023 09:56 - 07 Nov 2023 10:01 #12334 by xpycy001
Dear support :
The problem is as follows,
30 attempts were made to write values to the point, and each write operation returned success, but the point was not actually successful
1. 2023/11/7 13:40:15 call opcUaClient.WriteValues() success=true
2. Subscribe Side not received valueChange
3. retry more times …
4. trace tips: timeout
5. trace sequence number 5699
6 opcUaclient used default parameters . (session too much and create again and again)
7 at last I used HoldPeriod =120s && SessionTimeOut=120s ,but write fail again
【opc.tcp://10.xx.xxx.xx:4840】,【ns=4;s=|var|Inovance-PLC.Application.PR109_OPC_MES.vs_OnSlotFinish_B】
trace:

13:40:30.407,EvId:6002,Information The OPC-UA subscription on client session with connect sequence number 5699 to endpoint URL "opc.tcp://10.31.199.205:4840" has been successfully created and checked, and given subscription ID 2. Revised publishing interval is 7500, keep-alive count is 10 and lifetime count is 1000.

13:42:00.691,EvId:4051,Warning The OPC-UA client session with connect sequence number 5699 on endpoint URL "opc.tcp://10.31.199.205:4840" has encountered a publish error with code 0x800A0000 for subscription ID 0 and sequence number 0. The error might be from the Publish or the Republish service. Further publish errors with this code on this session will not be logged.
Attachments:
Last edit: 07 Nov 2023 10:01 by xpycy001. Reason: content format

Please Log in or Create an account to join the conversation.

Moderators: support
Time to create page: 0.050 seconds