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.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- Getting 'Read not completed' and 'Write not completed' errors
Getting 'Read not completed' and 'Write not completed' errors
Anyway, we do not officially support version 5.23.
The fact that it gets long to complete the write might be on the server side too. The reason you are getting the timeout error is that you have set the timeout to relative low value (5000 milliseconds), so you get what you have asked for. So the problem is not so much the timeout itself, it is the fact that the Write takes long.
I strongly suggest to remove the setting of UpdatwRates.ReadAutomatic = 500. Instead, please try to use the settings described here: www.opclabs.com/forum/reading-writing-subscriptions-property...scriptions-made-with-opc-reads .
Regards
Please Log in or Create an account to join the conversation.
I attached the old thread, because I got last time an update in the library Version I am using, The new Versions of your library unfortunately it is not backward compatible, it means if I try to use the new library Version I would have to rewrite my complete application.
Anyway, could you explain what could be the reasons why the Problem is showing?
I run the function in a separate thread,
result = EasyDAClientWrite.WriteMultipleItemValues(Parameters);
where Parameters include the OPC items, and the values to be written, The function is not re-call if the thread is busy, in that way I dont overload the opc by performing several Write calls at the same time.
here is the configuration of my Client,
EasyDAClientWrite = new EasyDAClient();
EasyDAClientWrite.Isolated = true;
EasyDAClientWrite.InstanceParameters.Timeouts.ReadItem = 5000;
EasyDAClientWrite.InstanceParameters.Timeouts.WriteItem = 5000;
EasyDAClientWrite.InstanceParameters.UpdateRates.ReadAutomatic = 500;
EasyDAClientWrite.InstanceParameters.Mode.AllowAsynchronousMethod = true;
EasyDAClientWrite.InstanceParameters.Mode.AllowSynchronousMethod = true;
EasyDAClientWrite.InstanceParameters.Mode.DesiredMethod = DAReadWriteMethod.Asynchronous;
EasyDAClientWrite.SynchronizationContext = SynchronizationContext.Current;
I have been noticing that the new values take really long to be shown in the PLC, and if I check the result I got the error described in this thread. Here an example of my error Log file.
<Exception>
<TimeStamp>7/16/2019 2:03:16 PM</TimeStamp>
<ExceptionType>System.Runtime.InteropServices.COMException</ExceptionType>
<ExceptionData>
<OPCItem>/PhoenixContact.AX-Server.21/P3631_S4_XK3.w_Tab_service_function_MC2_9</OPCItem>
</ExceptionData>
<Message>Cannot connect topic (timeout). </Message>
<Source>OpcLabs.EasyOpcRaw.DataAccess.RawEasyDAClient</Source>
</Exception>
<Exception>
<TimeStamp>7/16/2019 2:03:16 PM</TimeStamp>
<ExceptionType>System.Runtime.InteropServices.COMException</ExceptionType>
<ExceptionData>
<OPCItem>/PhoenixContact.AX-Server.21/P3631_S4_XK3.w_Tab_service_status_MC2_13</OPCItem>
</ExceptionData>
<Message>Write not completed. This error indicates that it could not be verified that the requested write operation was completed during the timeout period. It is possible that the write operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled). </Message>
<Source>OpcLabs.EasyOpcRaw.DataAccess.RawEasyDAClient</Source>
</Exception>
<Exception>
<TimeStamp>7/16/2019 2:03:16 PM</TimeStamp>
<ExceptionType>System.Runtime.InteropServices.COMException</ExceptionType>
<ExceptionData>
<OPCItem>/PhoenixContact.AX-Server.21/P3631_S4_XK3.w_Tab_service_status_MC2_12</OPCItem>
</ExceptionData>
<Message>Write not completed. This error indicates that it could not be verified that the requested write operation was completed during the timeout period. It is possible that the write operation will actually succeed or fail, but later. Increase the timeout period if you want to obtain positive or negative indication of the operation outcome. Other reason for this error may be that under heavy loads, topic request or response queue is overflowing. Check the event log for queue overflow errors (if event logging is supported by the product and enabled). </Message>
<Source>OpcLabs.EasyOpcRaw.DataAccess.RawEasyDAClient</Source>
Please Log in or Create an account to join the conversation.
I do not not understand why you have related the issue with the browse dialog to this.
Regards
Please Log in or Create an account to join the conversation.
I am having a similar problem, but I have installed the version QuickOPC 5.23_1371.1
Please check this www.opclabs.com/forum/browsing/1437-opcbrowsedialog-bug/2230?start=0
Best Regards
Luis Garcia
Please Log in or Create an account to join the conversation.
- Forum
- Discussions
- QuickOPC-Classic in .NET
- Reading, Writing, Subscriptions, Property Access
- Getting 'Read not completed' and 'Write not completed' errors