CAN Object Input » History » Version 2
Adam Klama, 06/21/2026 03:02 PM
| 1 | 1 | Adam Klama | # CAN Object Input |
|---|---|---|---|
| 2 | |||
| 3 | ## Overview |
||
| 4 | A **CAN Object Input** is a single named **CAN object** decoded by a |
||
| 5 | 2 | Adam Klama | [CAN Preset](Working_with_the_CAN_Bus#can-presets) for a supported device (a |
| 6 | 1 | Adam Klama | dash, ECU, shifter, keypad, paddle…). |
| 7 | |||
| 8 | It is a **technical input created by the preset** — you do **not** add or configure |
||
| 9 | one by hand. When you add a CAN Preset it creates these inputs automatically (one |
||
| 10 | per object it exposes) and fills in their value from the incoming CAN traffic. Your |
||
| 11 | only job is to **use** the input: reference it by its alias wherever you need that |
||
| 12 | value (in maps, drivers, other IO). |
||
| 13 | |||
| 14 | If instead you need to decode a signal from a raw frame yourself, use a |
||
| 15 | 2 | Adam Klama | [CAN Bus Input](CAN_Bus_Input). |
| 16 | 1 | Adam Klama | |
| 17 | ## Prerequisites |
||
| 18 | - A **defined CAN bus** for the channel the device is on — see |
||
| 19 | 2 | Adam Klama | [Working with the CAN Bus](Working_with_the_CAN_Bus). |
| 20 | 1 | Adam Klama | - A **CAN Preset** added for the device — adding it creates the object inputs. |
| 21 | |||
| 22 | ## How it's created |
||
| 23 | 1. Add the device's **CAN Preset** on the relevant CAN bus. |
||
| 24 | 2. The preset automatically creates a CAN Object Input for each object it exposes. |
||
| 25 | 3. Reference the input you need by its alias from your maps/drivers/other IO. |
||
| 26 | |||
| 27 | There is nothing to create or wire manually, and the decoding cannot be changed — |
||
| 28 | the preset owns it. |
||
| 29 | |||
| 30 | ## Settings reference |
||
| 31 | |||
| 32 | A CAN Object Input has **no user-configurable settings** — the preset provides its |
||
| 33 | value and its alias (which you may rename). |
||
| 34 | |||
| 35 | ## Example — using a shifter position object |
||
| 36 | 1. Add the shifter/paddle device's **CAN Preset** on its CAN bus. |
||
| 37 | 2. The preset creates an input such as `Gear Position` automatically. |
||
| 38 | 3. Reference `Gear Position` from your shift logic — no further configuration. |
||
| 39 | |||
| 40 | ## Troubleshooting |
||
| 41 | - **The object input doesn't exist:** confirm the **CAN Preset** that provides it |
||
| 42 | is added and on the correct CAN bus. |
||
| 43 | - **Reads nothing:** check the CAN bus baud rate and that the device is powered and |
||
| 44 | transmitting. |
||
| 45 | - **Value looks wrong:** the decoding is owned by the preset — verify you selected |
||
| 46 | the correct preset/variant for your device. |
||
| 47 | |||
| 48 | ## Related |
||
| 49 | 2 | Adam Klama | - [CAN Bus Input](CAN_Bus_Input) — decode a signal from a raw frame by hand. |
| 50 | - [CAN Object Output](CAN_Object_Output) — a named object the preset |
||
| 51 | 1 | Adam Klama | sends. |
| 52 | 2 | Adam Klama | - [Working with the CAN Bus](Working_with_the_CAN_Bus) |