Useful resources for getting started

From B58 Wiki
Revision as of 14:52, 28 May 2024 by Jtownson (talk | contribs)

Background information

Modern engines for dummies

N54 and N55 Tuning

There are a lot of similarities but N54 tuning is simpler.

PID control

Dialling in boost control requires a familiarity with PID error control. If you are new to this, these introductions are highly recommended and enough to get you started.

Other B58 tuning resources

Tools for tuning

A2L file for your car

Having an A2L file that corresponds to your car is the resource for tuning because it describes every value, curve and map in the (stock) ECU. The A2L also describes all the units of these quantities and BMW's A2L are fairly well commented which helps with understanding.

As well as maps, the A2L describes every function and measurement in the ECU and the relationships they have to the maps. This provides a black-box view of what the ECU is doing and, although this does not describe the calculations taking place inside each function, for tuning purposes it is often enough to see the inputs and outputs.

It is worth remembering that, inside each function, the ECU only performs map lookups, simple arithmetic and logic operations. It is a real-time system, so even square roots are done by lookups. The results of complex modelling calculations (like airflow through a turbo) are always calculated offline and loaded into maps.

Usually, if we see a map is used by some function and, for example, it only has values defined upto a MAF of 1200kg/h and our new turbo flows 1800kg/h we know some sensible rescaling will be required and can move on without more detail.

This graph was generated using tools at https://github.com/jtownson/xdfbinext and shows the ECU considering pressure across the cat (for a gen 1 car). As you can see, the A2L provides an overview of all the maps and switches in context.

ASAP2 Demo

This is an awesome tool from https://jnachbaur.de/ASAP2Demo/ASAP2.html which lets you browse through A2L files and the calibration bins based on those.

A2Ls are loaded through the file-->open menu option and bins are loaded via the file-->load data file menu option.

Because it is based on the A2L, you can use it to glance quickly at any ECU object without having to import or convert (a common impediment with WinOLS and TunerPro). So, for example, if you see a map called KF_AUSY_TURB with an axis representing MAF, in the A2L, ASAP2Demo let's you see the map quickly and determine if you want to import it into tunerpro or other tool (more on this below).

One specific and important use for ASAP2Demo is to check the verion number of a bin file. This is held in a value called CustDiag_dDatasetVer_C:

Finally, ASAP2Demo supports all the characteristic types and axis types in the A2L standard, which makes it good for looking at non-numeric data.

QTranslate

QTranslate, from https://qtranslate-app.web.app/, is a very useful app that allows quick and easy translation of German text without having to switch to google translate.

Getting tunes off of your car

If you have a dialled-in tune on your car, it can be useful to read it off the ECU.

For gen 1 cars using Bosch MG1 with the SPC5777M chipset I have had success with ECU Bench tool. This is an inexpensive tool which works for reading ECUs without bricking them.

That said, a more effective workflow is to use the bench tool to read the DME but then write with the common flashing platforms like MHD since they support burbles, switchable fuel pumps, downpipes, etc. In order to do this, bear in mind that the bench reader reads a wider ROM segment off the chipset while the calibration space used for tunerpro bins are at an offset within this (e.g. 0x40001).

There are other more expensive professional options available, like autotuner and bitbox.

Tuning with MHD

Jobs involving antilag, flexfuel and map switching require editing of custom MHD tables which are not in any BMW A2L. MHD's approach here is to use tuner pro and they provide a well organized repo of tuner pro XDFs to support this. The XDF can be found at https://github.com/dmacpro91/BMW-XDFs.

The XDFs include table definitions for some but not all tables you might want to modify and they only include a small subset of tables you might want to inspect when trying to understand DME objects in context. For that reason, a good workflow with MHD is to

  1. Use the A2L and ASAP2Demo (or WinOLS if you have a licence) to browse and understand DME settings in the large.
  2. Import objects into XDF if needed and complete edits there.
  3. Flash with MHD Flasher.


TunerPro itself is available from https://www.tunerpro.net/. Generally, you want the TunerPro RT version. Consider registering the software at https://www.tunerpro.net/registration.htm, especially if you use the software to develop a working tune for your car.

Retrieved from ‘https://b58.wiki:443/w/index.php?title=Useful_resources_for_getting_started&oldid=344’