Hello,

I'm glad to inform that with latest build(5.54.1115) the issue is gone. Now everything works fine.

Thanks!

Hello,

I had the same issue with 'Read not completed.' error while reading data using 'ReadMultipleItems' method from the OPC server. Actually, setting AllowAsynchronousMethod property to false resolved the issue, but I've noticed that now I have another error popping up randomly from time to time when I'm using the same code to connect to another OPC server(Matrikon Simulator) : 'Invalid *ppwQualities returned from IOPCSyncIO2::ReadMaxAge(...). '.
Do you have any ideas why it might happens? I suppose that setting AllowAsynchronousMethod to false should not lead to random errors.

I'm using latest version of OpcLabs lib - 5.54.1026.1

Hi,

I'm trying to read and write to a Softing S7 server running on localhost, but getting errors.

I'm using OpcLabs.EasyOpc.DataAccess.EasyDAClient via the win32com client for Python.

I've installed on my machine (Windows 7) both the Softing S7 server and the Softing Demo Server.

When reading and writing from/to the Demo Server - it works.

The commands I'm issuing are:
client = win32com.client.Dispatch('OpcLabs.EasyOpc.DataAccess.EasyDAClient')
client.WriteItemValue('localhost','Softing.OPC.S7.DA.1', 'NodeB/Test1', 1)
client.ReadItemValue('localhost','Softing.OPC.S7.DA.1','NodeB/Test1')


I'm getting these errors:

1. Read not completed. This error indicates that it could not be verified that the requested read operation was completed during the timeout period. It is possible that the read 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).

2. 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).

After issuing the write operation, the item value is set to 1, but it hangs for a while, and then I'm getting this error.

Any help would be appreciated.