Kein Zugriff auf EDC17 MSG | Posts 16+

@Jochen:
How do you access the interface (from the laptop)?
If available/possible, use either a PCMCIA RS232 interface or a direct connection.
a desktop PC with a genuine serial port (we had a case of this at the company today,
that the interface in a recent IBM docking station repeatedly experiences transmission errors.
'It was made with high data rates in mind, but it didn't perform well (the USB dongle was also junk).'
[edit] This had nothing to do with VAG-COM. [/edit]

Hello Rudi,

My CF28 still has a 'true' RS-232 interface.
Another CF29 exhibited the exact same behavior when connected with the VAG-Com adapter.
Otherwise, the dongle functions perfectly. It can read the EDC16 module from my 8P.

Best regards, Jochen.

Okay... then it wasn't/is not that, at least not yet.

Jochen_145 wrote:

Hello Rudi, My CF28 still has a "true" RS-232 interface. Another CF29 exhibited the exact same behavior when connected with the VAG-Com adapter. Otherwise, the dongle functions perfectly. It can read the EDC16 module from my 8P. Best regards, Jochen

You have a private message.

Rainer wrote that Rosstech tested it with a USB adapter.

We have the RS232...
Perhaps the problem lies here, as the drivers are correspondingly different!

Drivers can be quite different. RS-232 does not require drivers.

With RS-232, the timing behavior is actually slightly better than with USB.

Aber um wirklich sicher zu sein habe ich mich bemüht noch mal Beta 711.1 mit HEX-COM+CAN Interface zu testen. Erst am Tisch mit A5 Gateway und CAPA MSG, und dann noch an einem echten A5 mit CALA Motor. Beide Motoren benutzen das UDS Protokoll. No problem.

Jochen, I really don't understand what the problem is. Given the multiple, sporadic communication errors that are visible in your parts list, I suspect that something within the car itself is responsible. Please perform a complete scan of the entire vehicle. There might be something else to see.

-Uwe-

Hello Uwe,

As requested, I'm posting a complete vehicle scan of the car again.

Due to the several sporadic communication errors that are visible in your installation list, I suspect that something within the vehicle itself is responsible.

This cannot be ruled out, as the vehicle does not necessarily have to be in complete original condition.

What makes me a little bit curious is the fact that the VAS was able to communicate with the MSG...
Therefore, there must be a difference between the communication of VAG and VAG-Com. Is a workshop code or something similar required?

Another thing I've noticed is:
The A5 activates terminal 15 after 3 minutes. If the engine is not started within that time, the vehicle will switch off again.

If this occurs during the car scan, communication understandably breaks down. Beta version 711 crashes during the initialization of communication with the SG (Service Gateway) at this point and cannot be terminated.
The entire computer is frozen and needs to be restarted 'hard.'

The problem occurred independently on two different computers.

If the engine is running during the car scan, there are no issues.

Best regards, Jochen.

Here's a small update for general information: the Jochens diagnostic interface is not an original Ross-Tech HEX-COM+CAN. He also didn't buy it as such...

That should resolve the issue.

Best regards, Rainer.

Jochen,

Please write me an email. My username here is also my email address; just add '.com' to the end.

-Uwe-