Build construction, agricultural, municipal, material-handling and other mobile machines around rugged controllers, displays, distributed I/O, motion sensors and connected-service architecture designed for vibration, weather and wide temperature ranges.
Use the controller as the core, distribute I/O close to actuators and sensors, provide operator interaction through rugged HMIs and add motion feedback and remote services only where the machine architecture needs them.
Rugged PLCs for mobile machines, including standard and safety-capable variants.
Rugged graphical HMIs for machine operation, diagnostics and controller integration.
Bring sensor inputs and actuator outputs closer to remote machine sections.
Coordinate hydraulic functions, motion feedback, operator controls and distributed I/O under vibration and weather exposure.
Combine controller, ISOBUS/CAN communication, speed/position sensing and operator display functions.
Manage multiple hydraulic and auxiliary functions with rugged controllers and local field I/O.
Use mobile controls, encoders, HMIs and network interfaces where CAN and Ethernet systems must coexist.
ifm's current ecomatmobile architecture connects rugged control with CAN-based field devices, Ethernet where needed and remote-data services for diagnostics, fleet visibility and maintenance.
| Current route | Typical scale | Protection | Interfaces / role | Use when |
|---|---|---|---|---|
| CR710S / CR711S | 37 / 60 total I/O | IP67 | CAN + Ethernet; safety-capable family | Medium mobile machines |
| CR720S / CR721S | 98 / 124 total I/O | IP67 | More I/O for complex machines | Large distributed mobile systems |
| CR403S / CR413S | 24 / 32 total I/O | IP20 | Compact controller architecture | Smaller machines / protected mounting |
Start with the machine I/O, actuators, communication buses, safety functions and operator workflow. Then select the controller and distributed architecture.
Count digital, analogue, frequency, resistance and PWM/H-bridge requirements before selecting the control family.
Map engine ECU, display, distributed I/O, sensors and service interfaces before hardware selection.
Decide whether the controller is exposed on the machine or protected in an enclosure; this changes the appropriate IP architecture.
Define the actual safety functions and target integrity before selecting a safety-capable controller.
Choose display size, touch/key operation and controller functionality around the operator task.
Add mobile IoT only where remote access, data collection or fleet management provides value.