Issue with excessive, sudden richening. No acc. enrichment active

Hello everyone,

I am currently in the process of tuning my engine on the dyno. Recently, I’ve encountered an intermittent issue (about 3-4 times) where the engine suddenly becomes extremely rich, and I’m not sure what’s causing it.

BMW_e36_ohne_AccEnrich_bis_4500rpm_50%_20251230.emub (146.1 KB)

4500_wieder_Anfettung_20251230_1246.emublog (233.7 KB)

Could someone take a look at the log file and the emub file? Maybe it’s a kind of protection or something seems to get active, but i didn’t find anything.
It’s possible that the VE table doesn’t align perfectly with the measurement, as I’ve continued working on it. However, the VE table is still not finalized, but I’m sure the map is not the source of the problem. Please note that this is still an initial setup phase.

I’d appreciate any insights or suggestions!

Best regards,
Matt

Have same issue during cranking I believe the trigger signal will be lost then it won’t fire the spark plugs thats in my case, datalog and triggers scope is ok but when I check it with an timing light it’s not flashing that means no signal coming from ecu but in test output timing lights work fine and flash.

Thanks for your reply,
but i don’t think that’s the reason in my case.
Two things: if you have no ignition (misfire) you will see a lean lambda, not a rich one. Additionally the injector pw rises, so it seems there’s an actuation from some functionality.

The issue is definitely caused by VE. It increases from around 50% to around 80% and there for it gets rich. Ur VE map looks okay and the actual VE value is higher than the one from ur VE map. There must somewhere be a correction for VE which gets active but i can’t find.
Are u sure the tune fits to the log?

You’re correct I checked your map vs datalog and the only thing is ve is getting higher than fuel table map.

Plus your Iat is high and ect as well you should have an correction timing for those then your knock table not actually active if it’s done right it read knock you have spike all the places in knock data.

That’s my thought as well.

As i said, i’m quite sure that it’s not from VE table, it was always quite smooth. Unfortunately i went on with calibration and did not safe the file separately. If i get this issue the next time i’ll do that.

yes the ignition timing is quite late and knock is also not calibrated yet.
Just testing around with it at the moment.

Can u reproduce it or did it just happen a single time?

it is not reproduceable..
Tomorrow i’ll go on, let’s see what happens.