Select a technical image to view it in detail.
Since BMW moved to turbocharged petrol engines, “chip tuners” have taken a strong interest in them. There are two ways to raise performance. One is to change the software in the DME. The other is to install an external “black box” that leaves the DME untouched. The second option is very tempting because it is simpler and does not put the warranty at risk: when you have to visit the dealer, you simply disconnect the unit and nothing shows that anything was ever fitted.
The principles described below also apply to other BMW turbo engines (N20, B38, B46/48, N55 and so on), with differences specific to each engine.
The most popular product among these power boxes is the JB4. The unit costs around EUR 500 to 800, depending on taxes paid and on installation.

What the JB4 does
The JB4 deceives the DME by reporting a lower intake air pressure and air mass than the car’s sensors actually measure. The DME then raises boost pressure and airflow until it reaches the values it expects, but the real airflow is considerably higher. More air means more power. That is the idea, at least. But how does it work in practice?
How the JB4 is connected
The JB4 is wired into the MAP sensor (intake manifold pressure) and the MAF sensor (air mass flow). The plugs of both sensors are routed through the JB4, which modifies their signals (in the positive boost pressure range) and passes the altered readings on to the DME.
It is also connected to the diagnostic socket. From there it takes its 12 V supply and communicates over the CAN bus. CAN communication allows the modes to be switched on the fly. The modes range from “stock”, through several increased-power maps, to a “custom” option.
Problems with the JB4
The occupied diagnostic socket
While the JB4 is connected, the OBD socket is occupied, so it is not possible to connect and read EDIABAS data. Newer JB4 releases do have their own OBD socket (or a Bluetooth connection, as you prefer), but the data available through it is very limited. It is plain OBD data, far narrower than EDIABAS. This matters for two reasons:
- If the engine starts to have problems, INPA/ISTA cannot be connected. Even OBD Mode 6, which would show misfires, is unavailable.
- Analysing EDIABAS data is essential for judging engine behaviour. It is needed to confirm that everything is fine with any of the increased-power maps, let alone a custom map.
Management maps working outside their intended range
If the intake manifold parameters are falsified this way, all the other management maps (fuel, ignition and so on) operate in a range that does not match the real situation. The difference looks small, 10 to 15%. If maps with +50 hp are used, I recommend not even trying the “more powerful” versions. The consequences can still be serious.
The JB4 and similar products rely on the other management maps “adapting” through the adaptation maps. For a perfectly healthy engine, with all components at or near zero deviation, a 10 to 15% difference should cause no trouble. The problem lies elsewhere. Depending on the particular engine, some adaptation maps may already sit close to the limits of their allowed range with stock management. Shifting these maps by 10 to 15% can push some of them to the limit, and that does happen. The result is:
- error messages in the DME fault memory;
- reduced power (limp mode, in any of its forms);
- often the EML (Check Engine) light on the instrument cluster.
The B58 and its twin-scroll turbo
The situation is particularly dangerous with the B58 and its twin-scroll turbocharger. This turbo loads the cylinder groups 1–3 and 4–6 differently. With these power boxes, nobody knows how large the difference in mixture between the two groups will become at high torque, which is exactly where the intake manifold data is faked. The DME will adapt and try to hold the average mixture, because the B58 has only one lambda probe shared by all cylinders. One group can therefore run lean and the other rich, and nobody will know, including the DME itself.
Switching maps without readapting the engine
The third problem is the main one. The JB4 encourages switching maps on the fly, yet it says nothing about readapting the engine: what that is, when it should be done and why. Both points are crucial. Switching maps without readaptation is the fastest way to damage the engine.
The DME builds multidimensional adaptation maps over a long period for each component: the throttle, wastegate control, fuel pressure sensor, each injector and so on. These maps cover temperature, fuel quality and many other dimensions. If the JB4 switches maps without warning, the consequences are severe. Take the transition from stock to JB4. The user increases power, having previously driven on stock maps. What happens?
- The JB4 deceives the DME by reporting reduced intake air pressure and airflow.
- The DME raises boost pressure (and airflow) to match its target. The actual amount of air is now much larger than the DME believes.
- The extra air makes the mixture lean. The DME sees this and uses STFT (short-term fuel trim) to correct it urgently.
STFT does not act instantly, so for the first few seconds the mixture is lean, which is dangerous for the engine. If the engine were allowed to adapt properly to the new conditions, the situation might be more or less acceptable. By switching boost maps this way, the user completely defeats that adaptation principle. If the STFT of the engine reaches its maximum (+30%), the mixture stays lean until the DME concludes that something is badly wrong. Then it reduces boost pressure or switches the turbo mode. During the seconds the DME needs to react, a lean mixture can do all the damage it can to your engine.
Open-loop operation
There is a second aspect. When operating modes change quickly, the DME works in open loop: the lambda probe readings are ignored and it runs only on maps (management maps plus adaptation maps). It returns to closed loop 2 to 3 seconds after stable driving conditions (steady torque demand and RPM) are reached. The JB4 then has two options:
- Not to modify the boost data in these modes, to avoid upsetting the DME (error messages or limp mode).
- To fake the data from the first second, without regard for the consequences.
In the first case, during a hard acceleration (0 to 100 km/h), there is no gain in 1st and 2nd gear. In the second case, the “upgrade” is already out of control.
The safety reserve and the claimed power gains
The 10 to 15% margin is something BMW built in for poor-quality fuel, for mountain regions (where the oxygen content of the air is lower) and for manufacturing tolerances. There is a 50/50 chance that your turbocharger cannot deliver what the most powerful JB4 maps ask of it. Then an EML light, loss of power and desperate questions on internet forums (“my car lost power after installing JB4, what to do?”) are guaranteed.
The +80 to 100 hp claimed by the JB4 manufacturer is not realistically achievable. By “realistic” I mean without error messages in various driving modes and at least partly safe for the engine.
Newer releases running the maximum-power programs do connect to the electric wastegate. Evidently they check whether the DME keeps it fully closed for a long time, which means the turbo “can’t handle” the demand. In that case they reduce the amount of falsified pressure so that the DME does not “fall out” with boost pressure errors. This partly solves the boost error problem, but everything described above remains. I will not even start on the ignition maps and knock sensor data when maps are switched. Everything is bad there.
Conclusion
The JB4 developers never mention readaptation of the engine, yet recommend switching maps “whenever you want”. This suggests, unfortunately, that they have only a minimal understanding of how a modern DME works. BMW builds sturdy engines, but I will not tempt fate by connecting a JB4.