[flashgorden2010]

Hello,

I have already problems with flashing Audi models with ODIS-E.

Audi A4 Avant 2013 2.0 TDI 177HP


ODIS Engineering 6.2.2
Diagnostic Kernel: 310.3.0
MCD: 3.0.0
ECF: 22.1.0 (20140912)
PDU API: 1.20.23
ODX (MCD project): AU48X

I have the problem with every Audi !!

Always this fail:

Error during update programming Job runtime: 0:00:00.116 Initial
repetitions: 0 Total repetitions: 0 Last value of STmin: 4294967295 µs
unknown Failure - Programming aborted


VW, Seat and Skoda...no Problem!

The logfile I have of course !!!!

PLEASE PLEASE can help me as someone.

[rs@chip]

Try use 5.0.14 is best for flashing I also had problems with newer odis

[flashgorden2010]

Try use 5.0.14 is best for flashing I also had problems with newer odis

Thank you alex, I try the times out!

[apoelistas]

What is the pdu-api of your firmware?? try to replace/renane the apps pdu folder files with your hardware pdu-api. also copy your pdu-api driver to odis-e pdu folder.

search some russian sites regarding the procedure.

[champagnecharly]

search some russian sites regarding the procedure.

Seems like I should start learning to read Russian too.

[apoelistas]

I could not find same info in english. The translation engine I used was not perfect. If I knew Russian I would translate.

[flashgorden2010]

What is the pdu-api of your firmware?? try to replace/renane the apps pdu folder files with your hardware pdu-api. also copy your pdu-api driver to odis-e pdu folder.

search some russian sites regarding the procedure.

the PDU-API Version is the same.....
Should I notwithstanding copy the PDU-API folder of ODIS-E into the modules of ODIS-S?

Software-Versionen :
Diagnostic Information System Service Patch 3 . 0 . 3

Haupt-Feature : 9.3.10
-Weitere :
MCD-Server Hersteller : Volkswagen AG
MCD-Server Name : VW-MCD
MCD-Server Version : 310.5.3
MCD-Server API-Version : 3.0.0
PDU-API Hersteller : Softing D-PDU API for VCIs
PDU-API Version : 1.20.38
PDU-API API-Version : 1.20.38
ECF Version : 26.4.0 (20160209)
General Testscript API Version : unknown
Testscript API Version : 4.31.6
Measurement Types : 9.0.4

[apoelistas]

The problem with flash is odis-e not odis-s. So we need to concentrate on odis-e.

Change project folder of odis-e to odis-s as a first step (admin settings).

I will give more details when I am back from holidays regarding the above. I don't have odis-e on my tablet.

To find the pdu api of your hardware you need to use the pdu-api test app.
1. Select the firmware version EDIC_D_PDU_API_1.20.???
2. Click the Parse the File MDF
3. This field should appear your diagnostic module
4. Press PDUModuleConnect

There you have 2 options. OE and OS. Check if OE passes the tests. If not try the following.
   

Install the pdu-api 1.20.???
Directories:
C: \ PROGRAM FILES (X86) \ SOFTING \ D-PDU API 1.20.???\ VeCom \ and copy the contents of a folder in the directory C: \ ODIS-DIAG-MODULES \ PDUAPI \ VEN-SOFTING \ 1.20.??? \ VeCom \

For the version of ODIS ENGINEERING 6.2.2 copy the folder in the directory C: \ ODIS-DIAG-MODULES -ENGIN \ PDUAPI \ VEN-SOFTING \ 1.20.??? \ VeCom \

I am not sure which firmware is governing so we need to test both:
1. The pdu-api of odis-e
2. The firmware pdu-api of vas5054a.

If it is the second use the pdu-api of your hardware where you see the question marks??? That makes more sense to me.

Hope this is helpful.

I did one step additional to the above: it is an example.
What I did with Odis 6.6.1 which has 1.20.034 pdu-api was to replace that with 1.20.037 pdu-api and rename everything that has 1.20.037 to 1.20.034.

My pdu-api of my hardware is 1.20.037.

[apoelistas]

Odis engineering 6.6.1 works fine with VXDiag VCX nano WiFi. I can do coding, I can read faults, I tested Xenon calibration, I can clear faults.
I have not tested to flash a Control unit, because of my past bad experience with instrument cluster with odis-e 6.7.5 and vcx nano.

[cornel]

Reflashing audi is different from other vag cars
use odis s - flas programm or flash 3rd button