Difference between revisions of "Inside the Python support in QuickOPC"
Jump to navigation
Jump to search
(Created page with "TBD!!!") |
|||
| Line 1: | Line 1: | ||
| − | + | QuickOPC can currently be used from Python using two approaches: With the help of Python.NET (the new, recommended approach), and over Microsoft COM (older approach, deprecated). | |
| + | |||
| + | = QuickOPC with Python.NET = | ||
| + | |||
| + | |||
| + | = QuickOPC with Python (COM) = | ||
| + | In this approach, the '''pypiwin32''' Python package is used to access QoickOPC COM API from Python. For the reasons explained further below, this approach is now deprecated. The examples using the COM approach remain in the product, at least for the time being. | ||
| + | |||
| + | The disadvantages of the COM approach include: | ||
| + | - Strictly limited to Windows only. | ||
| + | - Multiple layers (QuickOPC is .NET API primarily, the COM API layer sits on top of it, then Python layer accesses this COM API), with performance and possibly reliability implications. | ||
Revision as of 15:44, 3 November 2023
QuickOPC can currently be used from Python using two approaches: With the help of Python.NET (the new, recommended approach), and over Microsoft COM (older approach, deprecated).
QuickOPC with Python.NET
QuickOPC with Python (COM)
In this approach, the pypiwin32 Python package is used to access QoickOPC COM API from Python. For the reasons explained further below, this approach is now deprecated. The examples using the COM approach remain in the product, at least for the time being.
The disadvantages of the COM approach include: - Strictly limited to Windows only. - Multiple layers (QuickOPC is .NET API primarily, the COM API layer sits on top of it, then Python layer accesses this COM API), with performance and possibly reliability implications.
