My VAGCOM wont work (surprise surprise!)

[Audi A4 Lover]

Hi guys, I bought a 3rd party lead off fleabay, using version 311, it seems all was going swimmingly untill I try to scan or do anythign through the software, then I get an error message saying that vagcom has encounterd a problem and needs to close. Also when I checked the compatability thinggy,it said it wasnt compatable, I dont see how this can be as it read some of my cars data then decided to stop.Sadly after this the battery ran oput on the laptop so I have to wait before its charged before I have attempt number two.Anyone got any ideas other than re installing it?

[dansansome]

i think the shareware version will only allow you to read a few codes on the autoscan setting before reporting errors. (im basing this on v409.1 shareware) maybe the 311 version cant handle this shareware limitation propely and just dies.

you should be able to get 409.1 running easily enough, that shuoldnt close when the shareware limitation is reached. failing that, you may have to manually navigate to the control modules to find all the fault codes.

hth

[Eshrules]

your first port of call should be the vendor mate, if they're worth their weight in gold they should be able to advise you

[Audi A4 Lover]

well, Im getting the error messages even when im trying to access the individual control modules.I think Ill try version 409, as I remember the only reason i tryed 311 was because it has the USB listed in the interface locations bit,but the cable has fount itself a nice little place in a city called com4, so Ill install that then report back.


cheers!



**update**

vagcom managed to scan the engine before deciding it wanted to close, version 409 that is.Its still claiming that my car isnt OBD compatible,but I think its lying!

[brentos2004]

sounds to me like the cable drivers might be dodgy. What operating system are you using on the laptop? Did you install the drivers that came with the cable as this is a common problem. I had an issue in vista which was caused by two things A) I used the drivers that were on the cd ( I then uninstalled them and let vista install the correct drivers) B) It was on a COM port that was in use so changed it to COM2 and it worked fine. Failing that try uninstalling everything and reinstalling.

[bearthebruce]

i think the shareware version will only allow you to read a few codes on the autoscan setting before reporting errors. (im basing this on v409.1 shareware) maybe the 311 version cant handle this shareware limitation propely and just dies.

The 311 did not just up and die when it encountered problems. As someone else said, this problem is either the fleabay hardware or it is a driver compatibility issue.

you should be able to get 409.1 running easily enough, that shuoldnt close when the shareware limitation is reached. failing that, you may have to manually navigate to the control modules to find all the fault codes.

hth

Right, neither of these packages should close and die. We sold version 311 for nearly a year until it was replaced by 409.

The other issue you may be having is if you are trying to run 4 year old software under Vista. If you are, you need to search the forums for how people have tweaked things in XP compatibility mode to get it to work. RT is not going to go back and make 4 year old versions Vista compatible.

I hope you get your issue resolved. I'd contact your fleabay vendor for support.

[Audi A4 Lover]

Sorted it!Had to allow the program to run as an administrator!

[Sam]

your first port of call should be the vendor mate, if they're worth their weight in gold they should be able to advise you

I hope you get your issue resolved. I'd contact your fleabay vendor for support.

That's two people who have told you the same thing, I'd follow their advice

[Audi A4 Lover]

That's two people who have told you the same thing, I'd follow their advice

Erm....Iv sorted it out

[Sam]

Erm....Iv sorted it out

Heh, you posted 4mins before me, I type slowly

EDIT: Glad you got it sorted in the end.