Patch: Force OBD Inspection Pass (acamus, mrfred)
Jul 19, 2009 | 07:59 AM
#19
Does this suppress the throwing of any OBD codes (besides those disabled through other patches)?
Will this be modified in the future so we can pick which readiness indicators say ready and which say not applicable? The reason I ask this second questions is this (...and I will have to do some research to verify as I am going off second hand info for now...): The state of Missouri's smog inspection (St. Lous and surrounding counties) testing is hooked up to a central database. It has been told to me that it keeps track of what your car's readiness indicators (which apply, which do not) and compares to the next inspection. If there are big changes (say last time EGR was not applicable and now it is ready) it throws up a flag.
Will this be modified in the future so we can pick which readiness indicators say ready and which say not applicable? The reason I ask this second questions is this (...and I will have to do some research to verify as I am going off second hand info for now...): The state of Missouri's smog inspection (St. Lous and surrounding counties) testing is hooked up to a central database. It has been told to me that it keeps track of what your car's readiness indicators (which apply, which do not) and compares to the next inspection. If there are big changes (say last time EGR was not applicable and now it is ready) it throws up a flag.
Jul 19, 2009 | 08:48 AM
#20
Actually, you just described exactly what this does: it gives you two tables you can edit, one which defines whether the test is available or not, and one which defines whether it's passed or failed. So, this does exactly what you want.
This doesn't suppress the throwing of codes, however: it only tells the emissions folks what they want to hear. If you're in a location where a CEL will fail you at emissions testing (and you have a visible or stored code), you'll need to rectify that problem as well.
This doesn't suppress the throwing of codes, however: it only tells the emissions folks what they want to hear. If you're in a location where a CEL will fail you at emissions testing (and you have a visible or stored code), you'll need to rectify that problem as well.
Jul 19, 2009 | 08:09 PM
#22
Actually, you just described exactly what this does: it gives you two tables you can edit, one which defines whether the test is available or not, and one which defines whether it's passed or failed. So, this does exactly what you want.
This doesn't suppress the throwing of codes, however: it only tells the emissions folks what they want to hear. If you're in a location where a CEL will fail you at emissions testing (and you have a visible or stored code), you'll need to rectify that problem as well.
This doesn't suppress the throwing of codes, however: it only tells the emissions folks what they want to hear. If you're in a location where a CEL will fail you at emissions testing (and you have a visible or stored code), you'll need to rectify that problem as well.
) some of the tests normally come up as not available, i.e. they do not apply to this particular model car. If the state of Missouri sees a difference in this configuration (I think...) they throw up a flag that there was a change and invalidate the smogging.
Jul 19, 2009 | 09:34 PM
#24
As I see it the first table makes ALL the OBD-II tests available whether they apply or not. If I'm not mistaken (and I may very well be...happens all the time ) some of the tests normally come up as not available, i.e. they do not apply to this particular model car. If the state of Missouri sees a difference in this configuration (I think...) they throw up a flag that there was a change and invalidate the smogging.
) some of the tests normally come up as not available, i.e. they do not apply to this particular model car. If the state of Missouri sees a difference in this configuration (I think...) they throw up a flag that there was a change and invalidate the smogging.
The "Monitor Available(1)/Not Available(0)" table is what lets you set whether they've available or not; set a particular test to "0", and it'll show up as "not available" to an OBD-II scanner.
Jul 20, 2009 | 04:21 PM
#26
I did not realize that you could go in to the table and edit individual line items (turn them on and off)...I thought this patch was an all or nothing affair and the table was just there to confirm visually that the patch had set the indicators to available and/or ready.
This is now the single coolest patch to come out of the ECUFlash forum! Though there are a few others hot on it's heels.
Thank You guys! Love this stuff!
