VAG-COM/VCDS EVERYTHING

**crouchinggerbil** · 9th February, 2021, 05:41 PM

Originally Posted by jan4

no external 12v

Of course i wasnt watching for power

**ganobi** · 9th February, 2021, 07:34 PM

Originally Posted by nextor

Another guy (crouchinggerbil) said that it seems to work fine. Do you have it and it's not working as it should? If yes, what is not working well? Thanks!

Sorry, bad picture of type A, but if there is ATMEL MEGA162-16MU chip, that's fine.

**badrax** · 9th February, 2021, 11:56 PM

Tested my 415 upgraded to support VCDS 20.12 on my electric 2019 car

Code:

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
39-Right 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
D6-Light Ctrl Left 2 -- Status: OK 0000
D7-Light Ctrl Right 2 -- Status: OK 0000

Looks like it supported them all. I used auto-scan and holy shit it was fast compared to my older genuine HEX-CAN interface which took ages to complete scanning.

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

**BILAUTO** · 10th February, 2021, 02:56 AM

Hello badrax

Your vcds hexv2 work with loader or not?

Thks

**bg17aw** · 10th February, 2021, 08:50 AM

badrax, which loader version are you using (if any)?

some reported bugd and errors with latest 08.021.03

**flyfvdi** · 10th February, 2021, 10:12 AM

Originally Posted by bg17aw

badrax, which loader version are you using (if any)?

some reported bugd and errors with latest 08.021.03

please use VIIPlusLoader-08.021.03

**Creteil** · 10th February, 2021, 10:28 AM

Originally Posted by bg17aw

badrax, which loader version are you using (if any)?

some reported bugd and errors with latest 08.021.03

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.

**obdcarsale** · 10th February, 2021, 01:56 PM

Hello badrax, where can dwonload eeprom and flash, i have many STM32F415 cables

**badrax** · 10th February, 2021, 02:45 PM

Originally Posted by BILAUTO

Hello badrax

Your vcds hexv2 work with loader or not?

Thks

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.

**badrax** · 10th February, 2021, 02:53 PM

Originally Posted by bg17aw

badrax, which loader version are you using (if any)?

some reported bugd and errors with latest 08.021.03

I am not using a loader but I am using the firmware embedded in the loader version 08.021.01. That should be firmware version 01.02.05.

**badrax** · 10th February, 2021, 02:56 PM

Originally Posted by obdcarsale

Hello badrax, where can dwonload eeprom and flash, i have many STM32F415 cables

Nothing is yet available. My POC used the STM tool to flash over the debug port and I need to do some changes on the 415 bootloader for it to accept this new firmware.
This will most likely require a full reflash of the 415 and I don't have this code ready yet.

**badrax** · 10th February, 2021, 03:37 PM

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:

Code:

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):

Code:

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:

Code:

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:

Code:

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:

Code:

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?

**Toljanoss** · 11th February, 2021, 04:44 PM

Try to use both 20.4.1. If you can.

I had bad situation when I was trying to use vcds 18.2 loader with vag-com 17.8 (old eeprom). All information was different in coding and adaptation. Like another car.