OPC Foundation and PLCopen release version 1.02 of the “OPC UA for IEC61131-3” specification


The extended “OPC UA for IEC61131-3” specification now supports the current 3rd edition of the IEC61131-3 standard and simplifies vendor adoption

Scottsdale, AZ – November 25th, 2020 –The OPC Foundation, in collaboration with PLCopen, announced the release of v1.02 of the “OPC UA for IEC61131-3” specification. Building on the first version of the specification, the joint working group added:

  • support for all datatypes defined in the 3rd edition of IEC61131-3
  • an optimized, machine-readable version of the information model (i.e. nodesetfile)
  • compliance with enhanced specification templates to support the tool chain used to generate validated information models
  • inclusion in the global online searchable specification reference
  • OPC Foundation Compliance Test Tool (CTT) test cases for validation of vendor implementations of “OPC UA for IEC61131-3”

Founded in 2008, this joint working group has the goal of expressing IEC 61131-3 information models using OPC UA. By doing so, an IEC6-61131-3 PLC project that is loaded onto different control platforms can be displayed in a standardized form and made available for communication via the controllers’ OPC UA servers.

“This first step harmonizes the access of the project running in the controller” says Eelco van der Wal, Managing Director of the PLCopen organization. “With this an unprecedented transparency is created in the communication in industrial automation, enabling the configuration of the communication much faster and independent of the network and suppliers. For this reason, many suppliers have implemented this, providing their users with the ease of use in communication.”

Major PLC vendors implemented “IEC61131-3 as UA Client”
In addition to the server specification “UA for IEC61131-3” the group also worked very successfully on the “client specification” which was originally released in 2014. The implementation of this functionality on a controller makes it possible to initiate a communication session to any other available OPC UA Server. The controller can exchange complex data structures horizontally with other controllers independent of the fieldbus system used, or vertically with other devices using an OPC UA server service oriented architecture, like an MES/ERP system in order to collect data or write new production orders to the cloud.

Stefan Hoppe, the President and Executive Director of the OPC Foundation first initiated the idea of PLCopen Function Blocks during the first OPC UA developer conference back in October 2006 when he was a Product Manager of TwinCAT at Beckhoff. Mr. Hoppe commented “I am proud that this specification has been implemented by the world’s leading PLC manufacturers such as 3S, BECKHOFF, Bosch-Rexroth, B&R, Honeywell, Omron, Phoenix Contact and Siemens and is used in many international applications. For example, these function blocks were used by Honeywell for the implementation of the MDIS specification in the oil & gas market: These function blocks have been combined and nested to provide higher quality solutions tailored to the MDIS application, and so making it easier for the customer to use.

About PLCopen
PLCopen, as an organization active in industrial control, is creating a higher efficiency in your application software development: in one-off projects as well as in higher volume products. As such it is based on standard available tools to which extensions are and will be defined. With results like Motion Control Library, Safety, XML specification, Reusability Level and Conformity Level, PLCopen made solid contributions to the community, extending the hardware independence from the software code, as well as reusability of the code and coupling to external software tools. One of the core activities of PLCopen is focused on IEC 61131-3, the only global standard for industrial control programming. It harmonizes the way people design and operate industrial controls by standardizing the programming interface. This allows people with different backgrounds and skills to create different elements of a program during different stages of the software lifecycle: specification, design, implementation, testing, installation, and maintenance. Yet all pieces adhere to a common structure and work together harmoniously.
For more information see here http://www.PLCopen.org

About the OPC Foundation
Since 1996, the OPC Foundation has facilitated the development and adoption of the OPC information exchange standards. As both advocate and custodian of these specifications, the Foundation’s mission is to help industry vendors, end-users, and software developers maintain interoperability in their manufacturing and automation assets. The OPC Foundation provides the best specifications, technology, process, and certification to achieve multivendor, multiplatform, secure, reliable, interoperability for moving data and information from the embedded world to the enterprise cloud. The Foundation serves over 790 members worldwide in the Industrial Automation, IT, IoT, IIoT, M2M, Industrie 4.0, Building Automation, machine tools, pharmaceutical, petrochemical, and Smart Energy sectors.
For more information, please visit www.opcfoundation.org

Eelco van der Wal
Managing Director


Stefan Hoppe
President and Executive Director
OPC Foundation