VAG-COM/VCDS EVERYTHING

[liviudiaconu]

Open case, make 2 photos with both sides of PCB (good resolution) and post here.

[mircea13]

today will arrive and i will post some photos ;)

[networkers]

Hello all,

i found in my "electric treasure chest" an old VCDS clone. I don't know which software version belongs to the interface.
Maybe someone has an idea?

479748479754479755

[lovecoffee01]

Hello everyone, I'm new here. I have a cable that I bought from vag-diagnosics. It had full ross-tech 10.6.4. Long story short, I damaged the CD the software came on. Their website has the software but the zip file has a code. The company seems defunct so I can't get the code. Anyway, is there a way to use this with a different software? What are the steps? Where do I get the software. Any help would be appreciated.

[alexm1]

If do not find 10.6.4 on the internet, yout need to reflash your tool (if it has Atmega inside). For reflash you need: soldering station, USBASP programer, 12v psu, dumps from and the Tutorial.pdf file from this forum, after that instal new software coresponding to dumps and you are good to go.
Before you start this "journey" take a litlle time and read from the first page to have a clear picture in your mind before you proceed..

[pepeEL]

Hi all
Anyone know how i can read and save dump from cabel ? China clone has now all languages. I want do backup dump from this clone. How i can do it ? Anybody can write me all step by step pls....
Or maybe anybody has this dump...

[Domi]

Not possible, it is encrypted

[pepeEL]

But in ProgISP is available option read flash and eeprom...

[Domi]

Yes encrypted

[pepeEL]

ok thanks for help

[hid3]

today will arrive and i will post some photos ;)

So have you received your interface?
Where are the promised pics?

[Desmond0313]

Hi guys,

I bought a clone HEX V2 from AliExpress.

Yesterday it arrived. I connected it to my laptop, LED started blinking blue how it should. Did a cable test in VCDS that was on the disc they gave me, and it showed K1 and K2 line "Short to Ground", which I thought was a bit strange. Then I connected the cable to my 2005 Audi A4 2.0 TDI and tested again. Now it showed K1 line "Short to +12", K2 OK, CAN OK. I tried going into control modules, but as soon as I went to the control module selection screen, the dashboard on the car lit up like a christmas tree and every kind of errors came up (automatic headlight adjusment, brakes, PRNDS inverted then disappear, etc.). I can connect to the control modules (engine, auto trans, ABS) and they all have fault codes like "no communication" and such. I can read values from measuring blocks fine. I can start the engine, but until I select a control module the RPM gauge doesn't work and the engine is in limp mode (it barely reacts to any throttle input in neutral). If I select any control module then RPM gauge starts working and engine comes back to normal mode. As soon as I exit the control module it goes back to limp mode. I disconnected the interface, turned off the ignition, closed and opened the car, then tried starting it again and everything is back to normal, no errors, no lights, engine and gearbox work fine.

I disassembled the interface and it looks exactly the same as other HEX V2 knockoffs that I've seen in this thread. But one thing I found on the back side is that some soldering residue caused pin 8 and 16 to be connected to each other, and as I checked, pin 16 is +12V from car. Maybe this could be the issue why it says short to +12V? I removed the excess solder and will try it again soon. If that wasn't the problem, am I risking damage to my control modules with this cable? Because after restarting the car all the errors go away, but I'm still worried. I already applied for a refund anyway.

[tk500]

Why do you think it is "HEX V2" ?
The test result shows otherwise.

[Desmond0313]

Why do you think it is "HEX V2" ?
The test result shows otherwise.

You're right, it does say "HEX-USB+CAN" not "HEX V2"..... guess I got screwed over by them chinese... and I paid $25 for this piece of cr*p...
Tried it again with the removed excess solder but still no change.

480351

I applied for a refund for "product not as described" and "not functioning properly".

Could you guys recommend something that is tried and has a high chance of working? I want to do some basic stuff on my A4 B7 like adapting the multitronic clutch, turning off automatic door locks, etc...

Thanks!

[alexm1]

V2 or not, should work with software from the cd, in your case your reqouest for refund is legit.
However, can u share some pics? Just to see the ultimate miracle from chinese factory called V2...

[dorofteius]

I don't know if all of You experience the same thing.
But with the new loader for v 17.8 it is just shit.
I have lambda error on airbag and stuf like that.

[hid3]

Guys,

today I got a cable from a guy who doesn't use it as it has no VW/Audi car.
He told me that the condition of the cable is unknown, it might be spoiled because it was "updated" with bad version of V-C-D-S.

Anyway, I took apart and inside it looks like this:
https://ibb.co/fPX5p5
https://ibb.co/bK5EhQ
https://ibb.co/fz9wwk
https://ibb.co/coZkp5
https://ibb.co/dTBbwk

It has got the chips on with the following markings:

ATMEGA162V
8AU 0907

GAL16V8B

ATMEL912
93C56

--- on the backside >>>
FTDI
FT232BL

MCP2515

TJA1050

Also, it seems that someone has already been inside. As you can see in the pictures, it has got some chips already removed and some kind of spare wire is routed from ATMEL912/93C56 chip.

My questions:

Q1: Is it possible to upgrade this cable to something current? e.g. kolimer's dumps, etc
Q2: I suppose you need to solder wires directly to Atmega chip as there are no pins routed for programming, right?
Q3: Is the spare wire on the ATMEL912/93C56 chip required or should it be removed
Q4: Are there any other hardware modifications which need to be done before flashing/programming the Atmel?

Thanks a lot!

Hello,

today I finally flashed the above interface with Kolimer's V2 dumps (HW type 0x44). With latest \/(DS (17.8) it's crap... It shows as registered and activated, it was able to do the autoscan but... If I go to Instruments cluster Adaptation function, I get crap there... E.g. I select Staging and there's some kind of mileage (instead of values Active/Inactive). I tried a few more adaptation channels but it clearly displays wrong values in there!

Is 17.8 not compatible with the dumps? Which version should I use?

Thanks

[Desmond0313]

V2 or not, should work with software from the cd, in your case your reqouest for refund is legit.
However, can u share some pics? Just to see the ultimate miracle from chinese factory called V2...

Sure, here you go mate:

480467
480468
480469
480470

[tk500]

KL transceivers are made with cheap transistors. Good is case only.
Oddly, there are no prints "Versace".
Customers of this item will be welcome on the RT forum :rofl:

[ld6002001]

Hi guys,
Just joined as I have an issue with VCDS. I did have a working copy of VAG12.1 installed some time ago but it appears my anitvirus wiped the crack so it was rendered useless adn the original install CD was toast due to being snapped in my case! Although if anyone has a copy of the older 12.1 with crack I'd be happy to roll back and use the older version.

I have installed the 17.8 software and crack on my Lenovo Thinkpad X201 running Win7 64 which worked last time when VAGCOM12.1 was installed and for some reason when I connect to the cable via USB (standard RT driver installed) it sees the interface as an RT interface then when I plug it in to the OBD the green LED comes on but it then fails to recognise the port.

If anyone has any info, please send me a PM with suggestions.

By the way I don't think the OBD port on the Transporter is an issue as I can connect with my ELM327 and Torque Lite on the T5 and the TT.

[kolimer]

New VCDS Beta 17.10.0 (EN) was released. It's working with Loader_V2 and it seems that the problem with occasional Unregistered/Not Activated after long coding was fixed.

[zomikula]

This cable is the one to go for ?

http://www.obd2cartool.com/atmega162-vag-com-1780-cable-vagcom-178-full-englishfrench-interface-for-vw-audi-seat-skoda-p-1404

and this one the chinese are running code to allow all languages...

http://www.obd2cartool.com/vagcom-178-hex-can-usb-interface-vcds-1780-online-update-version-16-multilanguage-p-1263


which one of these 2 works out best?
Did read through the threads but saw the second cable and got abit confused lol



Thanks in advance

[hid3]

New VCDS Beta 17.10.0 (EN) was released. It's working with Loader_V2 and it seems that the problem with occasional Unregistered/Not Activated after long coding was fixed.

Hello,

what about strange values in Adaptation channels?
See my post here: http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3126190&viewfull=1#post3126190
It seems that more people reported the same issue...

Would be really nice to have a clue if it's our cables fault, or it's the dumps issue...

Thanks and thumbs up for good work.

[radsky]

Hello,

what about strange values in Adaptation channels?
See my post here: http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3126190&viewfull=1#post3126190
It seems that more people reported the same issue...

Would be really nice to have a clue if it's our cables fault, or it's the dumps issue...

Thanks and thumbs up for good work.

