Input mapping

tip

It's highly recommended to understand Signal flow functionality before studying input mapping.

Input mapping allows you to connect physical inputs (GPIOs) to OPHION inputs.

All settings are located in the /io directory of the controller. OPHION processes up to two analog inputs (level_INPUT and level2_INPUT) and two digital inputs (IN1_INPUT and IN2_INPUT). These inputs can be mapped to physical inputs or receive values through the Ophion control CAN message.

Parameters

Available input mapping parameters in the /io directory:

Parameter	Description	Range
level_INPUT	Maps analog input 1 to a physical input	Input ID List Use 0,255 for CAN_input
level2_INPUT	Maps analog input 2 to a physical input	Input ID List Use 0,255 for CAN_input
IN1_INPUT	Maps digital input 1 to a physical input	Input ID List Use 0,255 for CAN_input
IN2_INPUT	Maps digital input 2 to a physical input	Input ID List Use 0,255 for CAN_input

Physical inputs

When mapping to physical inputs, only the first parameter value is required.

• For analog inputs: Set the corresponding GPIO input ID
• For digital inputs: Set the corresponding GDIN or DIN input ID

Input ID List

note

• GDIN (Gpio DIN) represents a digital input on a GPIO pin
• The second input value is the device address, typically 0

Input from CAN

To receive input via CAN, set the parameter to 0,255. This configures the input to read from the CAN message.

Sets CAN control message offset. MSG ID = can_offset + addr Default 0x610
Range [0x600 - 0x700]

tip

• CAN and physical inputs can be used simultaneously.
• If you use Driver API command, this CAN message and all analog inputs will be overriden.