Patch: Force OBD Inspection Pass (acamus, mrfred)
They do keep a record of whats going on, and when you go to the inspection station, it may look fine to the person there but when it goes to pass and print your sticker BAM you get a rejection and you also get locked out and have to go to a Motorist assistance center to get your car inspected. Some even run into tech's hooking up laptops and monitoring fuel trims (Odd since this is quite a few % off right from factory) and then visually checking all your emissions stuff.
Mine was flagged for a Euro Rom two years back, it was flagged last year in the system as a USDM Rom but with everything saying Passed. the guy said that is obviously not possible, and then this year it was flagged for "modified bits in the ecu" i.e force passed changes to things like EGR.
just dont have the pass/avalible option selected for stuff that isnt on our cars and youll be fine.
mine is set At
1
1
1
0
0
1
0
1
i used to throw codes before, since applying the patch i have not had one single code thrown... idk how that happend :0
mine is set At
1
1
1
0
0
1
0
1
i used to throw codes before, since applying the patch i have not had one single code thrown... idk how that happend :0
That is inaccurate. ^ Stuff that is not forced passed on our cars still can be detected as modifications to the bits. It is logged and stored. So just keep that in mind if your states start enforcing this as well.
What do you mean? Force/pass to all? and Avalible Ready to stuff thats not on my car? or Force/pass to all Avalible Ready to whats on the car?
Here they run a program like PCMscan, if it checks out then your GTG. Obviously if some stuff comes up as Ready Avalible and its not on the car they gunna question why is it ready when it souldnt be.
What do you mean? Force/pass to all? and Avalible Ready to stuff thats not on my car? or Force/pass to all Avalible Ready to whats on the car?
Here they run a program like PCMscan, if it checks out then your GTG. Obviously if some stuff comes up as Ready Avalible and its not on the car they gunna question why is it ready when it souldnt be.
Here they run a program like PCMscan, if it checks out then your GTG. Obviously if some stuff comes up as Ready Avalible and its not on the car they gunna question why is it ready when it souldnt be.
This stuff is all logged, so if your just doing it to do it keep in mind it may still be in the emissions database. MA checked this stuff but people who force passed still got their sticker. As of about 6 months ago now they are force running the tests, and they are also comparing the results back from prior station visits. So YES you may be fine now, but keep in mind you may get flagged if they implement stuff like this in your states.
I was thinking about this the other day, too, and was thinking about ways to know that a car is patched.
There is only one inherent flaw in the process, as we do it today, that can be fixed, too (#3 below). All others have solutions.
1. Issue: A different ROM number
Solution: We can edit the ROM identifier to match whatever ROM number you want. You just have to make sure your XMLs, etc, all match so that you can edit the ROM appropriately. So, for example, you can actually be running say 96530006 and have it say 96940011.
2. Issue: Having tests that say available and pass for systems not on your car
Solution: Scan you car before the patch with an OBD app, and see what tests are available. Only set those as available and ready in the patch.
3. Issue: Any cars with the patch will immediately show all tests ready after a battery disconnect/reconnect
Solution: None, for current patch. The patch simply sets these tests to ready immediately. Normally, the OBD routines take some time to run. So, all a test station needs to do is disconnect your battery, reconnect, and scan the readiness tests. If they say pass, then they know something is up.
Potential solution: I haven't looked into the details of the patch exactly, but you would need something where the patch is stored in RAM and read only from RAM (like a DMA ROM), and upon battery reset, the original values would be read from ROM.
For #3, for now, I was actually thinking about taking the patch off. I actually don't need it, as my car passes everything fine. I just like messing around with things.
There is only one inherent flaw in the process, as we do it today, that can be fixed, too (#3 below). All others have solutions.
1. Issue: A different ROM number
Solution: We can edit the ROM identifier to match whatever ROM number you want. You just have to make sure your XMLs, etc, all match so that you can edit the ROM appropriately. So, for example, you can actually be running say 96530006 and have it say 96940011.
2. Issue: Having tests that say available and pass for systems not on your car
Solution: Scan you car before the patch with an OBD app, and see what tests are available. Only set those as available and ready in the patch.
3. Issue: Any cars with the patch will immediately show all tests ready after a battery disconnect/reconnect
Solution: None, for current patch. The patch simply sets these tests to ready immediately. Normally, the OBD routines take some time to run. So, all a test station needs to do is disconnect your battery, reconnect, and scan the readiness tests. If they say pass, then they know something is up.
Potential solution: I haven't looked into the details of the patch exactly, but you would need something where the patch is stored in RAM and read only from RAM (like a DMA ROM), and upon battery reset, the original values would be read from ROM.
For #3, for now, I was actually thinking about taking the patch off. I actually don't need it, as my car passes everything fine. I just like messing around with things.
I was thinking about this the other day, too, and was thinking about ways to know that a car is patched.
There is only one inherent flaw in the process, as we do it today, that can be fixed, too (#3 below). All others have solutions.
1. Issue: A different ROM number
Solution: We can edit the ROM identifier to match whatever ROM number you want. You just have to make sure your XMLs, etc, all match so that you can edit the ROM appropriately. So, for example, you can actually be running say 96530006 and have it say 96940011.
2. Issue: Having tests that say available and pass for systems not on your car
Solution: Scan you car before the patch with an OBD app, and see what tests are available. Only set those as available and ready in the patch.
3. Issue: Any cars with the patch will immediately show all tests ready after a battery disconnect/reconnect
Solution: None, for current patch. The patch simply sets these tests to ready immediately. Normally, the OBD routines take some time to run. So, all a test station needs to do is disconnect your battery, reconnect, and scan the readiness tests. If they say pass, then they know something is up.
Potential solution: I haven't looked into the details of the patch exactly, but you would need something where the patch is stored in RAM and read only from RAM (like a DMA ROM), and upon battery reset, the original values would be read from ROM.
For #3, for now, I was actually thinking about taking the patch off. I actually don't need it, as my car passes everything fine. I just like messing around with things.
There is only one inherent flaw in the process, as we do it today, that can be fixed, too (#3 below). All others have solutions.
1. Issue: A different ROM number
Solution: We can edit the ROM identifier to match whatever ROM number you want. You just have to make sure your XMLs, etc, all match so that you can edit the ROM appropriately. So, for example, you can actually be running say 96530006 and have it say 96940011.
2. Issue: Having tests that say available and pass for systems not on your car
Solution: Scan you car before the patch with an OBD app, and see what tests are available. Only set those as available and ready in the patch.
3. Issue: Any cars with the patch will immediately show all tests ready after a battery disconnect/reconnect
Solution: None, for current patch. The patch simply sets these tests to ready immediately. Normally, the OBD routines take some time to run. So, all a test station needs to do is disconnect your battery, reconnect, and scan the readiness tests. If they say pass, then they know something is up.
Potential solution: I haven't looked into the details of the patch exactly, but you would need something where the patch is stored in RAM and read only from RAM (like a DMA ROM), and upon battery reset, the original values would be read from ROM.
For #3, for now, I was actually thinking about taking the patch off. I actually don't need it, as my car passes everything fine. I just like messing around with things.
Newbie
Joined: May 2011
Posts: 93
Likes: 0
From: Sonoma County
Will this work in California? Looking to buy a Evo but the damm smog laws in California suck, I'm not worried about visual, I'm worried about the OBD inspection! Car I'm looking at as a FF turbo setup and not sure what codes the ECU will throw, I come from Subarus and know TGV's and that throw codes, are Evos the same?
It will will fine in California, with the caveat I mentioned above.
By the way, California is going to be full OBD II emissions testing starting next year...no more tailpipe emissions. So, as long as your tests are ready and passed, you are good.
By the way, California is going to be full OBD II emissions testing starting next year...no more tailpipe emissions. So, as long as your tests are ready and passed, you are good.
Newbie
Joined: May 2011
Posts: 93
Likes: 0
From: Sonoma County
Thanks, when I go to check this Evo out what should I look for on the ECU? How many monitors are suppost to be working? Does a Forward Facing turbo kit with speed density screw with the ECU and throw a code they migh see? I come from Subarus and don't know much about Evos ECU. Thanks for helping, anything you could point out that I should keep eye out for would be much appreciated.
I was thinking about this the other day, too, and was thinking about ways to know that a car is patched.
There is only one inherent flaw in the process, as we do it today, that can be fixed, too (#3 below). All others have solutions.
1. Issue: A different ROM number
Solution: We can edit the ROM identifier to match whatever ROM number you want. You just have to make sure your XMLs, etc, all match so that you can edit the ROM appropriately. So, for example, you can actually be running say 96530006 and have it say 96940011.
2. Issue: Having tests that say available and pass for systems not on your car
Solution: Scan you car before the patch with an OBD app, and see what tests are available. Only set those as available and ready in the patch.
3. Issue: Any cars with the patch will immediately show all tests ready after a battery disconnect/reconnect
Solution: None, for current patch. The patch simply sets these tests to ready immediately. Normally, the OBD routines take some time to run. So, all a test station needs to do is disconnect your battery, reconnect, and scan the readiness tests. If they say pass, then they know something is up.
Potential solution: I haven't looked into the details of the patch exactly, but you would need something where the patch is stored in RAM and read only from RAM (like a DMA ROM), and upon battery reset, the original values would be read from ROM.
For #3, for now, I was actually thinking about taking the patch off. I actually don't need it, as my car passes everything fine. I just like messing around with things.
There is only one inherent flaw in the process, as we do it today, that can be fixed, too (#3 below). All others have solutions.
1. Issue: A different ROM number
Solution: We can edit the ROM identifier to match whatever ROM number you want. You just have to make sure your XMLs, etc, all match so that you can edit the ROM appropriately. So, for example, you can actually be running say 96530006 and have it say 96940011.
2. Issue: Having tests that say available and pass for systems not on your car
Solution: Scan you car before the patch with an OBD app, and see what tests are available. Only set those as available and ready in the patch.
3. Issue: Any cars with the patch will immediately show all tests ready after a battery disconnect/reconnect
Solution: None, for current patch. The patch simply sets these tests to ready immediately. Normally, the OBD routines take some time to run. So, all a test station needs to do is disconnect your battery, reconnect, and scan the readiness tests. If they say pass, then they know something is up.
Potential solution: I haven't looked into the details of the patch exactly, but you would need something where the patch is stored in RAM and read only from RAM (like a DMA ROM), and upon battery reset, the original values would be read from ROM.
For #3, for now, I was actually thinking about taking the patch off. I actually don't need it, as my car passes everything fine. I just like messing around with things.
Looks like the rallyevo site that the vid was hosted on no longer exists. I was able to find a copy of the video here: http://evoecu.logic.net/mirror/vids/ It is the ecuflash_06 vid.
Newbie
Joined: Aug 2012
Posts: 1
Likes: 0
From: Phoenix, AZ
Hi Guy's I need a little help.
My son's car 2003 Lancer ES all stock fails the OBDII emotions check in AZ because the cat is going bad and the EGR reports slow flow. What do I need to apply the patch ( hard ware ) do I just need this Tactrix Openport 2.0, or is this http://www.tactrix.com/index.php?pag...mart&Itemid=53 required as well ?
EDIT: what I have done to the car, Replaced the Vacuum switching valve, tested and cleaned the EGR valve, checked all of the vacume hoses, replaces both o2's.
I need to get this car to bass as he comes back from Iraq in a week.
Thanks for all your help.
My son's car 2003 Lancer ES all stock fails the OBDII emotions check in AZ because the cat is going bad and the EGR reports slow flow. What do I need to apply the patch ( hard ware ) do I just need this Tactrix Openport 2.0, or is this http://www.tactrix.com/index.php?pag...mart&Itemid=53 required as well ?
EDIT: what I have done to the car, Replaced the Vacuum switching valve, tested and cleaned the EGR valve, checked all of the vacume hoses, replaces both o2's.
I need to get this car to bass as he comes back from Iraq in a week.
Thanks for all your help.
Last edited by area1509; Aug 18, 2012 at 11:42 AM. Reason: Add Info