So today it happened again. For what I see lean and rich stay at 0
Readiness - Catalyst
- Thread starter carabuser
- Start date
Really nice that the fix is now part of the app ! Thanks 
To @Jake@MHD or anyone else who knows ( very probably @carabuser )
Does the AFR oscillation fix now apply by default (OEM DP not selected) when flashing a custom map too ? or just with MHD OTS maps ?
To @Jake@MHD or anyone else who knows ( very probably @carabuser )
Does the AFR oscillation fix now apply by default (OEM DP not selected) when flashing a custom map too ? or just with MHD OTS maps ?
Really nice that the fix is now part of the app ! Thanks
To @Jake@MHD or anyone else who knows ( very probably @carabuser )
Does the AFR oscillation fix now apply by default (OEM DP not selected) when flashing a custom map too ? or just with MHD OTS maps ?
It is a flash option checkbox that appears after you select aftermarket DP. You must also select the checkbox for osc. fix if you want it applied. This was split off as a separate checkbox so that those who need the o2 monitors to set can unselect it and have those routines run properly (which is prevented when oscillation is disabled).
I am still seeking advice regarding oscillation fix feature.
Does it essentially disable the secondary O2 sensors and are there any downsides to that?
Asking as the common belief has been that rear O2 input is required to calibrate the primary sensors afrs...
No. I've been running this for a year and the only side effect is that it prevents the O2 sensor readiness monitor.
Ok so you mean rear O2s are still active and NO downsides.
I mean we may not even notice if primary O2 slightly go out of calibration anyway so hard to say what's actually happening
One thing I noticed with oscillation fix is that afrs go super Smooth and straight even more than my old logs with stg1 and catalyst still on the car and oem cat box ticked.
Unless it's got something to do with brand new o2 sensors I installed since then...
Attachments
First screenshot looks like there's still interference from the diagnostic routines.
The changes that I made to fix the oscillation only disable the diagnostic routines that cause the forced lambda stimulation. The routines that diagnose catalyst efficiency do this by creating oscillations in lambda reading and monitoring the response of the upstream and downstream O2 sensors. The routine looks at the increase in free oxygen and a lag in the response caused by the restriction of the cats to determine if they are operating properly. When you remove the cats you just end up with the routine failing and restarting endlessly.
There probably is but I haven't looked into it. I made a flash that just forces all readiness states to pass and bypasses the CVN checks for that purpose. Readiness monitors don't really matter outside of inspection, they are just a reflection of the states of certain diagnostic routines that are deemed emissions relevant.
I honestly haven't looked at any other engines regarding emissions equipment removal. I'm pretty sure there's massive scope for improvement on the N55 and B58 platforms as looking at the state of the public XDF and the caliber of the tunes available it seems that nobody has put much effort into those platforms yet.
The N55 platform is neglected because it's inferior and the B58 is still in the early days. As platforms mature they tend to accrue more tinkerers that are more invested in their vehicle whereas new platforms tend to mainly be lease cars and piggybacks for people just want a little extra poke until they return the car to the finance company.
Does anybody have a solution to set readiness to ready for MSD80/81?
There seem to be a work around in some test mode but I haven't found the correct switch location in the calibration file yet.
There seem to be a work around in some test mode but I haven't found the correct switch location in the calibration file yet.
Why play around with the data space when you can go in the program space and just turn the byte that displays ready or not? I won't go further in testing since I'm not losing my home and everything I own because someone waited to save a couple hundred bucks to throw a cat back on the car....
Depending on the mods it's pretty easy to pass readiness with cal changes if you just have cats removed, I have both my vehicles tuned so they pass all diagnostics now without the need for code disabling. It's only cars that have the O2 sensors removed or repurposed that require a mod to the program section.
Flashing a binary with a modified program sector is pretty tricky. MHD only allows calibration changes and Bimmerlabs isn't set up for it, you need to create a custom 0pa that contains the program changes and correct the program checksum then flash it after an RSA bypass which is a bit painful.
I've been making a Windows program in my spare time that can flash the complete DME including changes to the program sector. It will correct all checksums and automatically apply the RSA bypass. I need to test it more robustly but hopefully it could be useful if there is people out there wanting to play with custom logic.
If you have MHD+ and make a change the car will not start just a FYI even cloning and just the bootpin being different will cause a miscalculation in the encryption. Best to do it stock.
So make it stock, apply readiness patch and then install MHD to keep the patch?
I haven't analyzed the logic behind the patch as I am not at that level yet. So a bit clueless here. I suspect the variables are directly set in RAM rather than being calculated.
No because MHD is custom program space it's not just calibration data. You would have to modify the stock and leave MHD off.
Similar threads
