CAN Object Input

Overview

A CAN Object Input is a single named CAN object decoded by a CAN Preset for a supported device (a dash, ECU, shifter, keypad, paddle…). It is a technical input created by the preset — you do not add or configure one by hand. When you add a CAN Preset it creates these inputs automatically (one per object it exposes) and fills in their value from the incoming CAN traffic. Your only job is to use the input: reference it by its alias wherever you need that value (in maps, drivers, other IO). If instead you need to decode a signal from a raw frame yourself, use a CAN Bus Input.

Prerequisites

  • A defined CAN bus for the channel the device is on — see Working with the CAN Bus.
  • A CAN Preset added for the device — adding it creates the object inputs.

How it's created

  1. Add the device's CAN Preset on the relevant CAN bus.
  2. The preset automatically creates a CAN Object Input for each object it exposes.
  3. Reference the input you need by its alias from your maps/drivers/other IO. There is nothing to create or wire manually, and the decoding cannot be changed — the preset owns it.

Settings reference

A CAN Object Input has no user-configurable settings — the preset provides its value and its alias (which you may rename).

Example — using a shifter position object

  1. Add the shifter/paddle device's CAN Preset on its CAN bus.
  2. The preset creates an input such as Gear Position automatically.
  3. Reference Gear Position from your shift logic — no further configuration.

Troubleshooting

  • The object input doesn't exist: confirm the CAN Preset that provides it is added and on the correct CAN bus.
  • Reads nothing: check the CAN bus baud rate and that the device is powered and transmitting.
  • Value looks wrong: the decoding is owned by the preset — verify you selected the correct preset/variant for your device.