New Eagle Adds CODESYS Support to Rugged Production ECUs

New Eagle, known for its Raptor suite of rugged production ECUs, has quietly begun offering native CODESYS integration on select controllers. Historically designed for MATLAB/Simulink workflows, these ECUs now support the widely adopted IEC 61131‑3 automation standard, marking a meaningful shift toward developer flexibility.

Rationale Behind the Move: Market-Ready and Developer-Friendly

CODESYS is celebrated in industrial automation for its hardware-agnostic IEC 61131‑3 programming environment. It supports multiple languages—Ladder Logic, Structured Text, Function Block Diagrams, and more—allowing engineers to align with varying workflows. By enabling CODESYS on its ECUs, New Eagle addresses a common constraint: locked workflows tied to Simulink models alone. This move opens the door for developers who prefer or require standard PLC tools without swapping hardware.

Technical and Commercial Upside

• Multi-lingual development: Engineers can now use their preferred IEC‑standard languages, simplifying porting legacy PLC code and accelerating development cycles.
• Vendor-independence: CODESYS introduces portability across hardware platforms—an arsenal for OEMs aiming to avoid vendor lock-in.
• Hardware remains the same: Support has been added via firmware updates or new configuration options; customers don’t need to redesign physical control systems.

Balancing Perspective: Benefits vs. Caveats

While enthusiasm for CODESYS is high, particularly in off‑highway automation and industrial controls, experienced practitioners urge caution. Maintenance teams may face increased hardware variability and vendor-specific quirks; integration testing remains critical .

Nevertheless, many users embrace CODESYS for its flexibility, powerful diagnostic features, and capacity to treat ECUs as mini industrial PCs—ideal for field updates or telematics expansion.

Context in Aerospace and Off‑Highway Markets

For aerospace, mobile machinery, and rugged vehicle systems, reliability and deterministic control matter most. CODESYS has become a go-to in these environments—ISOBUS, J1939, and CANopen stacks are already ship‑tested in heavy equipment and rail systems. The addition of CODESYS on New Eagle’s ECUs aligns with ongoing trends toward open automation platforms, virtualization, and firmware-over‑the‑air updates.

Bottom Line

New Eagle’s embrace of CODESYS is a strategic pivot: one that bridges the gap between model-based and PLC-centric development. For OEMs in mobile and aerospace industries, this hybrid support could significantly reduce engineering timelines and integrate legacy codebases more seamlessly.

The proof will lie in field adoption. Will development teams embrace this dual-mode flexibility? Can support and part‑management systems adapt? If executed well, New Eagle may well help catalyze a new era of adaptable, portable control systems.

• What Changed: New Eagle ECUs now support the CODESYS runtime, enabling IEC 61131‑3 programming (e.g., Ladder Logic, Structured Text).
• Why It Matters: Engineers gain language flexibility and potential hardware portability without swapping ECUs.
• What to Watch: Adoption hurdles include team familiarity, version compatibility, and maintaining control over hardware sourcing.
• In Perspective: Places New Eagle’s ECUs firmly within the modern automation ecosystem—opening doors to virtualization, telematics, and open control architectures.