Wrong values on adaptation channels , but the worst is that you can erase coding for eq. ABS - Golf7 when you try to adjust steering angle - coding for ABS is erased :-(
Passat B6 - the same with abs.
It`s very dangerous to use at this moment.

[liviudiaconu]

@radsky: is about 17.8.0 or about 17.10.0 beta?

[radsky]

@radsky: is about 17.8.0 or about 17.10.0 beta?

all 17.x.x

tested on many interfaces

[FoxMulder]

Hello,

what about strange values in Adaptation channels?
See my post here: http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3126190&viewfull=1#post3126190
It seems that more people reported the same issue...

Would be really nice to have a clue if it's our cables fault, or it's the dumps issue...

Thanks and thumbs up for good work.




This cable is the one to go for ?

http://www.obd2cartool.com/atmega162-vag-com-1780-cable-vagcom-178-full-englishfrench-interface-for-vw-audi-seat-skoda-p-1404

and this one the chinese are running code to allow all languages...

http://www.obd2cartool.com/vagcom-178-hex-can-usb-interface-vcds-1780-online-update-version-16-multilanguage-p-1263


which one of these 2 works out best?
Did read through the threads but saw the second cable and got abit confused lol



Thanks in advance


This with autoupdate :
http://www.obd2cartool.com/index.php?main_page=product_info&products_id=1263



Gesendet mit Tapatalk

[kowaltom99]

New VCDS Beta 17.10.0 (EN) was released. It's working with Loader_V2 and it seems that the problem with occasional Unregistered/Not Activated after long coding was fixed.

Hi All
I've updated my RL cable via USB (I was lucky - my cable had a proper loader)
VCDS 17.8. and polish version 17.1.3 + Loader_V2, interface works ok.

But with 17.10.0 beta after the test of the interface there is info "CAN not ready" -
It is necessary to make procedure of reflashing the interface again using VCDS 17.10 beta (via USB)?

[hid3]

all 17.x.x

tested on many interfaces

Same here. Rhetorical question - is it only us (radsky and me) who are unlucky to have that issue? Guys, how about the rest? Could someone confirm that their interface is showing correct values in Adaptation? Or could shout that it's wrong too? Any input would be appreciated.

[Mslm2]

Bro thanks for uploading this package...
I read the info.pdf many times but i didnt understand that... HWtype shows me FW.1.96 / HW 0x46 / identif. Hex OEM... after i start EEPROM-> 0xFA24 -> Write -> Error ( Ft_SetBaudRate - Invalid baud rate / FT Write - General IO error / Usb Device error. After i try again i get this message (Not in Bootloader mode)
So i stop befor i make it worse.... is there a step by step instruction?
I would be very grateful if someone would help me!

[Mslm2]

483574
that is my interface...

[engycz]

This interface is China invention HW with ARM CPU (not with ATMEGA162 as original has). This interface will NEVER be supported by Kolimer's loader. It's not V2 as described by sellers, but china HW in V2 cover.

[Mslm2]

Thanks for reply,

[H2Deetoo]

Hi guys,


Today I found my Chinese clone VCDS cable which is still working with the supplied (cracked) VCDS 15.7.0 software.
I opened the cable and it looks very much like type HW 0x46.
(pin 34+35 of ATMega162 are not connected to the ATF16V8B)


I tried to read HW type using VAGCOM_HWType.exe, and hangs for a while and then says no reply.


What could be the cause?




Rgs H2Deetoo

[H2Deetoo]

I have the *exact* same hardware as PepeEL in this post:
http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3093197&viewfull=1#post3093197

[jakuza]

If you read thread careful you will find answer. Run 15.7 software, do test to unlock atmega, than run VAGCOM_HWType.exe
Instruction for flashing your interface you will find on this thread also. Need to remove stc and few other components, or just break connection from stc, I think picture is even in instructions you already have. Just read careful

BR

[testourii]

Hi guys,


Today I found my Chinese clone VCDS cable which is still working with the supplied (cracked) VCDS 15.7.0 software.
I opened the cable and it looks very much like type HW 0x46.
(pin 34+35 of ATMega162 are not connected to the ATF16V8B)


I tried to read HW type using VAGCOM_HWType.exe, and hangs for a while and then says no reply.


What could be the cause?




Rgs H2Deetoo
you have to plug vcds cable to 12V

[H2Deetoo]

I have done that, same problem.
But I'll check again to be 100% sure. Thanks.

[zecas]

Hi
somebody notice that vcds stop working??


solution is put date back to 1 November and work again (or use runasdate)
i am using Pt version 17.1.3


regards
ze

[iwoodcraft]

hi obd2cartool,
I bought this one from you, could you please tell me if this one supports reprogramming?


Vagcom 17.1.3 En / De/ Fr Full VAG COM 17.1.3 crack latest VCDS


http://www.obd2cartool.com/vagcom-1713-en-de-fr-full-vag-com-1713-crack-latest-vcds-1713-version-p-1336
Thank you for your replay in advance.

--- delete this post please!!!

[iwoodcraft]

most vag cable version hw with ATMEGA + FTDI chips support reprogramming like vag 11.11.3, vag 16.8.4, one kind need active 16.8.3 only support english version ,vag 17.1.0 . other like use original software (not office cable) it is used NEC project, we test different FT232 chips, there is no obvious difference. and Thanks kolimer and other friends!!

hi obd2cartool,
I bought this one from you, could you please tell me if this one supports reprogramming?
VAGCOM 17.1.3 EN / DE/ FR FULL VAG COM 17.1.3 CRACK LATEST VCDS 17.1.3 VERSION

http://www.obd2cartool.com/vagcom-17...version-p-1336 (http://www.obd2cartool.com/vagcom-1713-en-de-fr-full-vag-com-1713-crack-latest-vcds-1713-version-p-1336)
Thank you for your replay in advance.

[H2Deetoo]

Just tried it again and now it works:
FW Version : 1.94
HW Version : 0x46
Identification : ROSS-USA

*EDIT* ah I read that it has worked now because I started 15.7 sw to unlock ATMega. Thanks!


I will order an AVR programmer and try the upgrade!

[H2Deetoo]

I had a broken interface which was HW version 0x44 but had the so called "bootloader" inside.
So I could easily upgrade it using VAGCOM_EEWrite.exe :)

Would it be possible to insert this bootloader in a cable which doesn't have it?
Or does it require special hardware?


Thanks to all for releasing this stuff!


Rgs H2Deetoo

[networkers]

I tried to read HW type using VAGCOM_HWType.exe, and hangs for a while and then says no reply.


The Interface is connected to 12V or OBD during HWType.exe? Ups, to slow :02.47-tranquillity:

[alexroma85]

Hi guys i'm sorry to ask i now that probably somewere there is the answer but im not able to find on 353 pages ;) i have a china vag com 912 with FT232RL can i update it to the last version? do you have any stable version to suggest? And finally were i can found a tutorial to follow to update? all the link that i found are down pls help me, tks

[H2Deetoo]

Go a couple of pages back, there is a posting where 3 links are posted about V2 loader. Atleast 2 links are valid.
In the archive you can find latest firmware/eeprom files for the 2 supported hardware types.

You can check which hardware type you have using one of the tools in the archive, or post some pictures of your cable here (or compare it with posted pics).


Rgs H2Deetoo

[alexroma85]

485028485029

This is my cable vag 912 i check all the pages and i found a lot of way to update but i dont understand which is better and faster for my case can you help me?

[H2Deetoo]

Run HWtype tool and check which version you have. Remove STC chip before programming, no need to put it back.
Use some AVR programmer like USBASP to flash your avr (solder wires to it)

[hid3]

Why everyone is upgrading to the latest version?? Does it work properly for you? Valid adaptation channels, long codings, etc?

[H2Deetoo]

To be honest I haven't fully tested my upgraded cable yet, I only did a quick test to see if the cable was working again.

How can the problems you describe come from either the fw upgrade or the loader?
And what version of fw or loader or vcds is working for you then?

[H2Deetoo]

I just did a test with cluster on table and indeed when selecting adaptation channel staging i see a mileage value. This is with VCDS 17.8
But version 17.1.0 seems to work fine though.

[nobug]

Do these files work on a genuine RT cable?
I have a couple RT cables that were accidentally plugged into a laptop that had 17.1 clone software on it and online, now the cables will not work, must have blacklisted the serial numbers.
I have talked to RT and they advised to send them back for repair @ near the price of a new cable. I have been searching and reading a lot of these posts but seems it is mostly talking about
clones and making them work with the loader file.

Is there any way to restore the RT cable?

[H2Deetoo]

I don't know your exact problem because you didn't specify, but try to use VCDS 17.0 together with Kolimer's V2 loader (this will patch VCDS and disable some checks).
Perhaps this is enough to make use of your cable again.

If the AVR firmware or eeprom in the cable is really damaged then indeed you must fix this.
I guess you can use the files from Kolimer's package, because they are real dumps afaik.
(Please correct me if I'm stating something wrong ...)

[horstxx]

Hi,

this is my working 1.84FW 10.6.4 cable. I want to flash firmware to use newer VCDS.
HWtype tools says "no response", is it because the cable is not connected to the car?
Do I need USBASP or can I flash this one just connected via USB?

Thanks in advance.

Regards

485748
485749

[relax80]

Connect to USB 12v, and open VAGCOM_EEWrite as Admin.
I think that will help you.
Please let me know if it works.

[horstxx]

Hi, thanks for your reply.

But USB on the computer is only powered with 5V. You mean external 12V to the OBD connector (GND pin 5 and 12V pin 16?)?
Is it important which driver version is installed?

Thanks!

[H2Deetoo]

Yes, put 12v to the OBD connecter (or plug in car).
Not so important which FTDI driver is installed.

If you don't get a response, then start try your 10.6.4 software, and do the TEST.
Once your 10.6.4 software reports something about your cable, close it, and start again the EEWrite tool.
(this worked for my with my 15.7.0 clone, it needs to unlock communications with the ATMega it seems.)

[robertbeam26]

Does Chinese clones 908/912 works with 64bit OS? I found some drivers on the net but during instalation I've getting message that drivers are old, and need to be update. Do you have working drivers for 64bit OS?
Cheers.
THERE IS MANY CLONES THAT WORK WITH THIS ON 64 I AM USING WIN7 64 AND 3 DIFFERENT ONES the programs were altered by fantomel and his collection of software is spread across net ,google fantomel's vag collection and there will be all u need .

[H2Deetoo]

I've read and experienced with different cables already that they don't reply, unless you first start the software with came with it to unlock at the ATMega.
Can anybody explain what exactly is done to achieve this?
Is there some special command sent? Or some specific pattern on some output pin?


Regards,
H2Deetoo

[Majami]

Hey,
I downloaded version 17.10.0 EN and it does not work for me with Loader_v2. There is no communication with CAN vehicles. License is active but not connected to vehicles. Polish version 17.8.0 does not have encoding descriptions. Do you have any idea how to fix this or what is wrong? With version 17.8.0 EN all works well. My interface looks like this:
486218

[horstxx]

Hi,

one more question before I connect the cable to 12V and try to reflash: Is it required to remove the STC chip? I have not modified anything on the cable, yet.

Regards

[H2Deetoo]

@Majami, using 17.8.0 EN can you check an UDS cluster and go to Adaptation channels and choose "staging" channel and see what is read?
Several people get a "km" result and not "active" as it normally should be.

[H2Deetoo]

The STC will reflash the ATMega it seems, so you need to remove it if you plan to upgrade yourself. Otherwise the STC will reflash back to some old version.
You can simply remove 1 resistor (R50) but you can also simply remove all (STC+RESISTOR+TRANSISTOR).

[kolimer]

I can confirm that Beta 17.10.0 has some problems with CAN communication.

[H2Deetoo]

Also 17.8.0 gives problems for several different users at least (UDS cluster adaptation f.e.)

[obd2cartool]

Hi, friends
we have new ATMEGA162 HEX-V2, HEX V2 VCDS 17.8 full active cable For VW Audi Seat Skoda VAG HEX V2 support reprogramming, full chips : ATMEGA162 + FT232RQ + 9241 + 16V8B +ATA6561... Special thanks Kolimer for his support!!!
486381
486383

[horstxx]

The STC will reflash the ATMega it seems, so you need to remove it if you plan to upgrade yourself. Otherwise the STC will reflash back to some old version.
You can simply remove 1 resistor (R50) but you can also simply remove all (STC+RESISTOR+TRANSISTOR).

Thanks for the reply. In my case the PCB is not numbered and the resistors not numbered, which one is R50?

[H2Deetoo]

In that case I suggest to remove the STC completely, don't worry about the other components.

[H2Deetoo]

@kolimer:

I am working on VCDS protocol and I might have a small improvement to your tool EEType.
As you know sometime the AVR doesn't respond when requesting fw version.

It is mentioned here the cable must be "unlocked".
But in fact this is because cable is in some other mode (lets call it "canbus" mode).

You can send the following command to put the cable back in "command" mode :
-> 53 04 A0 F7
<- 4D 04 FE B7

After you sent this command you can request firmware version again :)

Also, for completeness, the following command will put the cable back in "canbus" mode:
-> 53 04 B0 E7
<- 4D 04 FE B7

Feel free to contact me to discuss this protocol if you're interested.


Rgs H2Deetoo

[alexm1]

Hi,
There is possible to run vcds software from PC (NR.1) with the cable plugged into another PC(NR.2) using a internet connection with a remote/vpn software like Teamviewer?

Same questions for flashing Atmega via usb in the same situation: interface connected on PC NR.1 and running software(VAGCOM_EEWRITE) from PC NR.2? Pc.s conected togheter via a wirelles network using Teamviewer or another software?

[T_ac_S]

Hi forum!

I'm looking into buying a VAG-COM cable for my 2016 Skoda Superb, but I dont want to spend $199 for a cable.

Since it looks like there are many bright heads here, is there a cable you can recommend? I'd like to use Ross Tech VAG-COM 17.8 - need a cable to which is compatible with this software.

[2xded]

Look post #5316 for example :)

[pacomasi]

hi i need help vcds loader blocks 91% in Windows 8.1,
i have uninstalled vcds loader and vcds 17.1.3 remains the same.:thumpdown:


487069

[relax80]

hi i need help vcds loader blocks 91% in Windows 8.1,
i have uninstalled vcds loader and vcds 17.1.3 remains the same.:thumpdown:


487069
Wrong theard, we talk about Kilomer Loader and not China garbage.
Forget Windows 8 and 8.1

[obd2cartool]

Hi, you could try use newer vcds loader v1.10 to try , EST software this period not work very well, waiting for update newer

[pacomasi]

Hi, you could try use newer vcds loader v1.10 to try , EST software this period not work very well, waiting for update newer

Where can I find vcds loader v1.10?:uncomfortableness:

[stonecoldro]

Hi guys,

So after successfully updating my first vcds cable (which had programmable headers), I'm now trying to update an even older one for 2009. While opening up the PCB I found out it is based on ftdi+atmega, it also seems to have a STC chip. Could I be able to use EE_Write to program it via USB so I won't need to solder cables to it ? It doesn't have programmable header pins like the more quality ones. Pics below..


487273

487272

Thanks

[H2Deetoo]

Just try with EEWrite. If it doesn't work it will report it. Then you have to solder those couple of wires :)

[stonecoldro]

@H2Deetoo (http://www.digital-kaos.co.uk/forums/member.php/432116-H2Deetoo), unfortunately EE_Write didn't work for me. I've tried it using your previous tips: install original vcds version and run "Test" to unlock Atmega, connected to the car's CAN port (for 12V), then ran the software. I get "No response" - please see screenshot below. I guess it's soldering on the bench for me now :).

487352

Does anyone has a schematic for it ? I found some tips on another forum that mentioned soldering directly to MCP2515, not sure though.

[hid3]

Hey, your board has got some empty slotds for pins marked with "G T R U" letters. I think you need to use multimeter to check if contacts on these slots point to correct connections...

In fact, it's OK to solder directly to MCP2515. It's even easier to do that, because Atmega legs are tiny. Personally I have done that

You need to solder (before doing that, check those empty slots if they point to these contacts):
RST - Atmega leg #4 (the only thing which needs to be soldered to it)
MOSI - MCP2515 leg #14
SCK - MCP2515 leg #13
MISO - MCP2515 leg #15

GND - anywhere to Ground (USB is fine, but again, check those empty slots, one of them should be ground for sure!)

You can safely skip soldering VCC as it's unneeded. Use +12 V external power on the OBD connector 16 pin (and #5 on ground) to power up the interface while programming.

Also, I would suggest soldering in a protection diode while you are in there.

BTW, your interface soldering quality looks disgusting.

[alexm1]

Hey, your board has got some empty slotds for pins marked with "G T R U" letters. I think you need to use multimeter to check if contacts on these slots point to correct connections...

In fact, it's OK to solder directly to MCP2515. It's even easier to do that, because Atmega legs are tiny. Personally I have done that

You need to solder (before doing that, check those empty slots if they point to these contacts):

BTW, your interface soldering quality looks disgusting.

Empty slots are not for programing Atmega. Soldering wires to MCP is the way to go, RES will got to Atmega.

[zoggermaster]

Hello
I also ordered the Hex V2 adapter from Ali. Unfortunately, the same problem with K1 short to + 12v. Has anyone solved the problem? Thank you

[obd2cartool]

Hi, your V2 I think cant fix, they not use Atmega chips

[zoggermaster]

I Think only the Transistors are damaged. I Have ordered new Transistors.

[hid3]

Transistors can bea easily soldered out and checked with multimeter. Have you already done that?

[zoggermaster]

Transistors exchanged, but problem persists. Then the problem seems to be somewhere else. All resistances are ok. So it can only be on the chip itself.

[xoom]

Maybe someone have software for this cable:
489119489120
Cable with that ARM chip ( HL008 )

In the begining it was with damaged FT232RL chip.. replaced that and tryed with supplied soft (16.8.3) but it shows not activated:
489123

It read serial from this cable but shows that interface not found:
489124

Anyone have more versions that work with that type hardware?

[jackie86]

Hi friends. Can someone help with a problem that i have..?
Problem: audi a4 2008 year use to have symphony3 media unit but someone changed to concert3.
Concert3 working, but cd doesnt work becouse car still see symphony unit that have cd 6cd..
When i do diagnose of 56-radio, car see symphony 3 unit. How to recode system to concert3??
Thank you in advance..


Sent from my iPhone using Tapatalk

[engycz]

Maybe someone have software for this cable:
489119489120
Cable with that ARM chip ( HL008 )

In the begining it was with damaged FT232RL chip.. replaced that and tryed with supplied soft (16.8.3) but it shows not activated:
489123

It read serial from this cable but shows that interface not found:
489124

Anyone have more versions that work with that type hardware?

Interfaces with ARM CPU will never be freely supported, because they have china firmware.

[xoom]

Interfaces with ARM CPU will never be freely supported, because they have china firmware.

I know they have custom FW.. im not asking about firmware. Im looking for Software.. just to try and if its not working just toss it :)

[ramyhossni]

490529490530

Hello All.

hope you all to be fine :)

i have VAG12.10 cable, it was working fine but after 2 yrs, it was suffering from low response and error msg with interface not found.

i reinstalled the VCDS 12.10.3 lite, but accidentally i connect my laptop to the internet while the cable plugged into USB.

Now i have new error msg

Port status: OK
USB Library Version: 03.01.19
SUB driver Version: 02.04.18
Interface: found!
Type: Ross-Tech HEX-USB
Status: Not plugged into Car!

i tried with another laptop but not working also.

PS. LED working fine, it became green once connect the cable into car.

Hope to get a solution for this issue other than replacing the cable as it's very expensive now for me now :( .

[alexm1]

Are very important fuse/lock bits?
I am asking this because if you flash Atmega via usb, fuse/lock bits will be not edited.... so it is ok to reflash via usb?

[ramyhossni]

Please, can anybody support me here ??
Thanks

[ramyhossni]

490529490530

Hello All.

hope you all to be fine :)

i have VAG12.10 cable, it was working fine but after 2 yrs, it was suffering from low response and error msg with interface not found.

i reinstalled the VCDS 12.10.3 lite, but accidentally i connect my laptop to the internet while the cable plugged into USB.

Now i have new error msg

Port status: OK
USB Library Version: 03.01.19
SUB driver Version: 02.04.18
Interface: found!
Type: Ross-Tech HEX-USB
Status: Not plugged into Car!

i tried with another laptop but not working also.

PS. LED working fine, it became green once connect the cable into car.

Hope to get a solution for this issue other than replacing the cable as it's very expensive now for me now :( .

Please waiting for your support

[H2Deetoo]

I would suggest to reflash it (because it got damaged while plugging software to internet).
Check the Kolimer V2 package for which you can find some links some pages back.

You can try to flash over USB using EEWrite tool most likely it isn't supported.
Then reflash with some AVR programmer like USBASP. All info and files is inside the Kolimer package.

[peetr]

Anyone here who know's if the new interface works with kolimers launcher?
http://www.obd2cartool.com/atmega-vag-hexv2-vag-178-usb-interface-vcds-hex-v2-full-actived-for-vw-audi-seat-skoda-p-1492
Of course they say that it works, but has anyone tested it? What's the effective difference between them, keeping in mind that the new one has a another CAN chip and a K-line chip 9241.
And the big question is: is the Si9241 a real one, or just a fake chip as in many new Delphi DS150e interfaces? I really don't know, but what I know is that the Si9241 chips are not gonna be produced anymore.

I've got the classic one http://www.obd2cartool.com/atmega162-vag-com-1780-cable-vagcom-178-full-englishfrench-interface-for-vw-audi-seat-skoda-p-1404 and it works with VCDS 17.8 just fine. As the interface has arrived I immediately flashed the firmware files from kolimers package via a USBASP interface and it works perfectly.
But maybe the new interface is better. Kolimer, what do you think?

No matter what, thank you for your work. Without you this wouldn't be possible!

[hid3]

The advertised "HEX-V2" is in fact the same classic interface with old AT162 chip, just with different/modern case and detachable cable. It's not the same as genuine HEX-V2, as it has got different newer chip.

You say that the old/classic interface works perfectly with 17.8 version.
Have you checked UDS cluster adaptation channels, Long Codings, etc? Do those functions work perfectly too?

[peetr]

I used long coding but nothing very big. I played just around and learned how it works in case I need it. I was able to change codings back and forth. Reading fault codes and accessing all modules always worked just fine.
One time I've had a strange behavior with a VW Golf 7. Everytime I connected to the UDS cluster and changed small things like "oil temp reading", the radio made for 3 seconds a high pitched noise. But besides that, I didn't used UDS cluster adaptation channels.

[H2Deetoo]

Try to go to staging adaptation channel and check what it shows. When faulty it shows "xx km" instead of active.

[hid3]

^--- Yep... If it shows anything other than what is expected, then it's very DANGEROUS to use such tool... One wrong value in some random adaptation channel might bring the module totally unusable.

[ramyhossni]

Dear H2Deetoo,
Many thanks for your reply, but it's the first time i will use this tools of reflashing
Please, just if you don't mind and have enough time i need your support to lead me to do it :tears_of_joy:
or please send me the page number that i can find the suitable steps

My VAG ver. is 12.10 and the interface pics below.

thanks again for your support.

.491731
491732

[H2Deetoo]

Just go some pages back and read, all info is there.

[peetr]

Today I've tried my interface with a Seat Ibiza 6L and as much as I saw, the values were plausible. Service reset should also work, and I was able to set the coding on the power steering module back and forth without any problem.
The 6L Ibiza just hasn't that much capability.. just a few basic things, but nothing like indicator staging. Yesterday I've read the fault codes from a A6 2.5TDI V6 automatic and this worked just fine. But I know, the problem is in the long coding, not in reading fault codes.
I'm gonna try it with a another Audi A6 2.7T and maybe with a friends Golf 7, but it can take some time till I can test it.
But as long as I just read and don't write anything, I think it should be safe to use.
My interface is a HW 0x46 one

[alexm1]

Which vers. did you use?
17.8 , 17.8.1 or 17.8.10 beta?

[kamine22]

No reason for that at all, but I do attach dumps (hex for flash, eep for eeprom) and fuses screen shots for both 0x44 and 0x46 versions.
thanx ....

[peetr]

alexm1, I've used version 17.8. Maybe I'm gonna try a newer version, but as long as everything works I'll stick to 17.8

[liviudiaconu]

17.8.1 en-ro: No adaptations, no bits on Long coding helper" The same as in 17.8.0 from august and 17.10 beta.

[magadan]

17.8.1 en-ro: No adaptations, no bits on Long coding helper" The same as in 17.8.0 from august and 17.10 beta.
I wrote about this problem earlier. :)

....You will wait for the fact that substitution of public key, will become impossible, by means of a simple loader, it is necessary to do still something.

[kolimer]

I can confirm that long coding is not working as expected in 17.8.1 (No correct items are shown for bytes). It's working in 17.1.3 and 17.8.0.

[alexm1]

About 17.1.3 - will work with v2 loader +dumps? Or you can help with new loader /dumps?

[H2Deetoo]

I can confirm: 17.1.3 - will work with v2 loader +dumps.

[alexm1]

Can you share download link for 17.1.3 software? Thanks

[magadan]

I can confirm that long coding is not working as expected in 17.8.0 and 17.8.1 (No correct items are shown for bytes). It's working in 17.1.3.
If created the correct public key, and then calculated the new digital signature for atmega EEPOM, then long coding will work.
But there is also other way until it was forbidden by Ross.

[hid3]

One question. Currently I have and use 17.1.0, I want to try out 17.1.3 and see if Long coding and UDS Adaptation work fine.
Should I reflash the atmega with the dumps freshly or can I just reinstall the software to 17.1.3?

Thank you

[Mario6]

Can you share download link for 17.1.3 software? Thanks

Hi. Here you have a link to VCDS 17.1.3 En. (Slow download)

https://ulozto.net/!Jd4UHbfBjzIA/vcds-release-17-1-3-installer-rar#_ga=2.50073888.783336334.1513870187-473860178.1513870186


I fixed my broken VCDS 16.8.3En. Thanks to KOLIMER.
I have three types of activators. One is Kolimers (V2) and 2 Chinese. And they all work correctly. I use VCDS 17.1.3 PL and everything works. I tried VCDS 17.8.0 PL (Kolimer activator) but I did not notice if everything works. (long coding).

[hid3]

I tried VCDS 17.8.0 PL (Kolimer activator) but I did not notice if everything works. (long coding).

In order to verify that the cable is fully working and safe, you need to try UDS adaptation channel, which is known to have a certain value.

E.g. I test on Instruments cluster on 6 Golf, check Staging if it's Activve or Not Active. If you see some nonsense in such channel, means it doesn't work correctly and such interface is DANGEROUS.

Meanwhile, Long Codings may work (or at least you won't notice that it works incorrectly, so relying only on that is not a guarantee

[Mario6]

Probably you are right. I checked the cable only on VW Passat B6 2006 and B5 2004(runs slower on K lines). In my old VW I do not have UDS so I will not check it out.

[vaicekas]

In order to verify that the cable is fully working and safe, you need to try UDS adaptation channel, which is known to have a certain value.

E.g. I test on Instruments cluster on 6 Golf, check Staging if it's Activve or Not Active. If you see some nonsense in such channel, means it doesn't work correctly and such interface is DANGEROUS.

Meanwhile, Long Codings may work (or at least you won't notice that it works incorrectly, so relying only on that is not a guarantee

Stagging is a bad example for checking the interface. Because only in some of the dashes these options are allowed. In order to activate Stagging it is necessary to adjust the EEPROM dump of the speedometer. There is no way to do this with vcds.
My Passat B7 Speedometer did not have the ability to turn on Stagging with VCDS. I removed the speedometer, dumped the eeprom, corrected several bits, wrote back, and now I can activate or deactivate Stagging with VCDS

[hid3]

Stagging is a bad example for checking the interface. Because only in some of the dashes these options are allowed. In order to activate Stagging it is necessary to adjust the EEPROM dump of the speedometer. There is no way to do this with vcds.
My Passat B7 Speedometer did not have the ability to turn on Stagging with VCDS. I removed the speedometer, dumped the eeprom, corrected several bits, wrote back, and now I can activate or deactivate Stagging with VCDS

Yeah, I know Staging is not available on all of them, but I gave it as an example of a thing, where you know expected values: Active / Not Active. if you see something else there, you know it's wrong. On your cluster, you can pick up *any* adaptation, which value you approx. know. It might be time till service, mileage since service, etc.. - it's your car and you know it.

It looks like you really wanted to boast that you activated Staging on your car. On my car (Golf 6) it alsoo was not available, as it's only available on GTI/GTD/R versions. But instead of taking out the cluster, I had the EEPROM dumped via OBD port, amended the necessary bytes and pushed it back. In addition to that, I also enabled Volume To Be Replenished in menu and true coolant temperature indication

[hid3]

If created the correct public key, and then calculated the new digital signature for atmega EEPOM, then long coding will work.
But there is also other way until it was forbidden by Ross.

So you mean that R0$$ made some amendments in versions later than 17.1.3 so that it stopped working correctly?

Do we have a list of known-good working versions? Or should we make one? I can confirm that 17.1.0 and 17.1.3 are working absolutely correctly on 0x44 HW. Others feel free to add

[Majami]

Will anyone write a new loader to work properly with version 17.8.1 EN/PL? :tears_of_joy:

[magadan]

So you mean that R0$$ made some amendments in versions later than 17.1.3 so that it stopped working correctly?
Ross entered one more check of bytes checksum of public key into 17.8.0 versions of the program.

[hid3]

Oh, I see, that explains the case then!

Seriously, I think we need to stop using the terms such as \/(DS, R0$$ and etc. This gets indexed by google, this thread comes up easily in a simple search, and no doubt R0$$ reads this thread, sees what we are doing and tries to implement some blockage for this in order to make this happen harder.

Also, a great idea would be to make this thread visible only for members having over certain amoount of posts, e.g. 30 or so. This would prevent people who only sneak in the forums from reading the contents...

[magadan]

...a great idea would be to make this thread visible only for members having over certain amoount of posts, e.g. 30 or so. This would prevent people who only sneak in the forums from reading the contents...
Restrictions will not prevent Ross to read this subject. He can be the moderator of this subject. Or for example I or you can be Ross actually. :) :) :)

[hid3]

To be realistic, doubt that one of them are mods here. Also, doubt that their account (if they even have one) has got posts >30. They are busy guys which get paid for actual work done for the company and not for surfing/posting in some 3rd party forums... If they are browsing as guests and suddenly would lose such possibility, that would make it just a bit more difficult and time consuming to get an account with let's say >30 posts. And if they get one, then they'd have to share a single one accross multiple people just to read some stuff.

Anyway, that was just an idea on how to limit the visibility from random people and search engines

[BWF]

If created the correct public key, and then calculated the new digital signature for atmega EEPOM, then long coding will work.
But there is also other way until it was forbidden by Ross.I see that you have a solution for vcds 17.8 that solves the longcoding failure. Can you tell me more? Thank you

Enviado desde mi Redmi 3 mediante Tapatalk

[Wene001]

Hi to all the VCDS Gurus here!
Wish you a happy christmas evening.
i have read parts of this thread and my head is exploding :-)
In the moment i´m using a China VCDS interface(form the PCB is think i`ve learned this is HW1 with FTD32BL)
Becaus e BL, i have to use a loader? Right?
its labeled with VCDS 805.1
What is the newest version of VCDS if i try to flash the interface.
I found Tutorial.pdf and would replace the parallel port thing with USB-ASP Programmer.
Can you give me a hint which dump i should use and which VCDS Version to use?
is 11.11.5 the latest i can use (longcoding needed) or can i use newer versions also?!?
Best would be a version in German
494788
494789

