Release Notes

Firmware 2.1

CAN input timeout modes: UseFault now works

UseFault has been in the timeout-mode list for a long time, and in the documentation, but the firmware had no case for it. Selecting it left the timeout mode undefined and the configured Fault value was dropped entirely.

From 2.1 all three modes do what they say:

Mode After the timeout elapses
UsePrevious Holds the last received value, indefinitely
UseDefault Substitutes Default value
UseFault Substitutes Fault value

It does not raise a fault. The name is misleading — it substitutes a second, separate value. That is still worth having: give Default and Fault different values and the datalogger tells you whether a signal was never received or dropped out mid-drive.

Two related fixes went in with it:

  • The datalogger now shows the substituted value. Previously the log kept reporting the last received value after a timeout while the control path used the substitute, so the two disagreed exactly when you needed them to agree.
  • The timeout counter no longer grows without bound in UsePrevious mode.

Both Default value and Fault value are in raw units. They are substituted before the raw → out scaling and go through it like any received frame value. Full detail on CAN Bus Input.

Maths inputs: And, Or and Xor now work

Three of the seven operations had no case in the firmware. Selecting one left the input pointer null, and the null was registered as the created input — so the channel did not exist and anything referencing it read nothing, silently.

All seven operations are implemented from 2.1, and an operation the firmware does not recognise now raises fault 0x00D1 instead of registering nothing.

The bitwise operations are scaled like their siblings — the result is multiplied by the multiplier and divided by 1024, so 1024 is the neutral multiplier. Because a boolean on this device is 1024 or 0, and 1024 is a single bit, that makes them usable as logical operators between two Compare inputs. Details and the trap when an operand is not a boolean: Math Input.

Enable interpolation is honoured on CAN inputs

⚠️ Action required on existing configurations.

Before 2.1 the raw → out scaling on a CAN bus input was applied whether Enable interpolation was ticked or not — the setting was read into an empty branch and had no effect. From 2.1 it is honoured: with it off, the input reports the decoded frame value and Raw min/max, Out min/max and Saturate are unused.

The setting defaults to off, and the transmission-configuration editor never wrote it. So a CAN bus input made before 2.1 is scaling today and will report the raw frame value once the device is flashed with 2.1.

What to do: open every CAN bus input that has a raw → out scaling, tick Enable interpolation, and re-save the configuration. Then check each one in the datalogger — the symptom of a missed input is a channel reading in raw frame units, usually a much larger number than expected. Nothing faults.

Turning it off is now a useful thing to do deliberately: it is how you get the undecoded frame value out, for a Map Input to scale.

Torque calculation methods renamed

The Torque calculation method names were changed to run on a single axis — what the torque is derived from — because the old names implied a version relationship that never existed.

Old name New name
External Inputs ECU Reported Torque
Fuel Calculation v2 Fuel + Air (arbitrated)
Air only calculation Air Model
Fuel Only Calculation Fuel Model
Internal Calculation Throttle + MAP Estimate
Torque Tables Measured Torque Tables

Existing configurations are unaffected. The stored value is numeric, so a configuration made before 2.1 loads and resolves to the same method as before, under its new name.

In particular, Fuel Calculation v2 and Fuel Only Calculation were never two versions of one method. They are two different methods, and only the first cross-checks the fuel estimate against an air model. Their new names say so.

Fuel Calculation (v1) removed

Action required if your configuration selected it. Fuel Calculation (v1) has been removed from the configurator. It was never implemented — the firmware carried no branch for it, so selecting it produced a constant −123 instead of a torque value.

If a configuration made before 2.1 selected it, the method field reads back blank after loading. Choose a real method before driving the car; a transmission fed a constant torque value sets clutch pressure for an engine state that does not exist.

See Engine torque estimation for the methods, what each one needs, and how to verify the result.

Firmware 2.0.1

This section captures the mandatory hardware and signal-level requirements for the 2.0.1 firmware release, and the changes it ships. It serves as a reference for testers, installers, and customers to verify that their hardware stack and wiring meet the minimum specifications before flashing the new version.

Hardware prerequisites

  • Device: units whose serial number is GCU2202001 or higher (the prefix is part of the serial as stamped on the unit) require a hardware upgrade to address some of the manufacturing issues. (Mandatory)
  • Signal-conditioner board: required only when interfacing with DCT GS7D36SG speed sensors. (Mandatory for DCT GS7D36SG installations)

Required signal inputs

Signal Source Connection method Notes
Brake-pedal position Hydraulic switch or position sensor Analog IN or CAN On/Off signal
Engine RPM Crank/cam sensor or ECU Frequency IN or CAN
Throttle position (TPS) ECU / DBW Analog IN or CAN
Accelerator pedal position sensor (PPS) ECU Analog IN or CAN
MAP sensor ECU Analog IN or CAN kPa
Injector pulse width or engine torque ECU Frequency IN (PW) or CAN (torque) Provide either PW (µs) or torque (Nm)

DCT GS7D36SG-specific requirements

  • Install the signal-conditioner board between the gearbox speed sensors and the device.

Test log

Transmission Status
GS7D36SG Tested
DQ500
DQ250
DL800 Tested
7DT45 (PDK) Tested
TR9080

Implemented features and bug fixes

Transmission support — general

  • Improved reliability of valve control

Transmission support — dual clutch

  • Reimplemented closed-loop pull away (take up)
  • Added static tables for clutch pressure–duty and RPM–duty for clutch pressure
  • Improved closed-loop shifting method
  • Improved handling of clutch-by-wire during driving
  • Improved ability to pull away using clutch-by-wire
  • Added feature: start from 1st gear after stop
  • Added limit of adaptations based on the transmission temperature

Communication

  • Improved CAN bus traffic handling
  • Improved F80 DCT preset for CAN bus
  • Improved MoTeC support
  • Added implementation of the ProSpeed MoTeC communication protocol
  • Reimplemented USB stack to improve stability of the connection with the PC

OEM TCU support

  • 8HP45 and 8HP70: added support for OEM TCU over CAN bus
  • Added diagnostics for BMW 8HPxx transmissions
  • 911 997.2 PDK: added draft of support

Notice of obsolescence

In the upcoming releases the following functions are going to be removed and are no longer supported:

  • ZF 4HP transmission
  • NSX transmission
  • Mercedes 722.6 transmission
  • Aisin AA80E transmission
  • Aisin A960E transmission

Earlier releases

Changelogs for the 1.x firmware series, released under the product's earlier branding, are archived on Release history — legacy 1.x. They are a historical record: 1.x used different configuration software and is not configuration-compatible with 2.x.