ECU Tuning: No Access to EDC17 MSG

Hello everyone,

Version 704 of VAG-Com currently does not have access to EDC17.

The vehicle to be inspected is an Audi A5 3.0 TDI (CR).

Does anyone know why everything except the MSG (Modular Signaling Gateway) can be accessed with VAG-COM?
Has the seed-and-key method, or even the protocol for diagnosis, changed (e.g., using XCP instead of CCP)?

Is there a beta version available with EDC17 access, or when will the next version be released?
With the current VAS, we can address the MSG .

Best regards, Jochen.

Take this:

http://www.ross-tech.com/vag-com/download/beta/current.html

Thank you.

Unfortunately, this attempt has failed .
The computer crashed immediately upon closing.

Is anyone already working with the beta version? Was this an isolated incident?
Then I would try it again with that.

Sure, here's the translation:

'Something else:'

The motor is a CAP.
According to the SSP (Service Program), the 3.0 should be a bug and should actually have an EDC16CP.

Is the crucial difference here the fact that it has an EDC17 engine control unit?

Best regards, Jochen.

C... Aren't engines supposed to have four digits in their model number?

My Beetle at least survives the BMR (Siemens VDO, or whatever that control unit is).

m;

C... Engines should actually have four digits, right?

Yes, I would also expect that.

It could also be called CAPO or CAP0, considering that the many zeros still belong to the MKB (German tax identification number).
When looking at the engine, I wouldn't focus too much on the engine code .

Best regards, Jochen.

Hi Jochen,
I'm currently running the latest beta version. It works without any problems with MSA15 and EDC16.

Best regards,
Rudi

The beta version has been running flawlessly on both XP and Vista so far.
So far, I haven't had any problems with the new CAPA, CAUA, CALA, CAXA, and CABD.

So far, I haven't had any problems using VAG-COM with my Polo, which has an EDC17 engine control unit.

Okay, next attempt using VAG-Com Beta:

Unfortunately, with exactly the same lack of success .

'Address 01: Engine'
'cannot be reached'

Here's what I've gathered so far:

For the A5, Audi has changed the protocol and (allegedly) brought it very close to the Mercedes-Benz diagnostic protocol.

The 711-Beta has now been extended to also apply to the A5.
However, according to SSP documentation, the A5 3.0 TDI has a known issue, specifically with the EDC 16CP engine control unit, which is not the type of engine control unit used in 'our' engine.

(..) also
So far, I haven't had any problems with the new CAPA, CAUA, CALA, CAXA, and CABD.

These engines, however, are not found in the A5 , where, according to my information, the protocol changes were implemented.
So far, using VAG-COM has worked without any problems on my Polo with an EDC17 engine control unit.
It's not an A5 format (see above).

With the current VAS, it is possible to access the MSG.
I will try connecting the vehicle to the VAS diagnostic tool again and see how the MSG (Module Software Generator) responds.

We may have to wait for the (next but one) version of VAG-COM in order to be able to read out data from 'our' A5 3.0 TDI.

Best regards, Jochen.

Hi Jochen,

It should actually work. What diagnostic hardware are you using?
According to information from Ross-Tech, the HEX-USB+CAN (= professional systems KKL+CAN (USB)) has been successfully tested.

Best regards, Rainer.

Okay, next attempt using VAG-Com Beta:
However, according to SSP documentation, the A5 3.0 TDI has a known issue, specifically with the EDC 16CP engine control unit, which is not the type of engine control unit used in 'our' engine.


The BUG is the old 3.0 TDI engine, which was used in vehicles like the Q7, and which...
It definitely works, even with version 704.1.

Apart from that, this engine was NEVER installed in the A5! From the start of production of the CAPA, it was...
ready for deployment.

According to information from Ross-Tech, the HEX-USB+CAN (= professional systems KKL+CAN (USB)) has been successfully tested.

Hello Rainer,

We have the HEX + CAN (which uses RS232 instead of USB) professional system.
Should the difference already be apparent here?

Apart from that, this engine was NEVER installed in the A5! The CAPA could be used from the beginning of production. }

That aligns with what I have in my yard.
Therefore, once again: SSP should be enjoyed with caution in certain areas.

Best regards, Jochen.

Is the problem only with the engine? How about other control units?

Please use Beta 711.1 and do the following: [Autoscan] -> [Gateway installation list]. What happens then? If the function completes successfully, please post the result here using the [COPY] button.

-Uwe-

Hello Uwe,

I had started a car scan, but I then actively aborted it.
I can attach this one for now.

If a complete car scan is needed, I can post it again tomorrow.

The control units that I actively selected were visible, and the scan logged communication problems.

Therefore, I would say that not all departments work perfectly together.
But sees for himself:

Best regards, Jochen.

Okay, UDS itself seems to be working...

See:

http://www.ross-tech.com/vag-com/download/beta/710-ScreenShots/UDS-DTC.png

as an example

So, UDS itself is working....
UDS?
Is this the 'new' communication protocol?
I'm familiar with UDS flashing, but from a different perspective. A different SG manufacturer and much larger 'vehicles' .

Rainer wrote that Rosstech tested it with a USB adapter.

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

With the VAS (Vehicle Diagnostic System), the vehicle can also be accessed, so there is fundamentally a possibility to do so.

Best regards, Jochen.