Skip to content
Shop
Explore

INDEPENDENT BMW ENGINE EXPERTISE

MSD80. Advanced ‘features’

N43 / N53 · NOXEM · DIAGNOSTICS

[[[KEEP1]]](https://bimmerprofs.com/wp-content/uploads/2017/08/msd80.jpg)

The MSD80 is a very complicated engine management system. The days when an engine management system ran simple, easy-to-follow algorithms are gone for good. Today’s engine control units are specialized, high-performance computers that handle dozens of tasks at the same time. Their software is written by humans, who make mistakes. Even if the programmer writes perfect code, the processor or microcontroller manufacturer can have faults, meaning the processor executes a given task incorrectly. Faults also creep in during algorithm development and unit performance testing. Sensor and actuator manufacturers make mistakes too: sensors send incorrect data, and actuators execute commands incorrectly. Below is a summary of the top 10 most common MSD80 bugs.

Misleading reports and hardware weak points (places 10 to 8)

Place 10. Misleading self-diagnostics reports. This problem also runs through several of the entries below, but this place covers the more general cases. For example, incorrect individual cylinder adaptations can produce error messages about the Lambda probes and/or CO catalytic converters. A specific defect of the NOx sensor can produce an error message about a faulty temperature sensor in the exhaust system. You can replace that temperature sensor and its wiring a hundred times and the result will not change: the error message about the sensor (implausible temperature) will remain.

Place 9. Ignition coil control. This is a hardware problem, but because it is directly tied to the MSD80, it belongs on the list. The defect is improper control of the ignition coils. This puts the IGBT transistors that drive the coils, which work under severe temperature and voltage conditions, at high risk of damage. The same inaccurate switching also frequently destroys the coils themselves, because the coil insulation breaks down. I have found no information that this problem was solved in newer MSD80 releases, and it is one of the top N43/N53 problems. Replacing a defective IGBT does not remove the cause, so the problem can return after some time. The problem is described here and here.

Place 8. Rough road and “Rough run / Stratified charge” messages. An uneven road surface can trigger error messages about rough run or stratified charge. The ranking here is controversial. On one hand, this message, together with ISTA notes about misfires in specific cylinders and its suggestion to replace spark plugs, ignition coils and injectors, is one of the main causes of expensive, unfounded repairs that bring no visible improvement. On the other hand, once you know the causes and effects of this message, the situation is only amusing. The message has no significant impact in either passive or active mode. You can read more here. In fairness, several later software updates eliminated this problem.

Adaptation and logic errors (places 7 to 4)

Place 7. Incorrect, even misleading adaptation algorithm. For example, the injector opening times for bank X are strongly corrected with a “+” sign (lengthened), while the temperature corrections for that bank carry a “-” sign. The total corrections come out small, which looks close to ideal, yet the menu “picture” shows the engine running very incorrectly. Software updates have mostly eliminated this situation.

Place 6. No thermostat self-diagnosis. Like the M57/N57 diesels, the N43/N53 and other petrol engines do not self-diagnose the thermostat for low engine temperature. If the mechanical part sticks in the open position, which is a very common defect, the engine cannot reach its nominal temperature. The water pump also runs at its lowest possible setting. The consequences are:

  • overheated or damaged CO catalytic converters, because they are heated harder to reach the “necessary” working temperature;
  • disturbed desulfation sessions of the NOx catalytic converter;
  • increased fuel consumption.

Place 5. Gross logic errors in the individual cylinder fuel corrections. The two best-known examples are:

  • Suppose cylinder X misfires from time to time. When running its efficiency tests, the MSD80 simply sums the efficiency (Y) of all cylinders (X). Because of the misfire, the average efficiency is below normal, so the mixture is enriched in the misfiring cylinder while the other cylinders only get a lean mixture. The problem only grows. The solution would be to ignore measurements that differ strongly from the average, but even the latest MSD80 releases do not include this.
  • Suppose that external circumstances unbalance the cylinders (for example the AC, angular play in the dual-mass flywheel, or some misfire), and the MSD80 reduces the fuel quantity in a cylinder to rebalance efficiency. Once the engine returns to normal operation, it is obvious that a cylinder given less fuel will show below-average efficiency. The normal reaction would be to increase the fuel quantity, at least to the average. Instead, the MSD80 records an error message about inadequately low cylinder efficiency and stops creating individual fuel corrections. It is a very simple but gross logic error.

Place 4. Mathematical errors during adaptation in specific cases. If the NOx system (NOx sensor and/or NOx catalytic converter) has problems, and related error messages are stored in the fault memory, the MSD80 performs completely wrong mixture adaptations. The following messages usually appear:

  • 29D1: misfires, cylinder 5
  • 29F5: CO catalytic converter efficiency below threshold, bank 2

Fuel trim error messages, especially for bank 2, usually appear as well. When the NOx system is damaged, none of these messages has a real cause. They are usually the result of incorrect MSD80 operation.

Late adaptation failures and rare glitches (places 3 to 1)

Place 3. Adaptation failure after a series of specific error messages (for example for the NOx catalytic converter and/or sensor). Suppose the cause of those messages has been eliminated, the MSD80 fault memory has been cleared, no new errors appear, and all indicators (learn bits, integrators, individual adaptation registers) initially show correct operation. Even so, adaptations are gradually created incorrectly. After some tens of engine hours the engine starts to lose power, vibrate and shake, with misfires, and error messages about the Lambda probes and/or CO catalytic converter appear. The dealer diagnostic system ISTA D will not show the cause and falsely suggests replacing injectors, CO catalytic converters and Lambda probes. Only INPA loader 2.023, together with observation of the specific symptoms, makes it possible to recognize this situation. Unfortunately, in 99% of cases it is not recognized, and owners spend large sums replacing injectors and ignition coils. You can read more here.

Place 2. Sudden false group misfire detection. Under changing conditions (varying throttle opening and engine load), the MSD80 suddenly and without justification detects a group misfire in some cylinder. Under such conditions the flywheel uneven-run control has to be switched off. The MSD80 disconnects the “damaged” injector, goes into open-loop mode, continues to run on 5 or 3 cylinders (N53/N43) and turns on the EML lamp. The engine runs with reduced power and vibrates very strongly. This defect is very rare: it was confirmed once in 100,000 km, though it may have been the cause of several later problems. The good news is that if you let the engine idle for several minutes, it successfully restores the deleted bank and offset adaptations and starts creating new, correct ones. Again, there is no hint for the driver, for example in the CCC monitor. A non-technical driver will not keep driving, because while the adaptations are being restored the engine vibrates very strongly, idle RPM fluctuates, and so on.

Place 1. Hot restarts. I mean an arbitrary restart of the MSD80 without loss of power supply. It is rare: on the car in question I observed it once or twice in 100,000 km. The effect is impressive, though. The engine simply cuts out for half a second, and even the tachometer reading disappears, while the engine keeps turning on inertia. The good news is that the restart is quick and the MSD80 recovers without error messages or other symptoms. Causes are very unclear. The problem may come from a fault in the program code, such as a stack overflow, addressing of non-existent memory cells, RAM/EEPROM mismatches, or calculation errors such as division by zero with incorrect handling. Because it is so rare, it is unknown which software versions are affected, or how many. The EML lamp does not light, and the MSD80 fault memory contains no error messages. Extreme feelings are guaranteed. The corresponding entry is stored in the info memory and is not visible via ISTA D.

[[[KEEP2]]](https://bimmerprofs.com/wp-content/uploads/2017/08/MSD80_reset2.png)

Related entries

BEYOND THE FAULT CODE

A clearer picture.
A better next step.

Get in touch
Enlarged technical image
Open original image