VAG-COM/VCDS EVERYTHING

[Fabio89]

I flashed my 415 back to the original firmware it came with and used VCDS 20.4.1 to test on my same electric car.
This is the auto-scan list it produced:

01-Engine -- Status: OK 0000
03-ABS Brakes -- Status: OK 0000
08-Auto HVAC -- Status: OK 0000
09-Cent. Elect. -- Status: Malfunction 0010
10-Park/Steer Assist -- Status: OK 0000
13-Auto Dist. Reg -- Status: OK 0000
15-Airbags -- Status: OK 0000
17-Instruments -- Status: OK 0000
19-CAN Gateway -- Status: OK 0000
23-Brake Booster -- Status: OK 0000
29-Left Light -- Status: OK 0000
3C-Lane Change -- Status: OK 0000
42-Door Elect, Driver -- Status: OK 0000
44-Steering Assist -- Status: OK 0000
4B-Multifunc. Module -- Status: Malfunction 0010
51-Electric Drive -- Status: OK 0000
52-Door Elect, Pass. -- Status: OK 0000
5F-Information Electr. -- Status: OK 0000
75-Telematics -- Status: OK 0000
8C-Hybrid Battery -- Status: OK 0000
A5-Frt Sens. Drv. Assist -- Status: Malfunction 0010
BD-Hi Volt. Batt. Charg. -- Status: OK 0000
C5-Therm. mgt. -- Status: OK 0000
C6-Batt. Chrg. -- Status: OK 0000
E0-Auxiliary Display 1 -- Status: OK 0000

And you can see that these are missing from my last test (using 405 FW 01.02.05):

39-Right Light -- Status: OK 0000
D6-Light Ctrl Left 2 -- Status: OK 0000
D7-Light Ctrl Right 2 -- Status: OK 0000

And this is new on the org fw:

E0-Auxiliary Display 1 -- Status: OK 0000

One thing I noticed which are the same for them both is that module "03-ABS Brakes -- Status: OK 0000" shows OK without a fault but when the module was scanned it actually contains a fault:

Fault when using 405 FW:

Address 03: ABS Brakes (J104)       Labels: 5Q0-907-379-OMG-V1.clb
   Component: ESC
   Revision: 00000000    Serial number: 
   Coding: 01FA40A12C21216E477C060361CA2980023484E26086943338915078C2E203
   Shop #: 
   ASAM Dataset: EV_Brake1UDSContiMK100OMG 003019
   ROD: EV_Brake1UDSContiMK100OMG_003.rod
   VCID:


2 Faults Found 
8400 - Databus 
          U1123 00 [032] - Received Error Message
          [FCAN: AB_Gurt_FA signal is invalid]
          Intermittent - Not Confirmed - Tested Since Memory Clear


16401 - Tire Pressure Warning 
          C102D 00 [032] - -
          Intermittent - Not Confirmed - Tested Since Memory Clear

Fault when using org 415 FW:

Address 03: ABS Brakes (J104)       Labels: 5Q0-907-379-OMG-V1.clb
   Component: ESC
   Revision: 00000000    Serial number:
   Coding: 01FA40A12C21216E477C060361CA2980023484E26086943338915078C2E203
   Shop #:
   ASAM Dataset: EV_Brake1UDSContiMK100OMG 003019
   ROD: EV_Brake1UDSContiMK100OMG_003.rod
   VCID:


2 Faults Found 
8400 - Databus 
          U1123 00 [032] - Received Error Message
          [Tip-TNF 239934]
          Intermittent - Not Confirmed - Tested Since Memory Clear


16401 - Tire Pressure Warning 
          C102D 00 [032] - -
          Intermittent - Not Confirmed - Tested Since Memory Clear

It does not show the same text but I guess this could be coz of VCDS 20.12 vs 20.4.1?

i have few cables with STMF415 chip. Let us know when its done

[flyfvdi]

hi which is the latest VIIPlusLoader for 405 chip has anyone a link to it please. many thanks.

Buy VCDS Hex-V2 from aliexpress
https://www.aliexpress.com/item/1005...6bae4edfKNwPWm

[flyfvdi]

