Hi,

The engine management light is on. Again. It was last on about 6 weeks back and I ended up paying stealer prices to have a glow plug changed :thumbdwn::thumbdwn::thumbdwn:.

Rather than go back a second time I'd like to try and diagnose the fault myself.

Can somebody (anybody) recommend me a device that's is reasonable easy to use, and won't break the bank. Either a hand held scanner or something that runs via the PC, although this would necessitate the purchase of a 10m USB lead.

I'm not particularly IT literate so I'll probably struggle if I have to speak jargon to use it.

Thanks in advance.

Ross-Tech: Home

http://www.ross-tech.net/VCDS/download/VCDSCompatibilityCharts.pdf

Thanks for that,

Thinking about it, I think I'd really rather have a hand held device. Leaving the car switched on while I run upstairs to view the PC doens't sound like a good idea. Especially where I live.

Can anybody comment on a device like this?

U480 CAN-Bus OBDII OBD2 EOBD Trouble Code Read Diagnose: Amazon.co.uk: Electronics & Photo

U280 Car Scanner Reader OBD2 OBD 2 VW Audi SEAT SKODA: Amazon.co.uk: Electronics & Photo

U281 OBD-2 CAN-BUS CODE SCANNER for VW/AUDI/SEAT: Amazon.co.uk: Electronics & Photo

Thanks in advance...........

If you need a quick scan for now I can sort you out, you may have too get to me though

HTH

If you need a quick scan for now I can sort you out, you may have too get to me though

HTH

That would be great if you could. Thanks. I saw you had a reader on the list but in true British style I didn't want to ask. Rather just muddle through.... LOL.

I drop you a PM with some contact details, so that we can sort something out.

maximum length for a USB2 cable is 5 metres,any longer needs hub etc to amplify signal,for another 5 metres max.

I've spotted a gap in the market here: fault scans by internet!

PS: I have that U480 you linked to earlier sat in my car, and TBH, it's been almost as useful as the (unregistered) copy of VAG-COM I have, since I'm only interested in diagnosing faults and clearing codes - not changing settings. Obviously, VAG-COM accesses ALL controllers, not just the engine, but it depends what you're planning on using it for...

Something like this may suit you

Fault Code Reader for Volkswagen, Audi, Seat, Skoda (1996-2009)

Something like this may suit you

Fault Code Reader for Volkswagen, Audi, Seat, Skoda (1996-2009)

Thanks, yes that is the sort of thing I'm after. Do you have first hand experience of using it?

Thanks, yes that is the sort of thing I'm after. Do you have first hand experience of using it?

http://briskoda.net/diagnostics-vag-com/reccomend-me-fault-reader/157860/#post1834630

http://briskoda.net/diagnostics-vag-com/reccomend-me-fault-reader/157860/#post1834630

Thanks. I was wondering if Chris_55 had experience of the one he found to make a comparison to the one you have used/reccomended.

The Chris_55 recommends was the one I was thinking of Gendan iirc.

I've heard they do what your after

isn't it about time ross tech ported vag-com to a pda or palmtop computer anyway??

...sounds like a plan - how hard would it be on a Windoze device?

Anyway, in the meantime, the sub-50 quid handhelds are all much of a muchness, allowing you to read / clear active and incipient engine codes, but not faults with other controllers. Mine has been great for diagnosing a dying coolant temp sensor on my car, and a misfire on a friend's, but was no good when disconnecting SWMBO's battery threw up a rogue airbag light...

Can't speak for the more expensive ones, but they supposedly do everything VAG-COM can, bar data logging.

I've spotted a gap in the market here: fault scans by internet!

PS: I have that U480 you linked to earlier sat in my car, and TBH, it's been almost as useful as the (unregistered) copy of VAG-COM I have, since I'm only interested in diagnosing faults and clearing codes - not changing settings. Obviously, VAG-COM accesses ALL controllers, not just the engine, but it depends what you're planning on using it for...

This arrived today and appears to not be compatible with my car?!? Just wanted to let anybody else know should they read this and decide to purchase one.

I'll most probably go with the one that Chris_55 recommended or perhaps the U281 iirc as I think this was about half the money.........

Which one did you get? The U480? Mine works fine with the Fabia:

Clicky Linky

:confused:

That's got to be the only time I've ever hoped TO HAVE fault codes stored, but heigh-ho... :rotz:

You did have the ignition on when you tried it??? :ne_nau:

Yeah, inanition on and have the 480.

It recognises that there is a fault but won't give me a code. I get "N/A" which according to the manual (I don't have it in front of me) means the scanner does not support my vehicle. 

Not to worry though, shouldn't be too much problem to send it back and I appreciate you were trying to help. :thumbup:

When I had an 'N/A', it was due to the incipient failure of my coolant temp sensor - when the light was on, I got N/A, but then I did a scan when the light was OFF and got the relevant Pending code. What was happening was the the reader knew there was a fault because the light was on, but because the fault itself was intermittent, it couldn't tell you what the fault code was. Only when there had been sufficient intermittent errors to log a Pending code, but not enough to get a light on the dash was I able to find it because dash lights for intermittent faults get extinguished after a certain number of starts anyway. I've not explained that terribly well, but it certainly wasn't my experience that the N/A was due to the reader not being compatible. If it wasn't compatible, it wouldn't get past the 'Protocol' stage, AIUI.

Either that, or it's a fault code for a module that the U480 can't read, of course.

It's up to you what you do with it, but be aware that if it IS either an intermittent fault, or a fault with a module that the U480 can't read, you're more than likely going to be in the same boat with any other cheap handheld you buy...

Hmmmmm :confused::confused::confused:

Well, before you send it back, give the car a scan, delete the codes (even if you get 'N/A'), do a re-scan and see what you get then. Then take the car for a drive and scan it another time, and see what you get then.

How old's your car? My coolant temp sensor started to pack up after four years. It still sent a credible signal to the gauge (which is the usual tell-tale), but it was clearly sufficiently dodgy to start logging codes on the ECU. Your fault could be 101 other things of course, but just speaking from experience...

Thanks for the suggestion. I'll do that.

I already know what the code is as Fatty5000 scanned it for me . (glow plug 2). I wanted to confirm my cheap reader would also pick it up.

I cleared the code last night and it's not back on today so I'll give it another go this eveing.

The car is a '55 plate (Jan '06) so coming up on 4 years. It's futher complicated by the fact that the stealer diagnosed and changed glow plug 3 as knackered about 5 weeks back and that was only days after the cam belt service which as you know involves removing the glow plugs................ Hmmmmm.

Hmmm... ISTR one senior, knowledgeable, and highly-reliable Brisky member stating that glowplug failure on the 1.9 TDIs is virtually unheard-of! :ne_nau:

Which is what the service manager at the stealers suggested when I asked it was worth doing all 4 plugs at the same time.

:rubchin: OK...

Are you / they thinking glowplug failure because the glowplug light takes ages to go out when you start the car? That was what finally nailed it for me in diagnosing coolant temp sensor failure - I think it was Basil who posted about it originally. Might be worth doing anyway as it's a bit of a timebomb, but is dead quick and easy to replace (if a bit messy - the 'tidy' way takes longer!)

No, I have this fault:

Fault Found:

17056 - Cylinder 2 Glow Plug Circuit (Q11): Electrical Fault

P0672 - 35-00 - -

Readiness: 1 1 0 0 0

Which means this:

17056/P0672/001650 - Ross-Tech Wiki

It's the orange engine light/exhaust emmisions light that is the problem rather than the glow plug "coil" light.

It didn't come back on this morning (the scanner allowed me to delete the code but won't tell me what it was), so I now wonder if it's a faulty connection