2006+ readiness not setting flashpro
Thread Starter
Joined: Mar 2011
Posts: 175
Likes: 1
From: Rochester, NY
FWIW, it does seem like a new "bug" was introduced recently that is preventing the readiness checks from completing. I have been passing annual inspections for years while having the secondary O2 disabled (and removed), since Texas will allow 1 incomplete readiness check. However, I recently updated my FlashPro to the latest version, with hopes that it would fix an issue with idle speed, and now see that I have 3 readiness checks that won't complete.
Of course, I have to point out that I'm running ITB's, which would definitely contribute to the EVAP readiness problem. However, even with ITB's, prior to updating FlashPro Manager the readiness checks would quickly drop down to 2 incomplete tests in just a couple short driving cycles.
Of course, I have to point out that I'm running ITB's, which would definitely contribute to the EVAP readiness problem. However, even with ITB's, prior to updating FlashPro Manager the readiness checks would quickly drop down to 2 incomplete tests in just a couple short driving cycles.
Hopefully hondata can pin point what changed and fix it. I am going thru the same thing as you 3 not set. My evap will probably not set but I can have 1 not ready. No reason for primary and secondary to all the sudden not set.
Joined: Oct 2012
Posts: 1,115
Likes: 7
At one point I had 3 not ready also, I got emissions and it showed 2 not readiness, and then so I removed the negative terminal on the battery and it showed 3 not ready, so then I flashed the ECU with the Tuned rom, and then took it for a spin, after coming back it showed 2 not readiness and after the 4 drive cycles and 108 miles later I finally got the EVAP to set.
Joined: Apr 2012
Posts: 1,016
Likes: 6
I'm not sure of the date, but it was around the middle of Feb and I was on the current Flashpro release when I put my car back to stock, flashed it back to stock, drove it around, and passed emissions. I can dig through and find a date so we can get a better idea on what release this regressed, if it is a bug in the Flashpro software to begin with.
Joined: Mar 2010
Posts: 4,742
Likes: 211
I guess if I was having trouble setting readiness codes first thing I'd do is ask hondata for the previous version of firmware for the flashpro and software version for flashpro manager and rollback to previous versions. They should be able to provide it, and that way hopefully can get over the hump of passing emissions and figuring out the issue later.
Thread Starter
Joined: Mar 2011
Posts: 175
Likes: 1
From: Rochester, NY
I was going to but read this from a previous readiness issue threas.
"If there are any issues with a beta, we fix them and make a new release. The current beta will be released as production within the next week or so. You should never 'downgrade' software versions."
"If there are any issues with a beta, we fix them and make a new release. The current beta will be released as production within the next week or so. You should never 'downgrade' software versions."
Joined: Mar 2010
Posts: 4,742
Likes: 211
That sounds like lawyer speak crxdx. Bugs inevitably make their way into production/"stable" releases. I have a hard time believing we can't reflash our flashpros w/ an older version.. Perhaps there's a sequence to follow and it's less idiotproof but I'm sure there's a way..
Thread Starter
Joined: Mar 2011
Posts: 175
Likes: 1
From: Rochester, NY
I have almost 1k miles logged now going to try and unlock flash bringing my ecu to stock code and reinstalling newest beta and putting my tuned calibration in. Doubt it will do anything but I gotta try for sanity reasons.
Former Sponsor
Joined: Mar 2002
Posts: 15,526
Likes: 19
FlashPro Manager will not downgrade the firmware on the FlashPro itself, so once it's upgraded, there's no way to go back. You can run older versions of FlashPro Manager, but you won't be able to load any calibrations to the updated FlashPro.
Joined: Mar 2010
Posts: 4,742
Likes: 211