My 415 does not work with the VIIPlusLoader. Reason is that the firmware bundled in this loader checks the present of the extra "encryption" chip and this need patching.

yes， 415 vcds hex-v2 can not work with VIIPlusLoader

[flyfvdi]

badrax is working on the development of the update for a « STM32F415 » chip, until now, it was not possible...

Also, until now, it is claimed to use a « STM32F405 » for the reason given above.

Are you sure at your side you have a « STM32F415 » based cable ?

By the way, for now, like badrax say « Was playing around in vcds and everything seems to work just fine. Did not test any coding so don't know if that works yet ».

So, it would be better to wait another time for badrax making some tests about coding on recent platform, to be sure his work can benefit to others users with this kind of interface...

At your side, if you asking what version of loader you need to use, then, you probably have a « STM32F405 » chip based cable.

STM32F405VGT6 VCDS Hex-V2 firmware and VII PLus Loader can not work with STM32F415 VCDS Hex-V2

[flyfvdi]

STM32F405VGT6 VCDS Hex-V2 with LKT4106 encryption chip, STM32F415 VCDS Hex-V2 can not use STM32F405 firmware.

LKT4106 , STM32F405VGT6 and VII PLus Loader bundled each other.

[Stoatieweasel]

Hello all.. I have a STM32F405 cable. Installed VIIPlusLoader-08.021.03-EN connected cable to check if FW update was required.
InkedVIIPLUS_LI.jpg
I cannot find anyway to update FW. I'm using english 20.12 version of VCDS not requiring loader to start. I started VCDS with a 12v supply to cable and it is activated.. unlimited vins.
HEX-V2.jpg
My question is.. Is there an update available and how to update if so. Thanks very much for any help.

[badrax]

Hello all.. I have a STM32F405 cable. Installed VIIPlusLoader-08.021.03-EN connected cable to check if FW update was required.
InkedVIIPLUS_LI.jpg
I cannot find anyway to update FW. I'm using english 20.12 version of VCDS not requiring loader to start. I started VCDS with a 12v supply to cable and it is activated.. unlimited vins.
HEX-V2.jpg
My question is.. Is there an update available and how to update if so. Thanks very much for any help.

Its a bit confusing yes but in loader your press launch / or start vcds etc.
This will start a fw upgrade.
If you now use an older version of VIIPlus the same thing will happen but this time it will downgrade the fw.
Hope this helps


Sent from my iPhone using Tapatalk

[limengineer06]

hi,
I have my 2008 passat exculusive. Can I turn on mirror signals with American parks with vagcom?

[Stoatieweasel]

Thank you very much for quick reply.. upgraded. Simple.

[Ganja47]

updated my 415 cable today to run 20.12 just fine. Thanks again badrax
car battery is low so I can't test on car today and not sure how useful testing is on the 8N platform but I'll definitely report back after a full scan tomorrow

[obdcarsale]

updated my 415 cable today to run 20.12 just fine. Thanks again badrax
car battery is low so I can't test on car today and not sure how useful testing is on the 8N platform but I'll definitely report back after a full scan tomorrow

hi, how to update?

[crouchinggerbil]

hi, how to update?

By engaging your brain and looking through this thread especially this page

[miouser]

obdcarsale
did you provide cables to badrax?
as I understand you are selling these cables. so why should he provide a solution for someone to make money?

[Tomas005]

Can you share?

[tijgert]

Hi all, help request here.

My 2018 HEX-V2 clone from Ali works only with VCDS 18.2. Not with anything else.
I'd really like to use a more current version of VCDS though.
I use an older VCDSloader that came with this cable (it IS from 2018 after all), but I have up to v9.2 of the same type available should I need it.

The pics:




So the things I noticed are:
A. The bootloader is disabled (see 3rd pic). As far as I can find in this forum that means I cannot flash it from the PC? Is that correct?
B. The VCDSloader came with a ftd2xx.dll that I use that I didn't find with newer bootloaders...
C. Appears to be using an ARM chip.

So the final solution would be to just buy a new cable, but I'd rather try and hack this one to support newer VCDS's.
My question is thus: what are my options and how do I do it?