Implementing CODESYS 3.5 on CAN Bus Displays for Mobile Machinery
Table of Contents
For system integrators in mobile machinery, engineering cost is measured not only in hardware price, but in engineering hours.
Each new HMI platform introduces questions:
-
Do engineers need to learn a proprietary API?
-
Can logic be reused across machine variants?
-
Will the display remain maintainable over a 5–10 year lifecycle?
This is where CODESYS-based CAN bus displays have gained traction.
By combining a standardized software environment with sufficient processing capability, the display evolves from a passive interface into a programmable system node within the machine architecture.
This article explains how CODESYS 3.5 on CAN bus displays benefits OEM system integrators, from development efficiency to long-term maintenance.
Why System Integrators Prioritize Software Ecosystem
System integrators rarely optimize for a single project.
Instead, they optimize for:
Reusability
Predictability
Maintainability across platforms
Displays that rely on proprietary tools or undocumented APIs increase risk and slow delivery.
In contrast, IEC 61131-3–based environments reduce friction when projects scale.
This is why CODESYS familiarity matters more than feature lists.
CODESYS as a Familiar Engineering Environment
CODESYS is widely adopted across industrial automation, PLCs, and mobile control systems.
For system integrators, this means:
No need to retrain teams for each display vendor
Established IEC 61131-3 workflows (ST, FBD, LD)
Consistent project structure across controllers and HMIs
Running a full CODESYS 3.5 runtime alongside high-resolution graphical interfaces, however, requires more than software compatibility—it requires sufficient processing headroom at the hardware level.
Multi-core application architectures allow protocol handling, logic execution, and UI rendering to run in parallel, preserving deterministic behavior even under load.
Streamlining J1939 Data Mapping with CODESYS in Mobile Machinery
Handling J1939 data is a core task in mobile machinery HMIs.
Within a CODESYS environment, J1939 integration benefits from:
Structured variable mapping
Reusable function blocks for PGN and SPN handling
Clear separation between communication logic and UI behavior
This approach avoids scattered, hard-coded parsing logic and makes J1939 handling transparent and maintainable—especially when machine variants introduce new ECUs or parameter sets.
For integrators managing multiple OEM platforms, this structure significantly reduces commissioning and debugging time.
Logic Reuse Across Machine Platforms
Profitability for system integrators depends on reuse.
With CODESYS-based CAN bus displays, integrators can:
Build shared libraries for common machine functions
Reuse logic across display and controller projects
Maintain consistent operator behavior across product families
This reuse model is far more efficient than rebuilding UI logic from scratch for each display model.
Integrating Display Logic into a Distributed Control Architecture
Modern mobile machinery increasingly adopts distributed control architectures.
When a CAN bus display supports CODESYS and provides sufficient local resources, it can:
Handle operator interaction logic locally
Process local sensor inputs
Control auxiliary outputs without involving the main vehicle controller
With up to 20 inputs and 8 outputs available directly on the display unit, system integrators can offload localized logic to the HMI, reducing controller complexity and CAN traffic.
This transforms the display from a visualization endpoint into an active logic node.
Simplifying Commissioning and Debugging
Commissioning often determines whether a project stays profitable.
CODESYS-based displays support:
Online monitoring of variables
Structured debugging tools
Clear signal traceability from CAN input to UI output
When issues occur—missing J1939 data, incorrect UI states, or timing conflicts—integrators can debug within a familiar environment instead of relying on vendor-specific utilities.
Supporting Long-Term Maintenance and Lifecycle Changes
Mobile machinery platforms frequently remain in service for many years.
During this lifecycle:
Software teams change
ECUs are updated
Features are added incrementally
Displays with ample onboard memory and storage allow integrators to maintain complex CODESYS projects, store documentation, and retain historical data directly on the device.
This simplifies updates and reduces dependency on external systems during field service.
Linux-Based CODESYS Displays for High-Performance HMIs
Many modern CAN bus displays are built on Linux-based platforms.
For system integrators, a Linux-based CODESYS display offers:
Higher graphical performance
Better multitasking capability
Support for complex HMI and video applications
When paired with sufficient CPU and memory resources, this architecture supports advanced HMIs without sacrificing determinism.
Sonnepower SPD Series Advantage
From an engineering standpoint, Sonnepower’s SPD series CAN bus displays provide a balanced platform for CODESYS-based integration:
Full support for CODESYS 3.5 runtime
High-performance multi-core application architecture
Extensive integrated I/O for local logic execution
Ruggedized design suitable for mobile machinery environments
These characteristics align closely with the real-world needs of OEM system integrators.
To discuss your system architecture or integration requirements, contact us or send an email to
📧 [email protected]