Log In
09/19/2014
Offline
As many of you may have seen, the OPC Foundation has officially declared the OPC Core Components (OPC Classic / OPC DA) as strictly legacy, entirely unmaintained, and at its final End-of-Life (EOL) under the OPC MIT license.
For systems relying on older field devices, third-party integration servers, and legacy hardware, OPC Classic remains a reality of day-to-day operations. However, depending on an unmaintained codebase—especially one tied to legacy DCOM and critical Windows components—presents growing maintenance and security challenges.
While migrating entirely to OPC UA is the ultimate long-term goal, we recognize that replacing legacy field controllers overnight isn't always feasible for every site.
What is your reccomendation to support ongoing operations safely?
Looking forward to your insights and real-world experiences.
05/30/2017
Offline
The OPC-F will continue to provide signed installers since since COM/DCOM reacts badly if multiple vendors provide the same proxy/stub library.
The project is public and MIT so anyone who has the job maintaining old systems can share fixes and the OPC-F will review them and provide updated signed installers if they are deemed necessary.
This should be sufficient to support the community as long as needed.
1 Guest(s)
Usage Policy