Thanks for help and Happy Christmas!
Wene

[xoom]

Hi to all the VCDS Gurus here!
Wish you a happy christmas evening.
i have read parts of this thread and my head is exploding :-)
In the moment i´m using a China VCDS interface(form the PCB is think i`ve learned this is HW1 with FTD32BL)
Becaus e BL, i have to use a loader? Right?
its labeled with VCDS 805.1
What is the newest version of VCDS if i try to flash the interface.
I found Tutorial.pdf and would replace the parallel port thing with USB-ASP Programmer.
Can you give me a hint which dump i should use and which VCDS Version to use?
is 11.11.5 the latest i can use (longcoding needed) or can i use newer versions also?!?
Best would be a version in German
494788
494789

Thanks for help and Happy Christmas!
Wene

Becouse you have FT232BL you DONT have to use loader (becouse that FT232BL dont have hardcoded uniq id) but as for kolimer's loader.. yes.. its needed to be used..
but if you want only use not cracked 11.11 version then NO no need any loader or crack .. just flash your atmega162 with 11.11 dumps .. and also you need to remove that STC chip :)

[hid3]

Hi!

Your interface is exactly the same I had:
https://ibb.co/fPX5p5
https://ibb.co/bK5EhQ
https://ibb.co/fz9wwk
https://ibb.co/coZkp5
https://ibb.co/dTBbwk

1. You will need to solder out the STC chip completely
2. You will need to solder additional wires for programming as the interface does not have one
3. I would strongly suggest soldering in a protective diode for OBD 16 pin
4. Your HW type is 0x44 and the chip is FT232BL
5. Afterwards, you should clear the AT chip and program the Kolimer's dump
6. Use 17.1.3 version w/Loader

[flavyus1987]

Working without problems in adapting or LC.Was tested on passat b6 1.9&2.0 &b5.5 1.9tdi.
I use 2 hardware with BM & RL.
All it is perfect.

[BWF]

I have a problem with vcds 17.8 and longcoding.
There are solution for this?

Enviado desde mi Redmi 3 mediante Tapatalk

[hid3]

Again, long coding is NOT enough to confirm working properly.
Also, your Passats are way too old, they don't have UDS protocol.

[flavyus1987]

For the moment it is enough.for me it is working perfect.I use it only for my car, and ocasionally for others.
I have vcds 17.3 pack, and if it 's necessary i'll do downgrade without problems.

[1 6 D]

Hi, i,m back in recovering VCDS interfaces, I use kolimer loader like few months ago but when I try every option there is always problem with long coding and *.rod files in 17.1.3. One is HW44 and secong HW46, both on FTDI RL. What could I do wrong?

I can see that extreme burner dosen't make lock bit from FF to 3F, maybe it's why it works uncorrect?

[Wene001]

Thanks to hid3 and xoom!

Ive soldered programming pins, removed STC Chip
Used the command avrdude -p m162 -c usbasp -e -U flash:w:Flash1.96_HW_0x44.bin:r -U eeprom:w:eepromavr.bin:r -U lock:w:0x3f:m -U efuse:w:0xf9:m -U hfuse:w:0xdc:m -U lfuse:w:0xcd:m
to flash eeprom and flash. Installed cracked 17.1.3 in german.
Looks fine so far, but i get many communication errors while usding vcds on my Audi A4 8K.

What is the .epl file for?
Do i need this Mprog3,5 software ?!? or is this only a other way for programming the atmega?

Any hints?

Thx Wene

[alexm1]

Did you checked : About -License? Valid/Registered or ?

[H2Deetoo]

Don't use a cracked version.
Use original version and V2 loader from kolimer, should give better results.

[hid3]

Thanks to hid3 and xoom!

Ive soldered programming pins, removed STC Chip
Used the command avrdude -p m162 -c usbasp -e -U flash:w:Flash1.96_HW_0x44.bin:r -U eeprom:w:eepromavr.bin:r -U lock:w:0x3f:m -U efuse:w:0xf9:m -U hfuse:w:0xdc:m -U lfuse:w:0xcd:m
to flash eeprom and flash. Installed cracked 17.1.3 in german.
Looks fine so far, but i get many communication errors while usding vcds on my Audi A4 8K.

What is the .epl file for?
Do i need this Mprog3,5 software ?!? or is this only a other way for programming the atmega?

Any hints?

Thx Wene

As already mentioned before, don't use cracked version, use kolimer's dumps and 17.1.3 original german version. Let me know if you need this file.
I guess you are referring to .ept file, not .epl. This one is required for programming FTDI. If the cable is detected correctly and working, you don't need this.

[BWF]

As already mentioned before, don't use cracked version, use kolimer's dumps and 17.1.3 original german version. Let me know if you need this file.
I guess you are referring to .ept file, not .epl. This one is required for programming FTDI. If the cable is detected correctly and working, you don't need this.I need this file too, I have problems .
Can you pass me this file?
Thanks

Enviado desde mi Redmi 3 mediante Tapatalk

[Wene001]

As already mentioned before, don't use cracked version, use kolimer's dumps and 17.1.3 original german version. Let me know if you need this file.
I guess you are referring to .ept file, not .epl. This one is required for programming FTDI. If the cable is detected correctly and working, you don't need this.

You are right man, i mean .ept
Would be great if anyone has a link to official 17.1.3 in german

THanks

[H2Deetoo]

https://mega.nz/#!bpgH0LIB!NpJ3Ajhwe_3JukBm7Hr9LXH-6L50U2aDlF-hSaGkvSQ

[BWF]

someone can share the dump of kolimer's. thank you very much

Enviado desde mi Redmi 3 mediante Tapatalk

[Mario6]

Hi
Here you have VCDS 16.8.3, 17.1.2, 17.1.3, 17.8.0 in different language versions.


https://yadi.sk/d/kwoAv_pu3LkTV8


Kolimer v2


https://mega.nz/#!sHR3XQ5K!Xr8XWZjzq2l5SYO-PRKpoMzX2v81NlsdzeH5gOYPPl4

This is also cool. Everything in one place.


http://obd2-diag.blogspot.com/2017/08/vcds-178-download-free-with-user-manual.html

[BWF]

I have problems with long coding and version 17.8.
The long coding is not the correct one, and the car is badly configured.
Does anyone have a solution for this error?


Everything else works well

[alexm1]

For 17.8 long cod. it is not working as it should .... use v2 dump+ loader for 17.8 and use 17.1.3 software.

[H2Deetoo]

Latest working version with V2 loader is 17.1.3

[hid3]

I have noticed that for the same version, same language, same release the installer files are slightly different in size, and of course MD5 and SHA1 sums do not match. The files are downloaded at different time from different places but are supposed to be "original" and not modified ones.

Any ideas why is it so? Is it something what's supposed to be or am I facing corrupted/altered/modified installer files?

[Wene001]

Thanks again for help
Original 17.1.3 now working with v2 loader (kolimer)

One question ... why should i put protection diode on 12V power rail (Pin 16 OBD 2) ?

[Wene001]

I have noticed that for the same version, same language, same release the installer files are slightly different in size, and of course MD5 and SHA1 sums do not match. The files are downloaded at different time from different places but are supposed to be "original" and not modified ones.

Any ideas why is it so? Is it something what's supposed to be or am I facing corrupted/altered/modified installer files?

I`ve noticed that the Installation Splash Screens are different...maybe there are different "branded" versions out there?

Edit:
Info from an other German forum:


PCI (PCI Diagnosetechnik), AIB (Auto-Intern), MFT (Milewski Fahrzeugtechnik) und RKS (Kaufmann Diagnosesysteme) sind die 4 deutschsprachigen Vertriebspartner deren Versionen dem jeweils offiziellen Stand entsprechen. All diese Versionen basieren auf der DRV (Deutsche ReferenzVersion) und wurden ggf. leicht ergänzt (z.B. mit weiteren Plugins oder auch der Funktion Telediagnose).



Die DRV Versionen sind in der Regel etwas aktueller da wir sie nutzen um schnell auf Neuerungen bzw. Änderungen seitens VW/Audi reagieren zu können. Im Normalfall sollte für den Großteil der Kunden die jeweils aktuelle Version seines Vertriebspartners ausreichen, wer jedoch ein sehr neues Fahrzeuge besitzt oder regelmäßig an solchen arbeitet ist meist mit der jeweils aktuellsten DRV besser dran. Ebenso eine Ausnahme bilden die DRV Versionen wenn es um Vorabversionen geht denn Betaversionen werden von Haus aus nicht übersetzt, auch hier ist der deutsche Markt mit der Referenzversion etwas im Vorteil denn es ist der einzige Markt in welchem übersetzte Betaversionen angeboten werden.

[hid3]

Yeah, with German version it's clear that there are several partners/distributors/retailers etc which publish their own versions. But.. Why do English version installers differ in size? I suspect they were downloaded at different times but the version/release number is the same. So I would expect the SHA1/MD5 and size to be identical too... That's a mystery

[alexm1]

An user from a different forum told me that 17.8.0 was released initially In July 2017 and then was re-posted in August, maybe at that point something changed...size, information, data etc.

[hid3]

This applies for almost every release... e.g. the same 17.1.3. I have two installers with slightly different size

[JBeltran8]

Good Morning, I to seek some help. I just purchased a 2007 Jetta 2.5. The guy who sold me the car gave me a laptop along with the USB cable. When i try connecting it keeps saying Can not ready. Then no response from controller. Can i make this work with my car? or what adapter should i buy. I have the ABS and Airbag light on and want to fix the car.

495571495572

[alexm1]

It might be with no License....or you need to launch vcds after you change calendar date..but first tell us what version of vcds it is installed on your laptop?

[hid3]

The interface is decent quality but not perfect, I'd say. It can be reflashed to use the stuff which is floating around here.
In order to accomplish that, you need to to the following:

-Solder additional wires for programming as the interface does not have the dedicated pins for that;
-I would suggest solder in a diode for OBD 16 pin for protection;
-Your HW type is 0x44 and the chip is FT232BL. Clear it and program the dumps along with correct fuse/lock bits;
-Use 17.1.3 version w/Loader and you should be good

[xoom]

Good Morning, I to seek some help. I just purchased a 2007 Jetta 2.5. The guy who sold me the car gave me a laptop along with the USB cable. When i try connecting it keeps saying Can not ready. Then no response from controller. Can i make this work with my car? or what adapter should i buy. I have the ABS and Airbag light on and want to fix the car.

495571495572
First of all solder USB wires in place ;)

