OpenOPC for Python is an easy to use OPC (OLE for Process Control) library for use with the Python programming language. The project includes a Windows gateway service allowing non-Windows clients to also access OPC-DA calls.
Be the first to post a text review of OpenOPC for Python. Rate and review a project by clicking thumbs up or thumbs down in the right column.
Fixed problem with async read() calls which occurred when multiple OPC client objects were used in a multi-threaded application. The symptom was that multiple simultaneous read() calls would occasionally fail with an unexpected "timeout" error. This would most commonly be seen when using multiple client sessions connected to the Gateway Service. Fixed Windows specific code in the opc.py command-line client so it runs properly on Linux. (SourceForge Request ID 2260592) Fixed the System Health module so it works properly with Windows Vista. (SourceForge Request ID 2260581) Added better support for unicode-based error messages. On some machines the OpenOPC Gateway Service would fail to successfully start during a reboot when set to a start-up type of "Automatic". This has been fixed. The Gateway Service's service name string has been changed from OpenOPCService to zzzOpenOPCService. The OpenOPC Gateway Service now logs messages to the Windows Event Log when it starts telling what port it's listening on. When removing OPC groups, OpenOPC was not closing the event notification callback created using win32com.client.WithEvents(). On some OPC servers this would cause resources to not be immediately released. OpenOPC now keeps track of all event callbacks and properly closes them when destroying their associated OPC group.
Fixed problem with async read() calls which occurred when multiple OPC client objects were used in a multi-threaded application. The symptom was that multiple simultaneous read() calls would occasionally fail with an unexpected "timeout" error. This would most commonly be seen when using multiple client sessions connected to the Gateway Service. Fixed Windows specific code in the opc.py command-line client so it runs properly on Linux. (SourceForge Request ID 2260592) Fixed the System Health module so it works properly with Windows Vista. (SourceForge Request ID 2260581) Added better support for unicode-based error messages. On some machines the OpenOPC Gateway Service would fail to successfully start during a reboot when set to a start-up type of "Automatic". This has been fixed. The Gateway Service's service name string has been changed from OpenOPCService to zzzOpenOPCService. The OpenOPC Gateway Service now logs messages to the Windows Event Log when it starts telling what port it's listening on. When removing OPC groups, OpenOPC was not closing the event notification callback created using win32com.client.WithEvents(). On some OPC servers this would cause resources to not be immediately released. OpenOPC now keeps track of all event callbacks and properly closes them when destroying their associated OPC group.
Fixed problem with async read() calls which occurred when multiple OPC client objects were used in a multi-threaded application. The symptom was that multiple simultaneous read() calls would occasionally fail with an unexpected "timeout" error. This would most commonly be seen when using multiple client sessions connected to the Gateway Service. Fixed Windows specific code in the opc.py command-line client so it runs properly on Linux. (SourceForge Request ID 2260592) Fixed the System Health module so it works properly with Windows Vista. (SourceForge Request ID 2260581) Added better support for unicode-based error messages. On some machines the OpenOPC Gateway Service would fail to successfully start during a reboot when set to a start-up type of "Automatic". This has been fixed. The Gateway Service's service name string has been changed from OpenOPCService to zzzOpenOPCService. The OpenOPC Gateway Service now logs messages to the Windows Event Log when it starts telling what port it's listening on. When removing OPC groups, OpenOPC was not closing the event notification callback created using win32com.client.WithEvents(). On some OPC servers this would cause resources to not be immediately released. OpenOPC now keeps track of all event callbacks and properly closes them when destroying their associated OPC group.
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
Thanks for your rating!
Would you also like to write a review?