First steps and requirements

From MS4X Wiki
Revision as of 02:00, 9 November 2020 by Sorek (talk | contribs) (Tuning Software)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Welcome to the first steps of tuning your Siemens MS4X ECU. As you already know, the content of this website takes care about three different ECUs used in combination with the BMW M52TU and M54 engines.

This section shows all details you have be aware of, before you go on with flashing and tuning your engines heart. So the first thing is to determine what ECU is built into your car.

To do this, open the hood and follow the biggest cable loom coming from the engine into a sealed box of the engine compartment. For example, on an E46 this would be the upper right plastic box.

There is a sticker on the silver metal case of the ECU indicating the model. An M52TU engine always uses the MS42, the newer M54 comes with MS43 or MS45 depending on production date and area.

During the next steps and pages you will often read the term "software version". It's absolutely crucial to know the software version of your ECU because there are major differences between them.

Unfortunately there is no easy and safe way to determain the software version of the ECU from the outside. Not even looking up the part number printed on the label as it might have been updated at the dealership.

The following versions are the most known and most occuring at MS42, MS43 & MS45:

MS42 0110AD 0110C6 0110C7 0110CA
MS43 MS430037 MS430055 MS430056 MS430064 MS430066 MS430069
MS45.0 456L0B 456L3B 456M0B 456N0B 456O0B
MS45.1 457L0L 457L3L 457M0L 457N0L 457O0L 457G2L

MS42, MS43 and MS45 firmware is NOT compatible! You cannot use MS43 software on MS42 ECU or vice versa.

Each software version has minor or major improvements and changes in comparision to its predecessor making it incompatible with others because every change in the code also means that the maps in the tune need a new layout or position.

So keep in mind that a definition file (XDF/Damos/A2L) is written for a very specific software version!

If you load a flash file with MS430069 into TunerPro and use the definition file from MS430056, it´ll get really messy! If you are seeing strange values double check that you are using the correct version!


Example: Even loading a MS430055 tune in TunerPro with a definition file for MS430056 will result in a mess:

430055 binary with 430056 definition file

You can perfectly see the injection table is not located correctly by looking at the color scheme of the table and the sudden changing values iside the cells.


NEVER EVER FLASH A TUNE FROM A DIFFERENT SOFTWAREVERSION ON YOUR ECU OR IT WILL BE BRICKED OR RESULT IN FATAL ENGINE FAILURE!

Software & Tools

Before rushing into the tuning thing, make sure that all of your tools are working properly and you fully understand the following sentences.

The Siemens MS43 flashchip contains two different sections:

  1. 0x00000 - 0x6FFFF (448 KByte)
    • This is ECUs program space, special features (EWS or checksum deletes, Launch Control, etc.) are programmed here
  2. 0x70000 - 0x7FFFF (64 KByte)
    • This is the parameter space, where most of the functions in the ECU program lookup their corresponding values

Together these sections sum up for 512 KBytes total. So when you hear someone talking about the "512k file" or "full read", the whole flash content is meant.

Most of the regular tuning stuff can be done inside the parameter space, or often called "partial read".

So as long as you only want to raise your limiters, change injection or ignition tables, etc. you're fine with the smaller file. This reduces your flashing time as well.

Nevertheless, there are some special functions that require massive code rewritings in the program space, where a full write is nessessary.

Software collection with some goodies Google Drive

You can download the flashtools right here: Flash Tools

Tuning Software

The tuning software is not required, as you can make all the changes to the file with a HEX editor as well, but then you propably wouldn't need this wiki ;)

There are several tools, that'll make messing with the ECUs tables and values much easier and help a lot with a built in visualization engine.

Again, there are more than the two programs listed below, but people using WinOLS or even a HEX Editor don't need this guide.

These programs are relativly dumb, as they rely on so called "definition files". A definition file is unique for every software version, as stated in the beginning.

A definition file describes every value and table of the ECU (at least in the best case) with its HEX location in the flashfile, a conversion factor and its upper and lower limits.

In addition to that, there are logging definitions, that help you to log all the values for tuning or troubleshooting. Romraider has some nice wideband o2 sensor plugins!

  1. TunerPro
  2. RomRaider

Other datalogging software could be

Checksum correction

Modifying data in any of the two files will invalidate the internal checksum values. These will need to be updated or your car wont start.

You can solve this with ether correcting them before flashing the modified file, or flash the 512 KByte file from Daniel, where the calibration CRC16 checksum is disabled.

Be careful the calibration addition checksum is still enabled in that file, so editing _mon_ values is not possible without correcting or disabling this checksum first.

Check here how to disable the calibration checksums.

See HERE for the needed software to correct the checksums.