BMW Fxx DCT (DKG) — IOcan Support

Overview

The F-series BMW dual-clutch transmissions (DKG, Getrag GS7D36 family) run behind IOcan the same way the 8HP does — as an OEM gateway setup. The factory DKG mechatronics (TCU) stays in place and keeps doing the clutch and shift control; IOcan supplies the vehicle environment the TCU expects — engine torque above all — and reports gear state back to the car.

flowchart LR ECU["Aftermarket ECU<br>(RPM, TPS, torque, …)"] -->|inputs| GW["IOcan<br>Gateway BMW OEM<br>+ Fxx DKG presets"] GW -->|PT-CAN / PT-CAN2| TCU["Factory DKG TCU<br>(GS7D36 mechatronics)"] TCU -->|TCU state| GW GW -->|"gear, mode, speed"| OUT["Outputs / dash"]

This page covers the F-series (Fxx) units. For the E-series DKG (single PT_CAN) see Supported variants. For running a DKG without its factory TCU, see the DCT Standalone Drivers instead — that is the opposite approach.

Supported Fxx units

Unit Notes
GS7D36SG F-series 7-speed DCT
GS7D36BG F-series 7-speed DCT — different connector pin-out

Compatibility depends on the hardware version, TCU firmware, and the platform the transmission came from — verify your unit before starting the project.

Hardware & wiring

  • IOcan powers and wakes the transmission itself (KL30B, KL15/wakeup) — no external relays are needed.
  • Fxx units use both PT_CAN and PT_CAN2; wire both to the transmission-side CAN interfaces. The two Fxx variants differ only in connector pin assignment — see DKG wiring for the per-variant pin tables and the device pinout.
  • Engine signals must reach IOcan from the ECU, over CAN or on pins — see the mandatory list below.

Configuration

The DKG uses the BMW OEM Gateway controller (app name Gateway BMW OEM) — the same controller that runs the 8HP — paired with the DKG transmission-emulation presets instead of the 8HP ones. The full field and table reference on that page applies to the DKG as well.

  1. Add the Gateway BMW OEM controller to the IOcan configuration.
  2. Add a CAN bus for the transmission and pair the Fxx DKG transmission-emulation preset matching your platform and bus (PT-CAN or PT-CAN2).
  3. Assign the mandatory inputs: engine RPM, throttle position, pedal position, manifold pressure, coolant and oil temperature, and the brake switch — plus KL15/Ignition so the gateway can wake the TCU.
  4. Choose a torque calculation method — ECU Reported Torque, Fuel + Air (arbitrated), or Air Model — and provide what it needs.
  5. Route the outputs: gear display, reverse light, vehicle speed, transmission wakeup, and the torque-management handshake (engine torque + cut/blip requests) back to the ECU.
  6. Set Diff ratio and Wheel diameter so the speed emulation works.

Shifter

The F-series GWS gear selector is shared between the 8HP and DCT platforms, and the DCT version adds the Drivelogic button:

  • A DCT F-series shifter works with a DCT transmission directly.
  • Mixed combinations (an 8HP shifter with a DCT, or vice versa) are possible with protocol translation through IOcan.

See the GWS pinout and connection variants and the OEM shifter configuration.

Torque management during shifts

The DKG TCU requests a torque cut on upshifts and a blip on manual downshifts, exactly like the 8HP. The gateway relays these on the Cut request / Blip request outputs; your ECU executes them. Without ECU-side handling the box still shifts, but shift quality suffers — see Shift torque management.

Troubleshooting

The gateway troubleshooting list applies to the DKG unchanged: mandatory-signal configuration faults, poor torque values causing harsh shifts, missing cut/blip handling, wrong road speed from the speed parameters, and the TCU sleeping when wakeup is not routed.