ifm · ioControl

ifm Mobile I/O Modules

Reduce long vehicle wiring runs by placing rugged configurable I/O close to sensors, valves and actuators. Current ioControl modules connect to the mobile controller over CAN and can also serve as CODESYS-programmable field controllers where the application needs local logic.

ioControlCANopenJ1939IP65 / IP67E1 approval
ifm CR2052 ioControl mobile I/O module
Environment−40…85 °CCurrent core ioControl routes
Field networkCANCANopen / J1939 architecture
I/O scaleUp to 16 I/OCR204x / CR205x routes
Field housingIP65 / IP67Rugged mobile installation
Distributed machine wiring

Move the I/O to the part of the machine where the signals actually exist

01
Shorter harnesses

Decentralised connection

Place modules near remote machine functions to reduce individual sensor/actuator wire runs back to the main controller.

02
Flexible channels

Configurable input types

Current modules support configurable binary, frequency, analogue and resistance input routes depending on model.

03
Actuator control

Digital / PWM outputs

Output-focused modules can drive valves and actuators through digital and PWM-capable channels.

04
Local intelligence

Controller inside

ioControl can operate as a configurable CANopen participant or as a CODESYS-programmable field controller.

Applications

Best suited to machine sections that are physically remote from the main controller

01
Hydraulic valve bank

Remote actuator control

Place output/PWM capability near hydraulic valves and reduce cable runs across booms or chassis sections.

02
Sensor cluster

Remote machine inputs

Collect analogue, digital, frequency and resistance signals near the measurement points.

03
Attachment / implement

Local programmable node

Use local logic where an attachment or implement needs independent functions plus CAN communication to the main vehicle.

ifm CR2042 M12 ioControl module
CAN-based architecture

ioControl bridges local sensors and actuators to the mobile controller

Digital and analogue sensors, frequency/resistance inputs and actuator outputs are handled locally; data and configuration are exchanged through CAN. Current modules offer two CAN interfaces on the main CR204x/CR205x families.

InputsSensors
Field nodeioControl
Vehicle busCANopen / J1939
ControlecomatController
Current core models

Select connector style and I/O mix together

ifm CR2052
DEUTSCH MIXED I/O

CR2052

Mixed input/output ioControl module with DEUTSCH field connection.

  • 8 inputs / 8 outputs
  • Analogue, resistance and digital input capability
  • Digital / PWM / PWM-I outputs
  • 2 CAN interfaces
View official ifm information →
ifm CR2051
DEUTSCH OUTPUT

CR2051

Output-focused ioControl route for distributed actuator control.

  • 16 outputs
  • Digital / PWM capability
  • 2 CAN interfaces
  • −40…85 °C
View official ifm information →
ifm CR2042
M12 MIXED I/O

CR2042

Mixed I/O route with M12 field connections.

  • 8 inputs / 8 outputs
  • Digital / analogue / frequency / resistance inputs
  • Digital / PWM outputs
  • 2 CAN interfaces
View official ifm information →
Model familyConnectorI/O emphasisTotal I/OCAN interfaces
CR2050 / CR2040DEUTSCH / M12Inputs16 inputs2
CR2051 / CR2041DEUTSCH / M12Outputs16 outputs2
CR2052 / CR2042DEUTSCH / M12Mixed I/O8 inputs / 8 outputs2
CR3025Compact routeSmall mixed node3 inputs / 1 output1
Engineering criteria

Map channel type and actuator current before selecting the module

“16 I/O” is not enough information

The correct module depends on whether those channels are binary, analogue, frequency, resistance, PWM or current-controlled outputs, and on the field connector standard used by the machine.

InputsDigital, analogue, frequency, resistance and ratiometric capability varies by model
OutputsDigital, PWM and PWM-I capability varies by model
ConnectorDEUTSCH or M12 families
CAN2 interfaces on CR204x/CR205x; protocol/configuration depends on application
ProgrammingSelected modules can be programmed using CODESYS
ApprovalCurrent ioControl family carries E1 type approval for vehicle use
Requirement capture

Inputs required to select the I/O module

Input listDigital, analogue V/I, resistance, frequency or ratiometric signals.
Output listDigital, PWM, PWM-I, H-bridge and current requirements.
ConnectorM12 or DEUTSCH machine harness architecture.
NetworkCANopen, J1939 and controller topology.
Local logicPassive/configurable I/O or local CODESYS functionality.
EnvironmentTemperature, IP requirement, vibration and road-use conditions.