CODESYS · Motion control

CODESYS Motion CNC Robotics

Integrated PLC, Motion, CNC & Robotics Engineering
CODESYS Motion CNC Robotics extends the IEC 61131-3 project with single-axis and coordinated motion, CNC interpolation and supported robot kinematics. PLC logic and motion are engineered together, while performance is determined by the selected runtime target, drive network and motion licence scope.

Single-axis and coordinated motionCam and gearingCNC interpolationRobot kinematicsDrive communication
CODESYS SoftMotion official product image
MotionPLCopen Motion Control
CNCDIN 66025
RoboticsSupported kinematics
LicensingAxes + groups / interpolators
Product role

Integrated control logic and coordinated motion

CODESYS Motion CNC Robotics extends the IEC 61131-3 project with single-axis and coordinated motion, CNC interpolation and supported robot kinematics. PLC logic and motion are engineered together, while performance is determined by the selected runtime target, drive network and motion licence scope.

PLC and motion in one projectSequence logic, axes and coordinated motion are engineered in a common CODESYS project and variable model.
Single-axis through coordinated motionThe platform supports positioning, gearing, cams and synchronized multi-axis functions, with optional CNC and robotics capabilities.
Performance designed around the targetAxis count, bus cycle, interpolation load, kinematics and controller performance must be evaluated as one system.
Architecture role

From motion application to synchronized drives

Define the interfaces and ownership boundaries first; version, licence and target selection should follow the architecture rather than lead it.

01PLC + motion project
02Motion CNC Robotics
03Runtime target
04Industrial Ethernet / drive bus
05Drives / axes / robot
Confirm the exact target, product version, device package, protocol role, licence and—where applicable—certified safety scope before release to production.
Engineering scope

Motion, CNC and robotics capabilities

These capabilities define what the CODESYS component contributes to the architecture and what must still be provided by the controller, host platform, network or machine design.

01

PLC and motion in one project

Sequence logic, axes and coordinated motion are engineered in a common CODESYS project and variable model.

02

Single-axis through coordinated motion

The platform supports positioning, gearing, cams and synchronized multi-axis functions, with optional CNC and robotics capabilities.

03

Performance designed around the target

Axis count, bus cycle, interpolation load, kinematics and controller performance must be evaluated as one system.

Technical selection

Axes, kinematics, target performance and licence sizing

Use this table as a requirement-capture guide. The final implementation should be checked against current CODESYS product documentation, Store data, target documentation and—where relevant—certificates and safety manuals.

Motion modelPLCopen Motion Control function blocks and CODESYS motion extensions are used for axis and coordinated-motion functions.
CNCCNC functions use DIN 66025-style programming with supported interpolation functions and application-specific tooling.
RoboticsSupported kinematic models and axis groups are configured in the CODESYS motion environment.
Drive integrationDrives are configured through supported fieldbus integration and addressed symbolically from the application.
Current licence structureFor Control SL systems, current application-based licences separate SoftMotion axis capacity from Axis Groups/CNC Interpolators. Exact quantities are selected from the current CODESYS Store portfolio.
Sizing inputsController performance, cycle time, real and virtual axis count, interpolators, drive network, feedback and trajectory complexity all affect selection.
Project workflow

Motion architecture and commissioning workflow

Move from architecture qualification to engineering, commissioning and lifecycle evidence in a controlled sequence.

01

Document the mechanics

Record axes, drives, feedback, kinematics, travel limits and the required cycle time.

02

Fix the motion architecture

Confirm target performance, fieldbus, axis groups, CNC or robotics functions and licences.

03

Engineer the movement

Configure drive scaling, homing, cams, paths, interpolation and the coordinating logic.

04

Commission against the machine

Verify limits, stopping behaviour, recovery, synchronisation and response under fault conditions.

Documentation & requirement capture

Official CODESYS documentation and project inputs

Use the official product page for current product information, then provide the project-specific details below so the architecture can be reviewed against the actual machine or system.

Application scopeMachine/process functions, operating modes, cycle-time expectations and whether the project is new design, retrofit or migration.
Target & software baselineController/IPC, CPU architecture, operating system, CODESYS runtime, device package, compiler profile and existing project version.
I/O & communicationLocal/remote I/O, fieldbuses, Industrial Ethernet, OPC UA, MQTT, controller-to-controller links and required protocol roles.
HMI & user accessDisplay hardware, browser clients, independent HMI requirements, alarms, trends, recipes, user roles and remote-service policy.
Motion & functional safetyAxis count, drives, kinematics, CNC/robotics requirements, safe I/O, safe communication and required PL/SIL where relevant.
Deployment & lifecycleController quantity, sites, licensing, backups, certificates, update process, rollback expectations and maintenance ownership.