PLCopen Releases Motion Control Part 4 Version 2.0
Imagine being able to control robots from different manufacturers using the same familiar PLC programming approach, regardless of the PLC platform being used. With the official release of PLCopen Motion Control Part 4 Version 2.0, this vision has taken a major step forward.
PLCopen originally released Part 4 of its Motion Control suite in 2008, introducing a standardized approach for coordinated motion and robotics applications. The specification provided a programming interface for controlling robots either directly from a PLC or through a dedicated robot controller, while shielding the application programmer from the complexity of the underlying implementation.
Over the years, valuable feedback was received from robot manufacturers, system integrators, automation suppliers, and end users. At the same time, Siemens developed and released the Standard Robot Command Interface (SRCI), which was originally based on PLCopen Motion Control Part 4. Supported by many leading robot vendors, SRCI established itself as an important standard interface between PLCs and robot controllers.
SRCI demonstrated the value of a standardized robot interface, enabling users to control robots from a single PLC environment. PLCopen recognized the opportunity to take this concept one step further: enabling robot control through a vendor-independent programming model that can be implemented by multiple PLC suppliers. The result is PLCopen Motion Control Part 4 Version 2.0.
SRCI enables robot control from a PLC. PLCopen Motion Control Part 4 Version 2.0 enables robot control from multiple PLC suppliers using a common, vendor-independent and recognizable programming model.
For machine builders and end users, this means that robot applications can be developed using a common programming approach while maintaining the freedom to choose between different PLC platforms and robot suppliers.
Over the past several years, the PLCopen Motion Control Working Group collaborated closely with experts from the SRCI community to combine the strengths of both specifications. The goal was not simply to copy SRCI, but to incorporate its most valuable concepts into the PLCopen Motion Control framework and make them available to the broader automation industry.
The result is a significantly enhanced specification that extends the original Part 4 with new function blocks, robot-oriented functionality, trajectory handling, position information, transition and buffer modes, configuration capabilities, and improved interfaces to intelligent robot controllers. At the same time, it preserves the familiar PLCopen programming model and look & feel that is already widely adopted throughout the automation industry.
One of the most remarkable achievements of this project is the successful condensation of the extensive SRCI specification into a practical and easy-to-use PLCopen standard. While SRCI consists of thousands of pages of detailed documentation, the PLCopen working group managed to capture approximately 80% of its essential functionality in roughly 10% of the documentation size. This makes the technology significantly more accessible to users while preserving the capabilities that matter most in practical applications.
The objective of Part 4 Version 2.0 is to define a comprehensive set of extensions to PLCopen Motion Control Part 1 for coordinated multi-axis motion in 3D space. A key element is the kinematic model, linking individual axes to a mechanical construct and defining the movement of the controlled endpoint. This allows users to program and control a wide range of systems, including industrial robots, gantries, CNC machines, and other coordinated motion platforms, using a consistent software interface.
The specification supports both integrated architectures and distributed solutions involving dedicated robot controllers. By standardizing the programming interface, application software becomes largely independent of the underlying hardware architecture, robot brand, or communication network. However, PLCopen Motion Control Part 4 Version 2.0 is not tied to a specific network technology and can be implemented across different automation platforms.
For machine builders and end users, this means greater freedom of choice, reduced engineering effort, improved software portability, and easier integration of robotic systems into existing automation architectures. For PLC vendors, robot manufacturers, and software suppliers, it provides a common framework for delivering interoperable robotics solutions.
With the release of Version 2.0, PLCopen continues its mission of creating vendor-independent standards that improve efficiency in automation and make advanced technologies easier to adopt.
PLCopen would like to thank all members of the Motion Control Working Group, the SRCI community (PI), robot manufacturers, automation suppliers, and end users whose expertise, dedication, and patience made this milestone possible.
What started as an update evolved into one of the most ambitious Motion Control projects in PLCopen's history, resulting in a specification that brings the worlds of PLC programming and robotics closer together than ever before.
News release from PLCopen, 31/05/2026