[Wene001]

@hid3
Why do you recommend soldering the diode to pin 16 ?
Anyone had a problem without such a diode ?!?

just for my understanding....

[JBeltran8]

Xoom. That was the first thing i did.

[hid3]

@hid3
Why do you recommend soldering the diode to pin 16 ?
Anyone had a problem without such a diode ?!?

just for my understanding....

Short circuit protection for "just in case".
No, you won't haveany problems without it, unless something goes wrong.
But.. High quality interfaces have it. It costs about $0.05, so why not to add it for peace of mind?

[liviudiaconu]

[...] I just purchased a 2007 Jetta 2.5. [...]
When i try connecting it keeps saying Can not ready. [...]
I have the ABS and Airbag light on and want to fix the car.


1. I am not sure but your car is CAN Ready? Tried to make test on another car with CAN Ready?
If yes and in your program in "About" screen having "License status: Valid/Activated", MCP 2551 and/or additional components can be damaged.
But not always. Tell us-
|
V
2. As our coleagues asked you, what version of program using?
3. ABS and Airbag are connected on K Line as i remember.

[hid3]

This is Mk5 Jetta, so it is CAN-based.

[xoom]

The Diode on 16 pin is good for 2x2 adapter.. you can easy mix + and - becouse those adapters are like rubber and you can plug it wrong way.. :)

