Feature → minimum firmware

Which release each capability first appeared in. Use it two ways: to check that the firmware on your device actually has the feature you are planning around, and — before reporting something as missing — to check whether you are simply on an older version.

The current series is 2.x. Anything below marked 1.x has been present since before 2.0 and is still there unless the limitations page says otherwise.

1.x and 2.x are not configuration-compatible. A version number here is a "first appeared in", not an upgrade path. See Release history — legacy 1.x.

The one that matters most

Feature Minimum Note
Running an OEM transmission control unit over CAN — the gateway 2.0.1 8HP45 and 8HP70. The entire gateway approach is 2.0.1 and later; earlier firmware is standalone control only
BMW 8HPxx diagnostics 2.0.1
Porsche 997.2 PDK 2.0.1 Recorded as a draft of support — see limitations

If you are integrating a factory TCU, 2.0.1 is the floor. Nothing earlier does it.

Engine torque

Feature Minimum Note
Fuel-based torque calculation 1.1.1 Introduced as FUEL model v2.0 (calc)
Torque model v3 1.1.2
Predefined fuel types, plus custom 1.1.2
Injector dead time and flex-fuel input per fuelling bank 1.1.2
Current torque method names 2.1 Six methods renamed — what changed
Fuel Calculation (v1) removed 2.1 Was never implemented. A configuration that selected it reads back blank

Shift torque management

Feature Minimum Note
DBW modifier 1.0.17 Pedal-override cut and blip. Standalone drivers only — not on the OEM gateways
DBW modifier on the 6HP family 1.0.19
DBW modifier with a single input and output 1.0.19 Previously required two of each
DBW modifier alongside cut/blip tables 1.0.19 Mode selected in general settings
Blip target axis on shift delta RPM 1.0.18 Previously load
ECU cut/blip: blip Y-axis on delta RPM 1.1.2

Setting up the ECU side is on Executing cut and blip in your ECU.

Inputs, outputs and configuration

Feature Minimum Note
Duty and Time modes on frequency inputs 1.0.18
Digital inputs and power outputs created manually 1.0.19 Previously generated automatically
Digital input invert 1.1.2
Digital input pulse-width measurement 1.1.2
Minimum, maximum and start gear 1.1.2 Until set, only gear 1 is used
Power output fault codes 1.0.19
Adaptation progress fault codes and status indicator 1.0.19
UseFault timeout mode on CAN inputs 2.1 Before 2.1 the mode was in the list but had no effect — details
Enable interpolation honoured on CAN inputs 2.1 Before 2.1 the scaling was always applied. Existing configurations need re-savingwhat to do
And / Or / Xor on maths inputs 2.1 Before 2.1 selecting one produced no input at all — details

CAN presets

Preset Minimum
Emtron, MoTeC 1.0.17
Ecumaster CAN switch board v3 1.0.19
Holley (beta at introduction) 1.0.19
BMW E92 M3 (beta at introduction) 1.0.19
BMW F80/F30 dashboard and ECU 1.0.19
VW MQB shifter 1.0.18
VW dash gear indication 1.1.1
Holley variant selection — Dominator, Terminator X MAX, Sniper 1.1.2
Haltech secondary injector pulse width 1.1.2
MoTeC ProSpeed protocol 2.0.1
Improved F80 DCT preset 2.0.1

The full compatibility list is on Supported Vehicles & Modules, and what each ECU preset does and does not carry is on Aftermarket ECU integration.

Dual-clutch control

Feature Minimum Note
6HP closed loop 1.0.17
Line pressure adaptation 1.1.1 Runs at the end of static adaptation
Adaptive clutch and line pressure in both open and closed loop 1.1.1
Launch control with pre-load 1.1.2
Selector dynamic adaptation 1.1.2
Clutch pressure (kPa) outputs 1.1.2 Replaced the percentage monitor
Raw shaft speed channels and outputs 1.1.2
Adaptation health check 1.1.2 Validates mandatory inputs before static adaptation runs, and inhibits it on critical faults
Closed-loop pull away reimplemented 2.0.1
Start from 1st gear after a stop 2.0.1
Adaptation limited by transmission temperature 2.0.1

What is not version-gated

Worth stating, because these get asked as version questions and are not:

  • Shift points, drive modes and lockup are in the transmission's own tune, not in any firmware version — why.
  • The mandatory input and output sets are per driver, not per version — signal requirements.
  • Fields that do nothing are not waiting on a version; they are listed on the limitations page.