FWIW, here in Mass any OBD-II vehicle gets plugged in for a code check in lue
of going on the rollers for the driving cycle emisssion test. I found out the
hard way after working on a couple of family member's cars that if you clear
the codes with a scan tool immediately (with in a few days) before going for
the emission test you get turned away. Apparently a bit gets set when you clear
the codes the tool they use in the inspection stations read this bit and will
not allow the inspection to continue until the code is cleare by x start
cycles. Both family members were told to come back in a couple of weeks.
My recomendation would be not to use the scan tool at this point.
Dave Clement
99 SLT+ CC 4x4
In article <BAY101-DAV11AA0903E5B0339B997EDED2F00@phx.gbl>,
fasstdak@hotmail.com ("Bernd D. Ratsch") writes:
>
>
> 255 Key Cycles
>
> -----Original Message-----
> From: owner-dakota-truck@bent.twistedbits.net
> [mailto:owner-dakota-truck@bent.twistedbits.net] On Behalf Of
> Walt@Walt-n-Ingrid.Com
> Sent: Monday, June 13, 2005 7:17 AM
> To: dakota-truck-moderator@bent.twistedbits.net
> Subject: DML: Stored Error Codes - How Long?
>
>
> Does anyone know how long stored codes stay in the computer? I assume they
> stay even after disconnecting the battery. Do they stay for 50 key cycles
> or are they cleared only with a scan tool? I got a misfire-detected code
> last fall with my 2000 Ram. Since then I've given the truck a tune up and
> disconnected the battery to reset the check engine light. I have to take
> the truck through CT's new emissions and they now plug in and check for
> codes. I want to make sure that is cleared before taking it down to get
> tested.
>
> Thanks,
>
> Walt
This archive was generated by hypermail 2b29 : Fri Jul 01 2005 - 09:48:06 EDT