The device rejected my configuration

Applies to: IOcan · Standalone controller. What this means

A configuration fault means the device read your configuration and found something it cannot build. It is not a hardware failure and nothing is damaged — the device is telling you which element is wrong before it tries to drive a gearbox with it.

Every one of these has a code, and Fault codes documents all of them. That page is organised by code. This one is organised by what you probably did, which is more use when you are looking at a number and do not yet know what it refers to.

Read the Component ID, not just the code

Every configuration fault carries a Component ID alongside the code, and it names the specific input, output, map or pin at fault. The code tells you the kind of mistake; the Component ID tells you where. Chasing the code without the ID means searching your whole configuration instead of one element.

The common ones

Something mandatory is not assigned

0x0001 input · 0x0011 output · 0x0031 map

The driver you chose requires an element you have not filled in. This is by far the most common rejection on a first configuration, and the usual culprit is the brake signal — mandatory on both gateways, and carried by almost no ECU stream, so it has to come from a device input.

The mandatory sets differ per controller. See Signal requirements and Unassigned mandatory elements.

Two things are fighting over one pin

0x0014 two outputs on the same pin · 0x0005 two frequency inputs on one pin

A pin does one job. Several controller pins are shared between functions — on IOcan the low-current outputs share pins with analog inputs — so assigning both is a configuration error rather than a wiring one. The IOcan pinout and standalone pinout list which pins are shared.

The pin cannot do that

0x0081 no power stage · 0x0082 no analog output · 0x0083 no digital output · 0x0006 no frequency input

You asked a pin for a capability it does not have. The fastest way to check before you write is the pinout viewer in the Configuration workspace: it lists what each pin is capable of, and that list is the same constraint the device enforces. See the configuration workspace.

Duplicate IDs

0x0003 inputs · 0x0013 outputs · 0x0033 maps · 0x0015 datalogger channels

Two elements claim the same identifier. Usually the result of copying an element and not changing its ID, or of merging two configurations by hand.

A CAN element has no bus to live on

0x0051 input · 0x0052 output · 0x0053 entity · 0x0054 two instances on one bus

The bus has to exist before anything can be put on it. Add the CAN network first, then the presets and frames that use it. See Working with the CAN bus and CAN configuration faults.

A map axis is not monotonic

0x0037 X axis · 0x0038 Y axis

Axis values must increase across the table. An out-of-order or repeated breakpoint makes interpolation undefined, so the device refuses the map rather than guessing. See Scaling and maps.

The controller itself would not build

0x0071 configuration would not decode · 0x0072 controller would not be created

Something structural is wrong rather than one element being misassigned. Re-check the General section — transmission, ECU and shifter — and confirm the firmware version supports the driver you selected: Feature → firmware.

Before you go looking

  • Faults are not stored across power cycles. Read them in the same power session. A fault that vanished when you cycled the ignition is gone, not fixed.
  • Fix the first one first. One missing element often raises several codes; clearing it clears them.
  • Import from the device before you rebuild. If the configuration on the device is the only copy of a working state, keep it — see connect your device.