[mattock808]

hello everyone,
i have old cable 12.12 with NEC D79F8513A, as I read here in forum no can with NEC update .....

i muss buy new cable, there are two versions available NEC+RT232RQ or ATMEGA162+16V8B+FT232RQ ?

which version is better?

thanks

[hid3]

Re-read your own post once again and you will find the answer

[mattock808]

i can buy with atmega, or buyer write me : that version ATMEGA162+16V8+FT232RQ is not stable, some customer said can not do some of the functions

[kolimer]

Christmas present for everyone. New loader V3 working with 17.8.1 (thx to magadan).
It is necessary to modify the EEPROM. Either by programmer or by VAGCOM_EEWrite if previous version of the loader was used.

Enjoy
... Kolimer ...

Edited:
Unpublished the loader because it is not 100%. Stay tuned.

[xoom]

False alarm :)

[flavyus1987]

False alarm :)

About what?

[xoom]

too much versions :) compared same files :))

[xoom]

495787
Still looks not right...

[hid3]

Kolimer, others,

I confirm that the V3 stuff ant 17.8.1 DOES NOT WORK CORRECTLY.
Checked on a car with CAN/UDS protocols.
I wouldn't suggest anyone use it at this stage.

[liviudiaconu]

Christmas present for everyone. New loader V3 working with 17.8.1 (thx to magadan).
It is necessary to modify the EEPROM. Either by programmer or by VAGCOM_EEWrite if previous version of the loader was used.

