VAG-COM/VCDS EVERYTHING

**alexm1** · 8th October, 2015, 04:58 PM

Well if your has CAN then something is wrong with reflash, by the way I believe it is not rigth to indicate Can =ok if it is not conected to car, anyway never happened to indicate that thing to me.

**computerservice** · 8th October, 2015, 07:11 PM

Thank you Alex, I will try to connect it to the car asap and so I will tell...but if I do remember well when I used to make the test CAN was OK but maybe I'm remembering wrong!

Cheers

**Music73** · 9th October, 2015, 12:08 AM

You won't get can ok until it is connected to a canbus car... Being a 2006 Passat if it's the new shape(b6) then you should have can but if (b5) old shape then probably there will be no can...

Sent from my iPhone using Tapatalk

**computerservice** · 9th October, 2015, 09:39 AM

@Music73: It is a b6 version with CAN.
My clone cable was locked due to an unintentional internet access so I was forced to re-program the cable.
I have flashed FTDI and Atmega162 (fw+eeprom) and now I have fw 1.92 and vers 6 for 11.11.5-12.12.0 (eeprom 512 rl.hex).
I tried it with both software vcds version 11.11.5 and 12.12.0 simulating a connection giving 12v power to LM7805.
Everything seems to work fine except "CAN:NOT READY" warning message.

Port status: OK
Usb Library version: 03-02-04
Usb driver version: 02-08-14
Interface:found!
Type: Ross-Tech HEX-USB+CAN
Version:1.92
Copyright 2011 by Hex Microsystem Pty & Ross-Tech, LLC
Status:Ready
K1:OK
K2:OK
CAN: Not ready

Tried with both 11.11.5 and 12.12.0 and license status is fully activated (green color) and test is ok with K1,K2 except CAN:NOT READY, still not ready.
Should I maybe connect the interface to the car now to change it from NOT READY to OK?
I seem to remember that during the test (giving 12V+ power to the cable) everything was OK without connect it to the car (clearly, it was also OK when I connected it to the car).
As I said, I have a VW b6 car with CAN (made 2006).
Thanks for suggestions.
Cheers,
CoSe

**computerservice** · 9th October, 2015, 02:39 PM

Originally Posted by Music73

You won't get can ok until it is connected to a canbus car... Being a 2006 Passat if it's the new shape(b6) then you should have can but if (b5) old shape then probably there will be no can...
Sent from my iPhone using Tapatalk

to Music73 and Alexm1: you were both right mates, just tried to connect my re-flashed cable to my VW b6 car (with CAN) and now message is CAN: OK.

Port status: OK
Usb Library version: 03-02-04
Usb driver version: 02-08-14
Interface:found!
Type: Ross-Tech HEX-USB+CAN
Version:1.92
Copyright 2011 by Hex Microsystem Pty & Ross-Tech, LLC
Status:Ready
K1:OK
K2:OK
CAN:OK

I successfully tested my (ex 12.10 ver.) cable with both vcds v.11.11.5 (with long coding support) and 12.12.0: everything was perfect! I have also just done for the first time a complete "auto-scan", it never happened to do it completely before with previous beta ver. 12.10.3 (very bad release). Thanks mates for your suggestions!

PS: at the end of this story, it was "good" that RT had remotely locked my ex 12.10 cable... this has meant that I do improve to reprogram it and make it fully functional with better version as 11.11.5 and 12.12.0.
Greetings!

**computerservice** · 10th October, 2015, 12:03 PM

Hello again,
Does someone know why it is suggested to remove from the hardware pcb the resistence R51?
Mine still has got it on board and cable works fine.
Thanks guys in advance.

**alexm1** · 10th October, 2015, 12:19 PM

It is enougth to remove STC(if you have it); my first interface came with STC, and at my first update I removed that chip, in order to reflash Atmega. So you can leave R51 on pcb; if my cable works well with it on pcb, yours will do the same.

**computerservice** · 11th October, 2015, 11:14 AM

Originally Posted by alexm1

It is enougth to remove STC(if you have it); my first interface came with STC, and at my first update I removed that chip, in order to reflash Atmega. So you can leave R51 on pcb; if my cable works well with it on pcb, yours will do the same.

Hello Alexm1, I do not think mine got STC component (what was exactly this component, what's its function?).
You can give a look at my pcb on a previous post where I have attached pictures of the 2 sides at page 292 #4377: IC8 and transistor D7 are missing, R50 and R51 still present. Thanks.

**alexm1** · 11th October, 2015, 11:40 AM

IC8= STC , ok?
STC was "planted" there to protect Atmega, but this protection with STC was broken by RossT......etc.. It is useless to keep it on pcb, first of all does not protect Atmega and more than that you can not reflash with new dumps.

**zeljolaki** · 13th October, 2015, 08:18 PM

Hi all !
I wonder what the last free version of the firmware and software for interface with ft232BL chip?
Thanks!

**KenshinPT** · 1st November, 2015, 12:16 PM

Where can I buy a 15.7.1 VCDS with a good hardware, FTDI232BL to work with original software?
Thanks

**computerservice** · 2nd November, 2015, 06:26 PM

Hello mates, I have another chinese cable ver 12.12 that seems to work well and quickly with the included software 12.12.3a but honestly the impression "at first sight" of the pcb is that it is a bad product!
I would like to receive your impression/thoughts...
I attached here both sides of the pcb that genuinely seems very poor and built with great savings of all.
I immediately noticed, it does not have the voltage regulator LM7805 and I would not put in danger the ECU of my car while connected!
I want to include the LM7805 regulator for safety reason on this pcb circuit.. What do you think about it? if so, where it would be advisable to add it on the pcb?
I also noticed that there is no Atmel GAL / ATF16V8B IC that should serve to better support K-line (as K-line adaptations), right?
In addition, the specifications (serial model type/number) printed on ICs were canceled and I do not know if this cable comes out with an ATMEGA162 or any other EEPROM as NEC for example. Also FTDI label and number on IC is cancelled (but surely it should be a FT232RL). Only MCP numbers (on IC5 and IC6) are visible.
When I connect the vcds cable to the usb port on my netbook, the led turns on with a red light and when I make the test (the led turns from red to green and starts blinking). As result I have the attached odd message:
Status: Questionable
K1: short to ground
K2: short to ground
CAN: not ready
When I connect it to my car, then I get the following info
Status: Ready
K1: OK
k2: OK
CAN: OK
and everything starts to works fine.
Your suggestions and thoughts are welcome!
Thanks in advance.