VAGCOM: Communication Problems

Hi everyone,

For the sake of clarity, I have started a new thread (Rainer K, please forgive me).

It's still about the problems with the Marelli MSG (see: 'Motor computer not responding' by Ulf).

Problem:
The MSG (Message Security Gateway) suddenly stopped responding (error message: too many communication errors), while all other ECUs (Electronic Control Units) are functioning normally.

Due to the suspicion that it might be an adapter issue, I switched from 'Noxon' to 'Maik,' but without success!

Configuration:
MSG: Marelli 1AV
Adapter: MAIK
PC: 486 66 / Windows 95
VAGCOM versions 208.1 and 212 beta.

Are there any best practices or recommended settings for baud rate, KW2 delay, TST address, etc., in cases like this?

And most importantly: What is the probability that the MSG is defective?

I would be grateful for any help!

Jürgen.

Hello Jürgen,
Try using a larger pull-up resistor on the K-line.
While this contradicts the standard, the VAG test technicians do the same thing (2k2 to 10k).

Best regards, Rudi.

Take a look at the 'diagnostic adapter' technical articles. At the very end, there's information about the settings that helped me resolve the issue. Also, try the 0.81 version; it was less problematic for me than the 2.xxx versions!

Hello everyone,

Thank you for the tips!

After a long (very long) series of tests, I finally got it working.

Sure, here is the translation:

'The following setting:'

Start Baud: 4800
KW2 Delay: 15
BLK Int: 30

It only works with version 212.2 beta; it doesn't do anything with version 208.1! (which confirms my initial suspicion that VAGCOM might not be entirely innocent in this issue).

I also tested various potentiometer settings on the adapter, but it had no effect on the function (at least with my MSG)!

'If I ever have a lot of free time, I'll test my old Noxon adapter with the configuration mentioned above (if it works, I'll be kicking myself for not having tried it sooner).'

Best regards, Jürgen.

@juergen

Congratulations!!!!!!!

You see, reading helps! And you're not the first person to have these problems! Don't immediately demonize VAG-COM just because it's not working the way you expect it to.

@joergs

Please note: Version 208.1 cannot be made to run, even with Maik's adapter.
The 'breakthrough' didn't come until version 212.2 beta.

So, in my opinion, it probably wasn't just the adapter that caused the problem!

But now it's working, so thank you everyone for your help!

Best regards, Jürgen.

@juergen


'With version 2.081, I also couldn't establish any communication! I'm running DRV version 2.082. It only has one cosmetic flaw: it crashes quite often (but that's a known issue)! The new DRV version (3.022) also runs without problems and no longer crashes due to a general 'dirty' error! I think that version 2.081 might have some communication problems with our specific vehicles, because while communication was established with other VW vehicles, it wasn't entirely without issues.'
As I mentioned earlier, I had the fewest problems initially with the 0.81 beta version! It actually worked flawlessly right out of the box, without any communication issues. Of course, I'm not even going to mention the error entries in the control unit and the sudden bursts of acceleration with excessive black smoke that were described in another thread.