[..]

Vagcom_EEWrite is the same like previous or new version too?

[xoom]

There is different eeprom content:

Photo (https://image.ibb.co/kLfS9w/eep_diff.png)

[kolimer]

I can confirm that adaptation channel items are shifted by one in version 17.8.0 and up. Anybody to compare with genuine interface?

[H2Deetoo]

First of all thanks kolimer and magadan for releasing this!
I just tested with my clone 0x46 interface and I can see the same behaviour: atleast some channels are shifted by 1.

[BWF]

The problem of long coding is solved?
What is the problem with V3?

[hid3]

The problem of long coding is solved?
What is the problem with V3?


Issue is described here:
http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3126190&viewfull=1#post3126190
and here:
http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3135230&viewfull=1#post3135230

Originally in the posts it refers to V2 but V3 has got the same issues.

[Wene001]

tomorrow i have eventually the chance to test a genuine Hardware with adaption channel issue, so we can be sure the problem doesnt exist with genuine hardware.
I´m a VCDS Newbie.
Can someone explain what to test in detail?

Thanks

[mikroel]

@Kolimer
Sorry for my question but what exactly are differences between V2 and V3?


Sent from my iPhone using Tapatalk

[Wene001]

The Diode on 16 pin is good for 2x2 adapter.. you can easy mix + and - becouse those adapters are like rubber and you can plug it wrong way.. :)

Aah thanks, that makes sense to have a reverse polarity protection....

[tr3ce13]

17.1.3 works with kolimer's loader v1 v2 or v3?

[H2Deetoo]

17.1.3 works OK with loader V2.

[kolimer]

