[Diy_efi] Chrysler ODB2 / VSS question

[Martin Lebeau]

how can I equip myself with that ? ( to clear that kind of history)
----- Original Message ----- 
From: "Mike Schwall" <mschwall at cox.net>
To: <diy_efi at diy-efi.org>
Sent: Wednesday, January 01, 2003 11:07 PM
Subject: RE: [Diy_efi] Chrysler ODB2 / VSS question


> True, type A codes are single instance problems that triggers a code &
> MIL and creates a stored history code.  This history should be erasable
> using an OBD scanner.  Type A codes are caused by certain severe
> emission problems that only a single instance of a malfunction will
> trigger the code and light as well as a stored history code.  Not sure
> how the VSS ranks in priority (from A-D) or how the VSS is used with the
> emissions equipment, but I doubt the lack of speed information is going
> to cause a major emissions problem. YMMV, IMO
> 
> Mike
>   
> 
> 
> -----Original Message-----
> From: diy_efi-admin at diy-efi.org [mailto:diy_efi-admin at diy-efi.org] On
> Behalf Of Djfreggens at aol.com
> Sent: Wednesday, January 01, 2003 9:27 PM
> To: diy_efi at diy-efi.org
> Subject: Re: [Diy_efi] Chrysler ODB2 / VSS question
> 
> 
> the only way the trouble code will stay after a battery reset is if the
> problem is still persistent. also crhsylers later obd2 chrysler have a
> code history so even when current static code are cleared there will be
> a basic non violitale copy kept on the flash chip. its way more
> complcated then a battery/power down code clearing clear. 
> 
> 
> 

_______________________________________________
Diy_efi mailing list
Diy_efi at diy-efi.org
http://www.diy-efi.org/mailman/listinfo/diy_efi