Skip to content

auto scan/obd2 difference on vcds

Featured Replies

Finally got round to sorting the CEL on my mk1 fabia.It never worked and turned out the original owner put tape over it :wonder: I ran the auto scan and cleared the faults and the light is still on! So ran the OBD2 part of the vcds and cleared the fault on there and light is off now so far. Why does the second way work and not the first way? Is it likely to have caused an issue?

There should be no difference in the way the code is cleared. What do you mean the previous owner had put tape over it? Tape over what?

You might find the light will come back on again if it's emissions related. What did the fault you cleared detail about the issue?

  • Author

Ive had an issue with the needle sticking at around 90mph (on a private road) so had the cluster out today. It turned out the previous owner had put a piece of tape over the back of the black plastic cover with the symbols on it so the light didnt show through at all. I cleared the codes using the auto scan which showed no emmissions related codes, just a low voltage fault and the light stayed on. I then used the OBD2 part of vcds and it showed an emissins fault but after clearing that the light has gone off. Ive done roughly 80 miles today and its been fine and no light has come back on.Just curious about why the second way showed another different fault and sorted the light out. Ive since rescanned using both ways and nothing has showed on the faults at all.

Ah OK, with you now. Sounds fine then, if you've done that amount of miles since clearing it, and the type of fault it was too.

Can't answer you issue of the way you managed to clear it. In any case it should be the VCDS method of directly addressing the module that should be more reliable!

Ah OK, with you now. Sounds fine then, if you've done that amount of miles since clearing it, and the type of fault it was too.

Can't answer you issue of the way you managed to clear it. In any case it should be the VCDS method of directly addressing the module that should be more reliable!

+1 :thumbup:

This does not mean at all that you've cleared the fault. Every EOBD compliant vehicle's ECM monitors the systems, and when codes are cleared the readiness monitors are set to 'Not Ready'. They won't become 'Ready' until a drive cycle has been completed. This is usually a mix of driving styles and a stop of at least a few hours, typically overnight. Once the monitors are ready again the MIL will come back on if the fault re-occurs or if it still exists. Having said that if the original fault code was a component circuit fault and it wasn't fixed then the lamp would've come back on straight away, so most likely your fault code was generated because of an o2 sensor or catalyst effect related fault.....

  • Author

This does not mean at all that you've cleared the fault. Every EOBD compliant vehicle's ECM monitors the systems, and when codes are cleared the readiness monitors are set to 'Not Ready'. They won't become 'Ready' until a drive cycle has been completed. This is usually a mix of driving styles and a stop of at least a few hours, typically overnight. Once the monitors are ready again the MIL will come back on if the fault re-occurs or if it still exists. Having said that if the original fault code was a component circuit fault and it wasn't fixed then the lamp would've come back on straight away, so most likely your fault code was generated because of an o2 sensor or catalyst effect related fault.....

Thanks for the reply. It seems its had a new o2 sensor before i took ownership of it so thats probably what happen. I do get the feeling the previous owner was a bit of a chav though due to the styling and the fact the car was too expensive for him to insure and run! Check the long gone handle covers and awful "air ducts" infront of the rear wheels. Oh and not to mention the "rs" windscreen thingy! lol

http://i139.photobucket.com/albums/q306/m17tty/vRS5.jpg

http://i139.photobucket.com/albums/q306/m17tty/vRS1.jpg

I do get the feeling the previous owner was a bit of a chav though due to the styling and the fact the car was too expensive for him to insure and run! Check the long gone handle covers and awful "air ducts" infront of the rear wheels. Oh and not to mention the "rs" windscreen thingy! lol

Not to much of a chav as the bits look as if they are Milotec parts....one of the few "CZ" based Skoda styling makers!....if it was cheap "Halfords hero" tat then defo a chav!!!!! B)

  • Author

Not to much of a chav as the bits look as if they are Milotec parts....one of the few "CZ" based Skoda styling makers!....if it was cheap "Halfords hero" tat then defo a chav!!!!! B)

yeah they were milotec but chrome......... thats chav! lol

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.