HELP vagcom not connecting

[MarkWales]

cannot seem to connect my leon a 04 plate tdi cupra to central convenience 46 but the same setup is able to connect and control on mates 53 plate tdi cupra

cannot connect to control message pops up in my car but as above works fine on a 6 month older car

any ideas

 

[Theresias]

What version of VAG-COM and what interface hardware are you using?
Checked the car for a 3rd party/aftermarket radio?

http://www.ross-tech.com/vag-com/aftermarket-radio.html

 

[MarkWales]

cheers cannot believe this and yes i have a kenwood head unit installed - thanks for the response

 

[Andrewcupra TDI]

for the obvious cant see the trees through that forrest !!

luckily didnt blow anything then , u still got the original mark , fit it in and wel have another go

also found it odd that it will connect to the engine and not the convenience 46

software is 409.1s i believe

 

[Andrewcupra TDI]

rather than make another post , il tag along here


while checking vag com to see my injectors cilinders 1 & 4 ran negative figures and 2 & 3 ran positive anyone know off hand why this is wernt sure what to search for in vag com section


where as marks showed very differently all being consistent mostly all positive

cars are listed at OP's first post

any one help on this

 

[MarkWales]

will refit for monday so we can have another go

 

[MarkWales]

ok guys refitted the standard aura head unit last night

Still could not connect to the option 46 - any ideas guys what else it can be?

all i want to do is turn on the alarm chirp

 

[Cowie]

Hi mate just found this in one of the threads by cjhawker,this could help

COMMON ISSUES
Make sure the ignition is on. Don’t have to start the engine for 90% of things
If getting comm. Errors lower the Baud Rate in the Comm port setting in windows
device manager.
If having trouble or cant connect to Address 46: Central Conv
Try removing then reinserting these fuses to restart the module (easier than
disconnecting the battery):
Number 14 - (10A) is in the manual as interior lighting, central locking/electric
windows. It also has underneath a 5A marked down for Interior light but still under
14.
Number 38 - (10A) is boot light and also central locking/electric windows.

hope it helps,i had this at the weekend,wouldn't connect,then an hr later it would
i blame the e-bay cable tho,gonna invest in the proper one from ross-tech

 

[skahigh]

Ye, I can never connect to my convenience module (too many errors). It's got to be down to the ebay cable I reckon.

 

[MarkWales]

hmmm the cable as i said earlier connects fine to andrews car which is also a Cupra TDI but odly has not got a boot 12V supply or the lights above the sunvisor's

will try the fuses next monday though

 

[Theresias]

Just because it connects to a different car (even if its a similar model) may not indicate that its actually flawless. Believe it or not, with 3rd party hardware the mentioned "too many communication errors" is a design flaw of the interface hardware used. There's a reason why our stuff uses micro-controllers and costs a little more than the cheap stuff, because we need to ensure that it works no matter what.

 

[MarkWales]

anyway of testing lead for faults

 

[Andrewcupra TDI]

would love to buy the real deal , but cant justify them costs (not yet anyways )

 

[BeartheBruce]

anyway of testing lead for faults

You can go to [Options] [Test] but that will not tell you very much about communications issues.

You can play with the baud rate on the [Options] screen to see if you can improve things. As Sebastian has said, the electronics in the interface are the determining factor.

 

[MarkWales]

still find it strange that it works perfectly on the one leon and not the other

 

[BeartheBruce]

still find it strange that it works perfectly on the one leon and not the other

The control modules are very different from one platform to another. They often do not communicate at the same baud rates on the KLines. As a result, the interface must be capable of adapting to these changes. The higher priced units do this. The lower priced ones drop the circuitry which handles this change so they can give you the bargain basement price.

VAG-COM does give you the ability to tweak the baud rate to see if you can find one at which the interface will operate.

By the way, within the same vehicle, you can have modules that will communicate at one rate and others that communicate a completely different rate. It's not the diagnostic tools issue - it's the VAG group issue.

All modules using the CAN bus communicate consistently. But, VCDS for CAN only runs on genuine Ross-Tech interfaces.

 

[MarkWales]

What version of VAG-COM and what interface hardware are you using?
Checked the car for a 3rd party/aftermarket radio?

http://www.ross-tech.com/vag-com/aftermarket-radio.html

is this still the case for VW Golfs

my lead works fine in the golf which is a 2001 tdi with non standard head unit

 

[MarkWales]

The control modules are very different from one platform to another. They often do not communicate at the same baud rates on the KLines. As a result, the interface must be capable of adapting to these changes. The higher priced units do this. The lower priced ones drop the circuitry which handles this change so they can give you the bargain basement price.

VAG-COM does give you the ability to tweak the baud rate to see if you can find one at which the interface will operate.

By the way, within the same vehicle, you can have modules that will communicate at one rate and others that communicate a completely different rate. It's not the diagnostic tools issue - it's the VAG group issue.

All modules using the CAN bus communicate consistently. But, VCDS for CAN only runs on genuine Ross-Tech interfaces.

the two leons must have the same control modules

 

[Theresias]

Yes, the aftermarket page is still valid for vehicles using the k-line for communication.

When it comes to "must have same control modules", I wouldn't be so sure about that... even if its the same model year there is no guarantee for that.