Jump to content
stormseeker

VAG-COM scanning & help

Recommended Posts

By all accounts that one should work with a 16v 2.0ltr.

 

Did you set VAG-COM up to be at 4,800 "start baud" rate in "Options" so that the programme is pre-set that way before VAG-COM application is started. As registration is PC based, I run one copy of VAG-COM in a separate directory that starts at 9600 and have another in a separate directory which starts at 4800. Corrado modules are 9600 baud rate with this exception.

 

If it still doesn't work, there may be something perculiar about the SKPang interface the 16v ECU doesn't like. The only way to verify is to get someone elses to prove interrogation that is a know workable interface with the 16v.

 

.

Share this post


Link to post
Share on other sites
Hi, Does anybody in the Hull area have the VAG Com for a '95 2.0 16V. I need to check faults with the ABS.

 

Thanks

 

Chris

 

I'm not too far away, just east of york.

Share this post


Link to post
Share on other sites
By all accounts that one should work with a 16v 2.0ltr.

 

Did you set VAG-COM up to be at 4,800 "start baud" rate in "Options" so that the programme is pre-set that way before VAG-COM application is started. As registration is PC based, I run one copy of VAG-COM in a separate directory that starts at 9600 and have another in a separate directory which starts at 4800. Corrado modules are 9600 baud rate with this exception.

 

If it still doesn't work, there may be something perculiar about the SKPang interface the 16v ECU doesn't like. The only way to verify is to get someone elses to prove interrogation that is a know workable interface with the 16v.

 

.

Yes set it at 4,800 still no luck.

I'll see if i can try it on another 16v C and see if that's the problem.

Share this post


Link to post
Share on other sites

Please Help - I have just had my beloved C serviced at my local specialist and th VAG com report says somthing like "YOUR ABS is so foofed I cant even spit out the right code!"

(multiple comm errors I think it said.

)

HEARDY - I am only in Barnsley Mate, any chance of havin a butchers using your VAG Com?

 

:notworthy:

Share this post


Link to post
Share on other sites

Quick question.. can someone point me at what I need to buy if I want to get VAGCOM? I know I need a cable and I need some software.. which would be most suitable? I'm looking for the MK4 Golf..

Share this post


Link to post
Share on other sites

Ouch.. me and my mate were hoping it was about £100 so we could just go halves on a kit for both our Golfs but at that price, I think i'll give it a miss.

 

Cheers! :)

Share this post


Link to post
Share on other sites

Bit off the subject, but can anyone supply a wiring diagram for OBD2 connector? I've got a 2.9VR Conversion in my Mk2 Golf, the guy supplied the whole loom which I swapped out and works fine, but a couple of the pins have fallen out the connector and part of the loom which has 4 wires in it, connected back to the multiplug has been cut?? Any help would be apprecriated, realise its not a Corrado!! Thanks Gav.

Share this post


Link to post
Share on other sites
By all accounts that one should work with a 16v 2.0ltr.

 

Did you set VAG-COM up to be at 4,800 "start baud" rate in "Options" so that the programme is pre-set that way before VAG-COM application is started. As registration is PC based, I run one copy of VAG-COM in a separate directory that starts at 9600 and have another in a separate directory which starts at 4800. Corrado modules are 9600 baud rate with this exception.

 

If it still doesn't work, there may be something perculiar about the SKPang interface the 16v ECU doesn't like. The only way to verify is to get someone elses to prove interrogation that is a know workable interface with the 16v.

 

.

Yes set it at 4,800 still no luck.

I'll see if i can try it on another 16v C and see if that's the problem.

Right then i've finally got it to work and there are no fault code's,but when i go into measuring blocks i can't get any reading's it just says ERROR in most of the blocks any ideas whats up?

Share this post


Link to post
Share on other sites

The 16v 2.0ltr has only a Group 000 measuring block available. 10 fields with digits in each which have to be used in conjunction with the workshop manual. ie. "field 4 must achieve value 5 to pass, if other value replace......" So, its not like the VR6 with 7 sets of measuring blocks. That is why 001 upwards give error.

 

.

Share this post


Link to post
Share on other sites

Right, NickRStorm Vag-COMmed my VR at the TV meet today (mine is a '93 L-reg VR), and it only found the ABS system, not the ECU or anything else. He also scanned ZippyVR6's ('93, 2x2)and had the same result - yet a scan on thebrayne's '96 with the OBD2-style connector found everything.

 

I thought that all VRs were completely scannable, and only the 2.0 16V could only read the ABS and nothing else?

 

Any ideas why mine and Rog's weren't responding on the ECU and so on?

Share this post


Link to post
Share on other sites

Sounds like the interface lead was not compatible. What was the interface used (Ross Tech or EBAY type)?

 

VR6 engine ECU's are not a problem with communications. No special set up of VAG-COM needed. Should just go straight in and lock on.

 

.

Share this post


Link to post
Share on other sites

It was an official RossTech one, which left me slightly confused as to why it didn't seem to want to read! I'm afraid I can't remember which version of VAG-COM it was though, though I wouldn't have thought that would matter...

 

Ah well, at least the ABS fault codes are cleared! Cheers Mr RW1 sir!

Share this post


Link to post
Share on other sites

I have two Ross tech ones (optical & electrical isolation) and never have trouble with VR6's early or late. 9600 baud rate preset and straight in.

 

.

Share this post


Link to post
Share on other sites

Had the flat battery off for recharge and took the storm for 100 mile drive. stopped the car, then had to transporter it home as it would cut out just after startup! maybe some inlet sensor gone or something, or maybe immobiliser fault anyhow desparate for someone in Central/West /N.West/S.West london area to help out with their vag-com. sorry i cant come to you, large drink on me. im in W3 Acton.

 

Sane

Share this post


Link to post
Share on other sites

Hi,

I have G60 and I checked the VAG-Com socket which is 2x2. However it seems one of the cables is missing. Could is be like that? Or I will remove the dashboard to find it out where is the missing cabe.

 

vagcom9wi.th.jpg

 

Koray Ustuner

Share this post


Link to post
Share on other sites
Hi,

I have G60 and I checked the VAG-Com socket which is 2x2. However it seems one of the cables is missing. Could is be like that? Or I will remove the dashboard to find it out where is the missing cabe

 

3 wires means analogue (blink code) diagnostics - VAG-COM not useable.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...