|
Post by jrusso17 on Jun 27, 2022 14:22:42 GMT
Hey, Questions. can OBD read the if your car has a tune and what type? Can it be setup to automatically clear faults when they show up? Why do I ask? Well I bought a 2015 Golf GTI a month ago and it has a Catless Downpipe. Of course it keeps throwing the CEL which I clear but like 20 minutes later comes back on. At this point I'm looking to be done with it and put a new Catted exhaust on the car. My dilemmas, 1. I don't know what "brand" exhaust the car has 2. The car is tuned but I don't know what it has. So I am not sure what the appropriate catted exhaust I should get that would work with the car/engine. Been trying to locate originally owner so I can get more info but no luck so far.
|
|
|
Post by dv52 (Australia) on Jun 27, 2022 22:40:08 GMT
jrusso17 : hmm........ happy to be told otherwise, but I don't believe that OBD11 (or any other third-party diagnostic device) can tell you whether the car has been tuned. That said, OBD11 does have an EEPROM facility where you can read/change individual memory locations within module firmware. Theoretically, this function should allow a user to compare the current value in a memory location with the factory setting - but you would need to have a detailed knowledge of how the factory firmware is structured to understand which memory locations to interrogate - not something a normal OBD11 user can do!! As for your question about automatic clearing of faults - the answer is yes, ........well - kind-of, yes!! If you look at the freeze-frame data for a fault as reported by a module, you should see something like this:
Priority - # Malfunction frequency counter - # Unlearning counter - # km-Mileage - # date - #
Notice "Unlearning Counter". This means that if the error isn't re-registered in fault memory after the number of successive ignition cycles as specified, the fault will automatically be cleared by the module.
On your car, it seems that the error is re-registered as a fault regularly (this should increase the number in "Malfunction frequency counter"), so I assume that the "Unlearning counter" number is never reached.
Alas, there is no way to automatically stop this process AFAIK
Don
|
|