New loader V4 working with 17.8.1 available. Needed to rewrite avr eeprom. One multilingual eeprom is not possible anymore. Use VAGCOM_EEWriteLang to write eeprom of your choice.
http://ge.tt/5RryFzn2
https://www.sendspace.com/file/d9i4mo

Kolimer

[BWF]

Is it possible to use it in Spanish?
I do not understand that a multilingual eeprom is not possible
Thank you very much for the contribution of the V4 loader

[kolimer]

Is it possible to use it in Spanish?
I do not understand that a multilingual eeprom is not possible
Thank you very much for the contribution of the V4 loader

Yes. Read next sentence : "Use VAGCOM_EEWriteLang to write eeprom of your choice"

[kenzoo]

Thanks Kolimer for your great job!

If you have working e.g. 17.1.3 it is easy to update to 17.8.1

[As VAGCOM_EEWriteLang.exe is detecting HW Type you can start from point 4]

1. Check your HW type first with VAGCOM_HWType.exe to be sure about HW 0x44 or 0x46 (connect 12V to the cable)
2. then extract HW you want form eepromavr_AllLang.zip (e.g. 0x46 AKP = PL) to seperate folder (e.g. eeprom_update)
3. then to the same folder (eeprom_update) copy VAGCOM_EEWriteLang.exe
4. then run VAGCOM_EEWriteLang.exe (in the same folder as eeproms), choose language you want (e.g. for AKP its polish), connect cable to USB and 12V and push WRITE, when done klick OK
5. then install VCDS 17.8.1 in your language (e.g. AKP from vcds.pl) copy VCDSLoader.exe to main folder of VCDS and run it (loader)
6. do the TEST of the cable (still connected to 12V) it will ask for update FW from 1.95 to 1.96. Do it. After update this is done.
After another TEST you will see:
497117

...and it is good time to connect to the car :)

PS. I noticed it is better to use power supply like 12V 500mA, when I used 100mA I had issues with proper programming and TEST cable.

[mikroel]

New loader V4 working with 17.8.1 available. Needed to rewrite avr eeprom. One multilingual eeprom is not possible anymore. Use VAGCOM_EEWriteLang to write eeprom of your choice.
http://ge.tt/5RryFzn2
https://www.sendspace.com/file/d9i4mo

Kolimer
Thank you for your hard work Kolimer.[emoji106]
The problems with coding is solved with this ver.4?


Sent from my iPhone using Tapatalk

[mxsking]

New loader V4 working with 17.8.1 available. Needed to rewrite avr eeprom. One multilingual eeprom is not possible anymore. Use VAGCOM_EEWriteLang to write eeprom of your choice.
http://ge.tt/5RryFzn2
https://www.sendspace.com/file/d9i4mo

Kolimer

Chinese version 17.8.0,how do you crack the online verification?
thanks for you work
Attached file download address
https://yadi.sk/d/YFSWG60-3REHkW

[1 6 D]

I tried this V4 and on my laptop with win7 x64 still is problem with correct finding rod file and with long coding, I tried to install VCDS as 32 bit and as 64bit version.

[H2Deetoo]

@16D, what VCDS version did you try?

[hid3]

Also, what car and which module were you trying where it caused problem?

[Majami]

For me, the v4 charger works well, I checked the long coding and it looks like it works well.

[1 6 D]

I tried vcds 17.8.1 Release in english, modules which I test on bench are 7N0907530AK and cluster 1K8920875D.

Same interface but on win7 x32 works perfect with english version.

[xadamek]

Hi, I have a question whether in the original version of the vcds interface, for example, Polish akp can be used with vcds in English.

[hid3]

Yes, original VCDS interface can be used in 2 languages - the custom one and English.

[KayLastOS]

Thanks Kolimer and everyone. I've updated to 17.8.1 and interface is working.
I should always start VCDS with the loader or only the first time?

LE: I'm trying to connect on bench to 18-Aux. Heat to recode one board but it doesn't connect. On the car CAN connection is working and I can access the module, but not on the bench. Can I do anything to make it work on bench?

[flavyus1987]

Maybe you need corect pinout for your module.
I tested on airbag kline and passat b6 with LC.
All working for the moment.
Thx kolimer!

[vaicekas]

LE: I'm trying to connect on bench to 18-Aux. Heat to recode one board but it doesn't connect. On the car CAN connection is working and I can access the module, but not on the bench. Can I do anything to make it work on bench?

You will not be able to run an aux. heater without a car. Only when connected in a car.

[KayLastOS]

Maybe you need corect pinout for your module.
I tested on airbag kline and passat b6 with LC.
All working for the moment.
Thx kolimer!
kline is working on bench. I will need a CAN gateway in the setup in order to work. I will try to get one from scrap yard.

You will not be able to run an aux. heater without a car. Only when connected in a car.
I am able to run it without the car with webasto software, but is not what I'm looking for. I want to code few things on the board which webasto software can't do.

[H2Deetoo]

Make a specific module run on bench can be tricky.
You need to make sure everything is in order for the module to work properly:
- cabling (power, some other signals perhaps need to be present)
- gateway can sometimes be needed (specially if your module uses a 100kbps canbus)
- does the tool (VCDS) use the correct CANID? Sometimes it doesn't (like with UDS cluster) but gets corrected by gateway


Rgs H2Deetoo

[kolimer]

Announcing new loader V5.
http://ge.tt/2h4pV2o2
https://www.sendspace.com/file/2sva6i

[networkers]

Hello kolimer,


Announcing new loader V5.


thanks for your work. i appreciate it very much!

As far as i see, v4 is working well. I checked the german (DRV) version.

What ist the difference between v4 and v5? I guess i need to reflash the Interface?

[H2Deetoo]

Yes you need to reflash (only eeprom) the interface.
Simply said, there is a bug which causes a memory leak when used with 17.8.x and up, which has been fixed in V5.

[networkers]

Simply said, there is a bug which causes a memory leak when used with 17.8.x and up, which has been fixed in V5.

Ok, great. Thanks for the quick response.

[wiechec89]

Hi. Will I be able to use the english version, when i flash polish eeprom?

[flavyus1987]

What bugs we should check if it have been repaired?

[1 6 D]

I have to try v5 loader, my brother use V4 version in his Phaeton, today he wrote me that VCDS windows makas black when connecting with Comfort module of his car and VCDS uses 140MB in this moment, so I have to update interface to V5

[mikroel]

Work excellent on Golf4 1.9TDI 4WD
Encoding ,adaptation , Power steering calibration, Haldex AWD checking ,CAN GAteway , Automatic scan ,Can,K-line ...

good work Kolimer!

[H2Deetoo]

If you want to use 17.8.x or higher then use V5 indeed.

[papalazerous]

Hey I just bought my VCDS cable, this one http://www.obd2tuning.com/vcds-kabel-new-vcds-software-vagcom-100-original-function-vcds-interface-for-vwaudiskodaseat-p-2749.html but I install everything and need to register VCDS loader before I can use it. Is there a way I can generate registration or do I contact the Chinese seller. Also my version is "VCDS Loader V1.10.1 Setup(EN).exe" do I need to change to a newer version? If so will I need to register everytime. Sorry if this is common knowledge I am trying to read back through this very long thread to educate myself.

Thanks
John

[hid3]

The hardware looks identical to genuine. So much of the gossip "proudly made in the usa" they claim...
From what I remember, there should be empty holes for pins designed for reflashing. Solder in the pins, reflash to Kolimer's (God ble$$ him) and enjoy.

[papalazerous]

The hardware looks identical to genuine. So much of the gossip "proudly made in the usa" they claim...
From what I remember, there should be empty holes for pins designed for reflashing. Solder in the pins, reflash to Kolimer's (God ble$$ him) and enjoy.

My first thought was that the pcb looked like the real thing, I've been assured I can update it and it will still work too. I didnt know about the VCDS loader thing when I bought it, I thought it a little odd that I have to register it though... Like it's being sold off a chinese fake website why would I have to register it. I will have to look through the thread to find the correct guide to reflashing it based on my hardware etc. I have a programmer sat here so have all the gear ready to go when I know what to flash. I need to know I am following the correct info before I do anything as I dont want to brick it

[hid3]

If it looks like genuine, maybe it tastes like genune too? I'd give it a try. Grab latest Beta, install it and run without any loaders. But.. I would disconnect the internet conenction before installation. Also, make sure that it doesn't add anything to startup (use msconfig to check). So install latest beta, try to run a scan on a car, try to code it and see what happens. It might be possible that you got some kind of refurbished genuine (e.g. second hand or so).

If it doesn't work with latest Beta and no loader, then remove the software and only then restore the internet connection back.
Then it's time to program...
All you need for that is in this post:
http://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3185666&viewfull=1#post3185666

[peetee25]

Hello there, I found my old clone cable for VCDS.
My question is how i can do with it to make it work again with newest version ?
It have ATmega162 chip.
Is there possible to flash this cable or do something with it ?
When yes, Can you tell me how ?
This is the photo how it looks inside
498861
I have other clone cable with newer FW 1.92 or 1.93 (IDK now), but when i try to update firmware in original newest 1.96, VCDS says update failed so i want to try make something with this.

......AAAND sorry for my English...I'm from slovakia.

[H2Deetoo]

Please read 1 message above

[alinutz198]

hello, and glad to meet you.
i have a chinese clone of vcds cable with 17.1.3 software.
both are working in good condition but i want to update them.

