CODESYS Automation & Control Systems
Use the Hardware That Fits. Keep the Controls Architecture Consistent.
CODESYS gives machine builders one programming environment across multiple controller platforms. Automation Solutions uses that flexibility to help OEMs reuse engineering, reduce dependence on a single hardware supplier, and keep more options open as machines, volumes, and supply conditions change.
One Environment. More Hardware Choices.
Standardize the engineering without locking the machine to one controller brand.
CODESYS is a manufacturer-independent IEC 61131-3 control platform. The same engineering environment can be used across many CODESYS-based devices, making it easier to reuse software, move between hardware platforms, and support multiple machine configurations with a more consistent engineering workflow.
Reuse More Engineering
Common libraries, programming conventions, and application code can move more easily between CODESYS platforms.
Protect Hardware Options
If one controller family becomes unavailable or unsuitable, the machine is not necessarily tied to starting over in a different programming environment.
One Service Environment
Your engineering and service teams can work in the same CODESYS environment across multiple controller brands.
No Standard IDE License Fee
The standard CODESYS Development System is available free of charge, so servicing and monitoring a machine does not require an annual license for the base engineering environment.
Why CODESYS
Control software developed as a platform in its own right.
CODESYS is developed by an independent automation-software company rather than being tied to one manufacturer's controller family.
That matters to OEMs because the programming environment, runtime technology, motion tools, libraries, visualization, and communications ecosystem can span many different hardware choices.
Automation Solutions uses that independence as an engineering tool—not as a reason to force CODESYS into every machine.
Platforms We Support
Different hardware. A familiar engineering environment.
Our common CODESYS architectures include WAGO, Schneider Electric, Opto 22, Automation Solutions Raspberry Pi-based controllers, and other appropriate CODESYS targets. We also work with customer-selected CODESYS hardware where the application warrants it.
WAGO
Controllers and remote I/O for modular machine and distributed I/O architectures.
Schneider Electric
Commonly M241 and M262-class applications, along with Schneider remote I/O and machine-control components.
Opto 22
CODESYS-capable groov EPIC systems where the platform and application are a strong fit.
AS Raspberry Pi Controls
Open, Linux-based CODESYS systems when the application benefits from deeper platform access and flexible integration.
Supply-Chain Resilience
Hardware flexibility matters most when the preferred hardware is not available.
During the pandemic-era controls shortages, CODESYS gave Automation Solutions additional paths to deliver systems when some traditional PLC families were difficult or impossible to source.
For an OEM, that flexibility can preserve the programming environment, reusable application code, engineering practices, and service knowledge while the underlying controller brand changes.
Choose the Architecture That Fits
We keep both CODESYS and Mitsubishi in the toolbox for a reason.
We do not believe every machine should use CODESYS—and we do not believe every machine should use a traditional PLC. The right architecture depends on what the machine actually needs to do.
Tightly integrated machine control
Mitsubishi can offer exceptional value when deterministic machine control, high-speed hardware functions, direct interrupts, compact integration, and deep access to a tightly engineered hardware ecosystem matter.
- Excellent cost-performance for many OEM machines
- High-speed hardware functions and deterministic control
- Tight PLC, motion, servo, and drive integration
- Strong fit when the application maps naturally to the platform
Portable software and flexible architecture
CODESYS becomes especially compelling when hardware independence, code portability, distributed motion, or a less conventional machine architecture matters more than staying inside one hardware family.
- One programming environment across multiple brands
- More flexibility when controller availability changes
- Advanced distributed EtherCAT motion with SoftMotion
- Open-platform options when the application needs them
Motion, CNC & Robotics
When the motion problem no longer fits a conventional template.
Traditional PLC motion platforms can be extremely effective when the application fits the motion model they were designed around. CODESYS SoftMotion becomes particularly compelling when the motion problem is more distributed, more custom, or less easily expressed within a vendor-specific template.
Distributed EtherCAT Motion
Coordinated servo architectures using EtherCAT and software-based motion control.
CNC & G-code
Applications where G-code execution and CNC motion can live alongside the IEC 61131-3 control application.
Robotic Transformations
Mechatronic and robotic applications that require coordinate transformations, kinematics, and motion behavior beyond a simple axis template.
CODESYS Capabilities
One engineering environment for more than PLC logic.
IEC 61131-3
LD, ST, FBD, SFC and reusable application libraries.
PLC Control
Machine sequencing, diagnostics, recipes, and communications.
SoftMotion
Servo, coordinated motion, axis groups, and distributed motion.
CNC / G-code
G-code execution and CNC motion where supported.
Visualization
Local and web-based visualization where supported.
EtherCAT
High-performance distributed I/O and motion.
Modbus
TCP and RTU integration for devices and subsystems.
OPC UA
Structured machine data and external-system integration.
MQTT
Machine-to-cloud or machine-to-service communication.
Remote I/O
WAGO, Schneider, Mitsubishi, and other networked I/O.
When We Control the Platform
CODESYS can become more than a PLC environment.
Some capabilities depend on how open the underlying controller is. They should not be assumed on every WAGO, Schneider, Opto 22, or other OEM implementation.
On Automation Solutions Raspberry Pi-based systems, where we control more of the platform, the controller can combine CODESYS machine control with selected Linux capabilities.
- SQL databases and local data handling
- Remote desktop and service tools
- Custom Linux-side software and scripting
- I2C and SPI interfaces to board-level devices
- Custom communications and external applications
- Direct integration with purpose-built electronics where justified
Raspberry Pi-Based Industrial Control
High-volume computing hardware, used deliberately as an industrial controller.
Our Raspberry Pi-based systems are part of a supported controls architecture—not hobby hardware dropped into a machine without an engineering basis.
They can be paired with WAGO, Schneider, Mitsubishi, or other remote I/O, or in some applications with very little conventional I/O at all when the machine is primarily built around networked drives, servos, and intelligent devices.
The attraction is not simply low purchase price. It is the combination of high-volume computing hardware, Linux access, CODESYS, flexible networking, and the ability to integrate machine control with software capabilities that are harder to reach in a closed controller.
Serviceability
Your customer should not need an annual software subscription just to connect to the machine.
The standard CODESYS Development System is free to download and use. Paid add-ons and runtime licenses exist, but the base engineering environment itself does not carry a license fee.
For an OEM with machines in the field, that can reduce friction for service technicians, engineering teams, and customers who need to connect, monitor, troubleshoot, or modify a supported machine years after shipment.
Evidence to Add
Three proof points that will make this page stronger.
Pandemic supply-chain example
An anonymized OEM example showing how a CODESYS hardware change allowed AS to ship when the originally expected controller was unavailable.
SoftMotion / CNC example
A deployed machine using G-code, distributed motion, or robotic transformations.
Raspberry Pi control example
A real machine where Linux-side capabilities, remote I/O, or custom electronics created a meaningful customer benefit.
Frequently Asked Questions
CODESYS controls for OEM machines
Is CODESYS tied to one PLC manufacturer?
No. CODESYS is a manufacturer-independent IEC 61131-3 platform used by many controller manufacturers. The exact available features still depend on the runtime and hardware implementation selected.
Can code move from one CODESYS controller brand to another?
Often much more easily than moving between unrelated proprietary programming environments. Device-specific I/O, motion drivers, libraries, and hardware features still need to be addressed, so portability should be engineered rather than assumed to be automatic.
Does CODESYS eliminate hardware vendor lock-in?
It can reduce it substantially by keeping the application in a common engineering environment across multiple hardware choices. It does not make every controller identical.
Is the CODESYS programming environment free?
The standard CODESYS Development System is available free of charge. Some runtimes, device licenses, and optional professional or add-on tools can carry separate licensing costs.
Why would Automation Solutions choose Mitsubishi instead?
Because Mitsubishi can be an exceptional machine-control platform when deterministic performance, high-speed hardware functions, tight PLC/servo/drive integration, lifecycle, and cost-performance fit the application. We choose based on the machine rather than forcing one platform everywhere.
Do all CODESYS controllers provide Linux, SQL, I2C, and SPI access?
No. Those capabilities depend on the underlying hardware and how much of the platform is exposed. We emphasize them primarily on open platforms such as Automation Solutions Raspberry Pi-based controllers.
Can CODESYS handle motion, CNC, and robotics?
Yes, where the selected runtime and licensing support those functions. CODESYS SoftMotion and related tools can support coordinated motion, CNC/G-code, axis groups, and robotic kinematics.
Can Automation Solutions migrate a machine from one CODESYS hardware brand to another?
Yes. A common engineering environment can make that migration more practical. We evaluate device-specific I/O, fieldbus, motion, safety, libraries, and lifecycle requirements before recommending a change.
Choosing a Controls Platform?
Start with what the machine needs to do—not a logo on the controller.
We can help you compare CODESYS, Mitsubishi, and other architectures based on performance, motion, serviceability, hardware availability, lifecycle, and total machine economics.