Please enable JavaScript to view this site.

MaxxECU online help

Installed modules

 

Not installed or Installed indicates if the module is installed or not.

Note: Make sure connected CAN modules have a stable power supply when MaxxECU is powered and tries to communicate with module, otherwise and error is thrown.

 

 

Data transmission

 

Default CAN output protocol

Specifies the default CAN output protocol to be transmitted.

Disabled - No default CAN protocol is transmitted.

MaxxECU Default 1.2 - MaxxECU default CAN data protocol to be transmitted, for example connection to external Dash loggers (AIM, RaceTech eg).

MaxxECU Default 1.3 - MaxxECU default CAN data protocol to be transmitted, for example connection to external Dash loggers (AIM, RaceTech eg).

KMS CAN display - KMS CAN Display.

 

Protocol CAN Bus

Specifies which CAN bus to transmit/receive data on (only visible when more than one CAN Bus line exist in the connected MaxxECU).

 

CAN ID OFFSET

Specifies an offset value to be added to the above protocol IDs. Both positive and negative values can be used.

Note: Just be careful and make sure you know you are doing :)

 

Example CAN ID OFFSET usage

clip1863

KMS CAN Display protocol output, with not offset added.

 

clip1865

Example offset of "2".

 

clip1864

KMS CAN Display protocol output, with not offset "2".

 

message rate

Available for the default v1.3 protocol.

Default (10/50Hz) - 10Hz for the SLOW packages, and 50Hz for the FAST packages.

User settings - Set custom rate for SLOW/FAST packages.

 

slow package rate

Sets the speed of all the SLOW packages.

 

FAST package rate

Sets the speed of all the FAST packages.

Note: To determine which are SLOW/FAST packages, see MaxxECU Default CAN output page.

 

 

ODB-2

 

Enables/disables ODBII data output to enable diagnostics tools. Read disclaimer in MTune.

 

clip1064

When CAN OBD-II is enabled, a new setting page under CAN Bus is visible with some options.

 

 

OEM CAN protocols

 

Enables OEM (stock vehicle) CAN data to be transmitted and/or intercepted.

 

MaxxECU support the following OEM vehicles:

 

Audi A4 B7 VAG PL47 2006 (MED 9.1)

Audi RS6 C5 VAG PL45 (ME 7.1.1)

Audi S3 1.8T 2003 VAG PQ34 (ME 7.5)

Audi S3 8P VAG PQ35/36 2010 (MED 9.1)

Audi S4 B6 VAG PL46 (ME 7.1.1)

BMW E39 M5 (MSS52)

BMW E46 328i (MS42)

BMW E46 330i (MS43)

BMW E9x (MSS60)

Corvette C6 (GM E38 ECM)

Ford Focus RS/ST 2005 - 2012 (ME 9.0)

Ford Mustang 2011 - 2014

Lotus Elise/Exige 2007/2009

Mazda RX8

Nissan 350Z (ECCS 2)

Nissan Patrol TB48 Y61 (ME C23)

Porsche 996 2001 (ME 7.8)

Porsche Boxster 2003 with PSM (ME 7.8)

Skidoo 900R 2022 (Bosch MG1C)

Skidoo 900R 2024 (Bosch MG1C)

Skidoo 900T 2019-2022 (Bosch ME17.8.5)

Suzuki Jimny 2018

Toyota GT86

Volvo C30 (ME9.0) BETA

Volvo ME 7.0.1 (250kbit) BETA

VW Golf MK5 R32 MT VAG PL46.

VW Passat 3C (R36) VAG PQ36 2008 (MED 9.1).

Note: this list will be updated as we extend our support for other vehicles (based on demand).

 

Instr. cluster fuel flow correction.

Used to correct MaxxECU fuel consumption sent to the OEM dash, make sure to calibrate the MaxxECU fuel consumption before even try to adjust this value.

Note: only available on the supported OEM CAN protocols, so this settings might not be visible for your OEM CAN.

 

Wheel speed correction.

Used to correct the wheel speed coming from OEM ABS system (not available on all protocols) into the MaxxECU when an OEM CAN protocol is activated.

Verify and adjust the correction (%) value using an GPS or similar to make sure the wheel speed in MaxxECU is accurate.

Note: Make sure to enter correct wheel circumference in Speed/Gear --> Wheel setup before attempting to adjust this correction value.

 

Coding option

Used on some OEM CAN protocols where there are some "coding" options to make ABS/TC happy. Currently only used (and visible) by the Mazda RX8 protocol.

Coding 0 (mixed) - Initially we tried to "combine" a few codings we have seen, worked on some models.

Coding 1 (N3H8EM).

Coding 2 (N3H8EGI).

Coding 3 (N3K2 UAE Mazda RX8 JDM).

 

 

CAN powertrain controls

 

CAN Powertrain control protocols can be combined with the OEM CAN protocols, but be sure to check the documentation.

 

Power train control

BMW DCT (GS7D36SG) gearbox control.

CANTCU.

Dodge 8HP.

External TCU control.

Turbolamik control.

VAG Automatic pre 2012 (DQ250/DQ500/ZF 5HP) TCU control.

VW Haldex GEN1.

 

 

 

CAN peripheral controls

 

Volvo Power steering

BMW E9x EKPM (Fuel Pump Control Module)

BMW E85 EKPM (Fuel Pump Control Module)

 

 

CAN Shifter protocols

 

CAN shifter protocol

When activated, the RealTime Data value CAN Shifter Selector Position is updated with position/button data.

Note: The needed CAN messages to wakeup the shifter is automatically transmitted, so pay attention for CAN collisions.

 

BMW Fxx DCT

Transmitted CAN ID: 0x12F, 0x3FD, 0x202, 0x293, 0x393, 0x328

Receive CAN ID: 0x197.

Note: Do not activate in combination with the GEN2 DCT.

 

CAN Shifter Selector Position Data

Position

0

Not engaged

1

Mode change

2

Reverse

4

Neutral

8

Upshift

16

Downshift

32

Drivelogic UP

64

Drivelogic Down

 

 

Example how to setup a BMW M4 DCT shifter with the DSG control

clip2049

Example how to setup an Internal output to trigger the Transmission Neutral Switch.

 

clip2050

Example how to setup an Internal output to trigger the DCT/DSG Mode Switch.

 

 

Do the same for the Transmission Reverse Switch, Transmission UP shift, Transmission DOWN shift

 

 

clip2051

Setup the Shifter emulation in DSG settings.

 

 

 

CAN bit rate

 

CAN x Bitrate

The CAN bitrate has to be 500Kbit for use with MaxxECU CAN modules and most OEM protocols.

If you're using aftermarket dataloggers or dashes you may want to use another bitrate to match the rest of the system.

Note: Restart the ECU after changing the bitrate.