when i try to write with eelang ... it says not in bootloader mode.
what can i have to do to work ?

please explain to me stap by step.

10x

[hid3]

My God, everyone wants it in step by step.
Why don't you want to use your brain?

* Firstly, the Chinese cables might range from total sh1t to good ones. Identify if you have Atmega there. If not, throw then away and purchase some quality stuff. Costs $23 with free worldwide shipping.
* Secondly, read the Info.pdf file carefully in archive provided by Kolimer. Do what it says.
* Finally, when done, have some beer or weed, depends on your taste,

Step-by-step complete.

If you can't solder/program on your own, find someone who can and ship it to them to have it done properly.

[alexm1]

I did this way:

Open vcds (17.1.3) Test ok..... close vcds

Power on 12 v to your cable- usb plug in laptop



RUN hardware_ detect tool 0x44 or....0x46

Check you vid/pid


Run ee_write - see if vid/pid is ok if not corect it...wait for OK

After this Run ...writelang ...select you lang and write.

[alinutz198]

hello and 10x for your time.
is atmega cable . when i do the test it says that is 46 version with 1.96 firmware.
but i get "interface not in bootloader mode".
why is that ? what i have to do?

[alinutz198]

multumesc. fac toate astea, dar cand incerc sa scriu ee write lang imi zice ca nu este in bootloader mode

[Mario6]

multumesc. fac toate astea, dar cand incerc sa scriu ee write lang imi zice ca nu este in bootloader mode

Read this and use the V5 Kolimers loader.
Thanks to Kolimer.

http://obd2-diag.blogspot.com/2017/08/vcds-178-download-free-with-user-manual.html?q=vcds

[liviudiaconu]

Must understand that if the cable haven't a real oem bootloader, the kolimer's writer not work well. In this case external programmer needed.

[xoom]

And im guessing that HW difference is bootlaoder size (one is for FT232Bx chips - 256bytes , other for FT232Rx chips - 512bytes)

[liviudiaconu]

Not realy exact.

"44" hardwares (can be with BL, BM or with RL or RQ) having 512 bytes bootloader.
"46" hardwares (RL or RQ) having 1024 bytes bootloader.

Kolimer's writer work on both kinds of bootloaders but chineses don't write original FW, so, writer cannot do his job.

[xoom]

Not realy exact.

"44" hardwares (can be with BL, BM or with RL or RQ) having 512 bytes bootloader.
"46" hardwares (RL or RQ) having 1024 bytes bootloader.

Kolimer's writer work on both kinds of bootloaders but chineses don't write original FW, so, writer cannot do his job.

can be.. i can mix them :)

[alinutz198]

Must understand that if the cable haven't a real oem bootloader, the kolimer's writer not work well. In this case external programmer needed.

and where i can find real oem bootloader

[xoom]

its in firmware (Flash1.96_HW_0x44.bin, Flash1.96_HW_0x46.bin)

@ 3E00 offset

[alinutz198]

can i read before firmware from mi interface?
what is pinout of 46 hardware interface

[xoom]

can i read before firmware from mi interface?
what is pinout of 46 hardware interface
If its(ATMega162) locked (99.99%) it is.. then you can't.. Its allways same pinout for ATMega162

1pin. MOSI
2pin. MISO
3pin. SCK
4pin. RESET

[relax80]

Anyone have clean loader v5?

contact me on PM

[mikroel]

Anyone have clean loader v5?

contact me on PM

What does you mean “clear”?


Sent from my iPhone using Tapatalk

[relax80]

Clean = without Kolimer Logo on start

[papalazerous]

Clean = without Kolimer Logo on start

I would have thought if you want it without seeing the logo for 2 seconds you are asking too much!

Just remember how much money you save by seeing that logo ;)

[hid3]

Clean = without Kolimer Logo on start

You can get the loader without Kolimer's logo here (https://store.ross-tech.com/shop/cat/VCDS).

[cawadany]

Clean = without Kolimer Logo on startOr you can make the loader by yourself

[relax80]

You can get the loader without Kolimer's logo here (https://store.ross-tech.com/shop/cat/VCDS).

Thank you very much,

[relax80]

Or you can make the loader by yourself

Really, can you help me? :2in1:

[kowalwalcz]

Really, can you help me? :2in1:
For What? For sell kolimer job? Wrong way!!

[tk500]

For sellers, the text is a problem.
Chinese remove it and enjoy a lot of this free lunch :tears_of_joy:

[Vet]

Hello to everybody!

I’ve been watching for this conversation for a quite long time. In summer even tried to report, that V2 loader with 17.8.1 were made mess with coding bits and adaptation channels description, but it was not possible for me to register on forum.

First of all many thanks for all, who are trying to make "it" work! :)

Yesterday I tried all combinations with my cable (Atmega162, FT232BM, HW Type 0x44). Unfortunately still fully functional version is only 11.11.0_En.

Loader V5 with 17.8.0_En or 17.8.1_En doesn’t even see my cable! After pressing Test button in program, I’m getting “Interface: Not found” answer. Perhaps because of “BM”FTDI chip???

Loader V2 with 17.1.3En works fine from the first look: description of bits and adaptation channels are fine. But if I try to work with program a little bit longer (10-15 min), I’m starting to get “Communication lost with control module” massages. For example, if I start “Auto-Scan” procedure it’s in 100% cases never have been complete. Auto-Scan process always interrupts with massage “Communication lost”. And, that is most scared, during auto-scan process, program is messing with order of scanned control modules! It starts from 01 (Engine CM) than after some address (let’s say 19)program, instead of next control module, proceed querying 01 address ones again!

So unfortunately I can’t confirm, that V2 loader with 17.1.3_En is fully functional. :(

P.S. May be anybody have any idea, how to solve “Interface not found” answer on my cable with V5 Loader version???

[liviudiaconu]

I only one with BL tested on V5. Worked fine. (17.8.0 only, not tested with 17.8.1). So..is possible to be an issue with your cable? Or something in your OS?

[xoom]

Did you checked your VID/PID of cable? maybe its FA20.. and hw write cant "see" it

[liviudiaconu]

Asking me?
FA20 and worked.
I will try again this afternoon or tomorrow.

But not used Writer, always used external programmer.

[hid3]

Are you able to pst the PCB of the interface which is having problems?

[xoom]

Asking me?
FA20 and worked.
I will try again this afternoon or tomorrow.

But not used Writer, always used external programmer.

No.. The post before you :)

And Yes it doesn't matter if you use ISP :)

[alexm1]

What about fuse/lock bit?
I saw that they are changed only with external programmer, with Writer will remain the same as before reflash.
So, is important to change them or not?

[xoom]

What about fuse/lock bit?
I saw that they are changed only with external programmer, with Writer will remain the same as before reflash.
So, is important to change them or not?

They are not that important (as they are already set to hardware type)

if you use Writer ... then bootloader writes FW inside and no need to touch fuses

i allways leave my Fuses same :) and Lock Bits 0xFF (unlocked) ;)

[vaicekas]

Loader V2 with 17.1.3En works fine from the first look: description of bits and adaptation channels are fine. But if I try to work with program a little bit longer (10-15 min), I’m starting to get “Communication lost with control module” massages. For example, if I start “Auto-Scan” procedure it’s in 100% cases never have been complete. Auto-Scan process always interrupts with massage “Communication lost”. And, that is most scared, during auto-scan process, program is messing with order of scanned control modules! It starts from 01 (Engine CM) than after some address (let’s say 19)program, instead of next control module, proceed querying 01 address ones again!


P.S. May be anybody have any idea, how to solve “Interface not found” answer on my cable with V5 Loader version???

Your problem is a poor quality adapter. Probability of bad FT232. I had a problem like “Communication lost” I replaced the FTDI from another cable and got it all up. Sometimes MCP2515 crashes.
I have several adapters with FT232BL and with FT232RL. I tested them all with Loader v5, I did not notice any problems.
Try re-writing BL.ept to FTDI (FT232BM is the same as FT232BL) and then try the Loader v5

[Vet]

Thank you all guys – you make me believe my BM-cable should work with V5 Loader also! And finally “Interface is found”! :elefant:


This is what I did (just for the case, if somebody gona get in my trap):


1) I flashed ones again by USBASP-programmer ATmega162 with “VCDS HW 0x44 LB v2.prj” project file. – No luck (Interface: Not Found)
2) Then I flashed ones again by MProg FTDI chip with “ftdi_mprog_BMBL.ept” – No luck (Interface: Not Found)
3) Then, after reading XOOM’s post once again (
Did you checked your VID/PID of cable? maybe its FA20.. and hw write cant "see" it), I thought: If I have bootloader in my cabele (cable is already flashed by programmer with the firmware which has bootloader), why don’t to try reflash it in “lucky mode” by “VAGCOM_EEWriteLang.exe”. So I stared it, changed PID from 0xFA24 to 0xFA20, pushed write button and cable was reflashed one’s again to custom firmware (according to manual).
4) To my surprise cable past test in 17.8.0 program!
5) I had to agree with proposed firmware update from 1.95 to 1.96. And now 17.8.0/17.8.1 are seeing my cable smooth and perfectly!

Tomorrow I will test it in the car. Hope everything will past fine..


Thank you all guys, ones more!:wavey:

[flavyus1987]

Everytime before program it, check PID in device manager.