Fueltech FT450 / FT550 / FT600 and FT500

Applies to: IOcan · Standalone controller. What this means

You have a ZF 8HP or a Porsche PDK to run and a FuelTech FT450, FT500, FT550 or FT600 managing the engine. Plan the torque model early on this one: the FuelTech stream carries no torque broadcast and no injector pulse width, so the usual fuel-based estimate is not available to you.

This page covers the ECU side. The transmission side — which controller to add and which transmission preset to pair — is on the per-transmission pages (8HP · PDK).

Choosing between devices? Which device do I need? settles it in one question, and compares the IOcan CAN gateway with the standalone transmission controller.

Compatibility summary
Preset name in the app Fueltech
Torque broadcast No
Injector pulse width No
Recommended torque method Air Model

The preset belongs to the shared CAN layer, so it behaves the same behind the IOcan gateway drivers and the standalone transmission drivers.

⚠️ The fuel-based torque methods cannot be used with this preset. Both injector pulse-width inputs are exposed but never populated, and Fueltech does not broadcast torque either. That leaves Air Model as the only well-founded method — fill the VE tables, and validate carefully.

What this preset does not provide

The OEM gateways require seven mandatory inputs — eight on PDK. This preset does not carry the following, so they must be supplied from a device input, another CAN preset, or hand-mapped CAN inputs:

  • Brake status

A missing mandatory input raises fault 0x0001 and the driver will not run, so resolve these at the wiring stage rather than during commissioning. The full set is on the signal requirements matrix.

Signals this preset does provide: RPM, MAP, TPS, Pedal position (DBW), Oil temperature, Coolant temperature, Vehicle speed, IAT, Baro, Oil pressure, Fuel pressure, Lambda, EGT ×2

Injector PW (primary and secondary). exposed by the preset but never populated from the stream

Analog 5 and Analog 6. the stream frame carries only four analog channels

Wiring

  • One CAN bus between the ECU and the device.
  • The bitrate must match on both ends.
  • Termination: exactly two 120 Ω terminators, one at each physical end — the device's is software-switchable, so enable it only if the device sits at an end. See CAN Bus Diagnostics.
  • Twisted pair, routed away from ignition and injector wiring.

Setup

  1. Enable the CAN stream output in the ECU's own software, and note its base ID or configured frame set.
  2. Add a CAN bus in the device configuration, at the matching bitrate.
  3. Add the Fueltech preset to that bus.
  4. Assign the preset's signals to the inputs your controller needs.
  5. Supply the missing mandatory signals listed above.
  6. Choose a torque calculation method — see below.
  7. Set a Timeout and Timeout mode on every input feeding the torque estimate. UsePrevious holds a stale value forever and is the wrong choice on anything safety-relevant.

Torque signal setup and validation

No, and the fuel methods are unavailable too — see the limitation above.

Use Air Model. It needs displacement, a configured fuel type, and the VE tables. Note the all-or-nothing VE rule: VE is applied only when all three tables are present, and a partially filled set silently runs at 100 % VE.

The full method reference, the correction maps and the all-or-nothing VE table warning are on Engine torque estimation.

Validate before driving. The torque value sets clutch pressure, nothing checks whether it is plausible, and under-reporting is the direction that slips and overheats clutches. On a gateway it also sets the depth of every shift cut, because the TCU's requested torque limit is rescaled against it.

Verification checklist

  • [ ] RPM tracks the ECU's own RPM channel.
  • [ ] TPS reads zero closed and full scale at wide-open throttle.
  • [ ] MAP is plausible at idle and tracks load.
  • [ ] Every signal from the "does not provide" list above is present and correct from its alternative source.
  • [ ] Engine torque is present, changing, and passes the verification points.
  • [ ] No mandatory-input faults are active.