ZF 8HP — Configuration

An 8HP behind IOcan is configured with the 8HP OEM Gateway controller (app name Gateway BMW OEM). The factory TCU keeps doing the shifting; the controller gives it the engine torque and other engine signals it expects, and reports gear state back to the car.

Aftermarket ECU ─inputs→  8HP OEM Gateway  ─CAN preset→  Factory 8HP TCU
   (RPM, TPS,             (emulates the engine,          (mechatronics)
    torque, …)             reports gear state)
Outputs / dash  ←────────  gear, mode, speed  ←─────────  TCU state

This page summarizes the setup workflow. The full field and table reference is in the 8HP OEM Gateway controller reference; the shared concepts (signal flow, controllers, CAN presets) are described in Configuration Concepts.

Prerequisites

  • A factory 8HP TCU on the transmission, powered and woken by IOcan (see Wiring).
  • The transmission's CAN networks wired to IOcan.
  • Engine signals available to the device — from the ECU over CAN or on physical pins — at minimum engine RPM and a torque source.
  • For paddle or selector control, an OEM or emulated shifter.

Setup workflow

  1. Add the 8HP OEM Gateway controller to the configuration.

  2. Add a CAN bus for the transmission and pair the matching transmission-emulation preset for your platform and generation:

    Platform PT-CAN PT-CAN2
    F-series 8HP, Gen 1 BMW 8HP PT_CAN Fxx Gen1 BMW 8HP PT_CAN2 Fxx Gen1
    F-series 8HP, Gen 2 BMW 8HP PT_CAN Fxx Gen2 BMW 8HP PT_CAN2 Fxx Gen2
    G-series 8HP, Gen 2 BMW 8HP PT_CAN Gxx Gen2 BMW 8HP PT_CAN2 Gxx Gen2
    G-series 8HP, Gen 3 BMW 8HP PT_CAN Gxx Gen3 BMW 8HP PT_CAN2 Gxx Gen3

  3. Assign the engine inputs: RPM, throttle/pedal position, manifold and atmospheric pressure, temperatures, and a torque source. Mandatory signals missing → the controller faults and the transmission will not run.

  4. Choose a torque calculation method and fill the tables it needs:

    Method How torque is produced
    Torque Tables Looked up from measured engine data (TPS·RPM, MAP·RPM)
    External Inputs Taken straight from ECU torque inputs
    Internal Calculation Air-model from displacement, MAP, and VE tables
    Fuel Calculation / v2 From injector flow and fuel energy
    Fuel Only / Air Only Single-path variants of the above

  5. Route the outputs you need — current gear, gearbox mode, reverse light, vehicle speed, and the torque-management handshake (cut/blip requests) — to CAN or pins.

DBW Modifier

For clean clutchless shifts, the optional DBW Modifier momentarily overrides the electronic throttle: a torque cut on upshifts and a throttle blip on downshifts, each calibrated with per-gear tables. See the controller reference for the table axes and parameters.

Troubleshooting

  • Transmission won't engage / faults at start — a mandatory input (RPM or a torque source) is unassigned.
  • Harsh or lazy shifts — the TCU is getting a poor engine torque value; verify the torque method and its tables.
  • Shifts but no rev-match / driveline shock on manual shifts — enable and calibrate the DBW Modifier cut/blip tables.
  • Wrong road speed — check diff ratio and wheel diameter parameters.
  • TCU keeps sleeping — route and drive the transmission wakeup output.