Went to get my car inspected and when the OBDII computer was plugged in, the tech got a bunch of sensor not ready codes. I'm not exactly sure why. It has been a while since I last reflashed and and reset the ECU (disconnected neg. battery cable). I did change the oil last week, but the car has been driven several hundred miles since. Just before x-mas, I pulled a couple of logs and read the current map using Ecuflash. The car was parked for 4 or 5 days and then driven to get inspected today.
Would reading the map with Ecuflash cause the ECU to be put into a "not ready" state?

--Brock

Are you running anything like a electronic CEL defeat?

With the latest Enginuity/Ecuflash defs you can force all readiness monitors to be immediately ready ("Force Pass Readiness Monitors") for the 16-bit ECU. That is, once enabled and flashed, it will show ready for all tests after turning the ignition on (no drive cycle crap). Of course, this is for testing only and i don't condone using this to pass any emissions tests.

The only "CEL defeats" I'm using are the DTC's through enginuity. I just can't figure out why the codes are reading not ready when I haven't recently reset the ECU.

Tea Cups--when were the latest enginuity defs. released? I'm not sure if I have the newest ones. And if I need to get them, where can I download the defs. since the enginuity site is down?

......

taking a rom dump (reading the map) resets all the learned values and DTCs/readiness tests. if you don't have the new defs you can get them from a mirror you can find in this sub-forum.

Is the forced-readiness planned for th 32bit ECUs as well?

Is the forced-readiness planned for th 32bit ECUs as well?
I have idea how to do it for the 32-bit ECU but I haven't messed with it much.

well mess with it damnit ! lol

Well, after taking the car on a trip today, I took it back to be inspected and all went fine. I guess the ROM dump did reset the ECU.
I learn something new everyday!