Examples for OPC client and subscriber development in Python are now on GitHub: github.com/OPCLabs/Examples-QuickOPC-Python .

Note: QuickOPC now supports Python in much better way, cleaner syntax, and public packages (pypi.org/project/opclabs-quickopc/) on Python Package Index . See What's new in QuickOPC 2023.2 for more information. And, over 270 examples are available in the User's Guide!

Hello,

without further details I cannot tell what is the cause of "could not create certificate..." error, but at least one hint: Have you run your application (at least once) with elevated privileges? The first time the app is run, it generates and creates an application certificate, and that might require administrator rights.

Best regards

Hello,
thank you.

I have received a forum notification with a text where you described "Could not create a certificate via a proxy" error, and also claimed that "Also there is a bug here, the QuickOPC Returns "Could not create a certificate via a proxy" but at the same time it returns "The operation completed successfully"".

I cannot locate this post now on the forum, so it looks like that you have edited it and removed the original text?

Anyway, it is not quite clear what you mean by saying that QuickOPC has returned *two* results at the same time. That's not physically possible. If, what you have meant, is the fact that e.g. WriteMultipleItemValues method itself has returned a success, while there are errors in the individual result objects, then that is perfectly correct and by design. QuickOPC methods that operate on multiple items never return an error themselves (except in case of invalid arguments). The actual operation-related errors are always in the result objects only. If you think about it, it must be that way, because an exception thrown by the method would mean that you won't be able to see the individual results at all - because there would be none returned.

This is described in the documentation: opclabs.doc-that.com/files/onlinedocs/QuickOpc/Latest/User%2...iple-Element%20Operations.html .

Best regards

Hello,

I should say that we are absolutely Python beginners here. QuickOPC can be used from so many tools and languages that it is impossible to grasp that all.

However, with some hint from mail.python.org/pipermail/python-win32/2005-February/002923.html , I was able to extract the values by placing the following code below the bottom of your code:

It's unclear to me why a two-dimensional array is returned to Python - because what we return from our side is one-dimensional. Only the [0] row at the first dimension in Python seems to contain the actual data. This transformation is something that occurs inside win32com.client so we cannot influence it I think.

I hope this help
Best regards

Hello.

Ad 1. We have methods like ReadMultipleItems, ReadMultipleItemValues, WriteMultipleItemValues, precisely for that purpose. And they should be used if you have more things to be read or written at the same time, instead of single-item operations in a loop. There are no example for Python with them, though; for start, look for examples in other languages.

These methods take an array of arguments as input, and return array of results as output. I also have a feeling that we had a problem passing the arrays to/from Python through COM, but I am not sure, If you run into problems with arrays, let me know and I will have another look.

Ad 2. This may be normal. In OPC the constant portion of the time for each operation may be quite high, but with relatively little dependence on number of items affected. So, it is quite possible that reading one item may take 0.1 seconds, and reading 10 items still 0.1 seconds. That is why it is highly advisable to read or write multiple items at once.

Another factor is connection time - QuickOPC establishes the connection automatically upon first request, and keeps it open for some time then - but not on subsequent requests if it is still open. So, the connection time is added to the first operation but not necessarily to the others.

Ad 3. Pass in the name of the computer as the first argument to the methods - that's where you have an empty string ('') now. Do not be surprised if you run into DCOM security/configuration headaches with remote access then - that's kind of normal

Best regards