VAG-COM/VCDS EVERYTHING

[Roma77]

And why did you write this? if you have problems then you need to write about it and not write famous things ..

[iJo09]

Already written my problem in the previous page

[Roma77]

the previous pages have a solution to your problem

[ely862me]

Mprog can't find the device. What does that mean?

[Lolo4321]

Current cable from vip link.http://imgur.com/a/cteX7XQhttp://imgur.com/a/cteX7XQ.jpg643056

EDIT: Does someone know, i connected the dongle into the OBD port and into the USB. PC recognises it as a Ross Tech HEX, green light on.
When I run VAGCOM_HWType and click read, no interface found. I tried VAGCOM_EEWriteLang, same issue no interface found.
The cable is from the VIP link ( HEX, not the HEX V2)

I have to flash the fdti from xml file, how do i do that?

643093 cable has 6 pins

programmer cable has 2x5
643095

[gini80]

Try like this

[Lolo4321]

First of all thanks to all Digital Kaos members for making this affordable, and making it happen. One member guided me from the start and i cant thank him enough.
The issue was i didnt plug in the cable while installing the drivers.
It all works ! Im amazed. Thank u all for makinh it possible and alive.

[Novason]

Hi all,

I'm a total newbe here, hoping to get some help with flashing my VCDS cable...

I've been using VCDS 10.6 with my "VAG-COM cable" for many years and it's all working great on my 2009 Audi A4. I recently got a 2016 Audi A6 and obviously the kit is too old for this, so I've sorted out the SW side of things, I now have a working VCDS (v.18.9.0) but it wont work with my cable. When I try, VCDS finds the interface (as Ross-Tech HEX-USB+CAN) but show that the FW I am using is too old (v.1.84) and prompts me to update this, when I try doing it through VCDS it of course does not work. The cable still works fine with VCDS v.10.6 but I am hoping that it is upgradable to FW 1.96 and that I can run it with VCDS 18.9.0

I have used VAGCOM_HWType.exe to check the HW version and it says HW 0x44

Can someone help me with flashing FW1.96 into this cable? I am assuming that I need some sort of Eprom programmer, as such I would be happy to post it to someone who can flash it for a fee?

I can disassemble the cable and take some close up pics if needed as I've seen that there seems to be quite a few different versions out there

Many thanks in advance

[kaalis]

Sure, post images. Maybe it doesn't even contain atmega. Don't forget to read pdf file inside the loader archive.


------------------------
Here, open archive after downloading it. As of loader version 8.0 this file is called _README.pdf, previously it was Info.pdf
https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3639906&viewfull=1#post3639906
------------------------

[Novason]

thanks for replying kaalis,

I'll take it apart tomorrow, didn't even know about any .pdf files in the loader archive... I assume they are some sort of log files? What are they called, I checked the VCDS folder where the loader is located but I cant find any .pdf files... ?

[ely862me]

First of all thanks to all Digital Kaos members for making this affordable, and making it happen. One member guided me from the start and i cant thank him enough.
The issue was i didnt plug in the cable while installing the drivers.
It all works ! Im amazed. Thank u all for makinh it possible and alive.


Yaaay, finally someone with a solution. I just reinstalled the drivers and plugged the usb while doing that, now the HWType reads and also the Mprog sees the device. I can now see that the bootloader is disabled.
Can I still flash the FTDI if the bootloader is disabled? I assume the bootloader is disabled only in the ATME ?
643166

[Novason]

643196

Took my cable apart, and here is a close up of the internal. Is it a version that can be flashed with a later FW?

[gini80]

Yes , you can flash, but you must remove stc cip

[SzymonZy]

643207643208

[bg17aw]

Use MProg to rewrite your cable (in 9.2 package K0l1mer put FT232BMBL.ept. Use-it.

About Loader9.2: why was Mprog taken out?

There is no more FTDI-MProg 3.5/Templates in this loader package.

[Novason]

643209

And this is what the "HW type read" from loader 9.2 (thanks to Kolimer) reports...

Seems bootloader is disabled...

[Novason]

643224

And here is also a close up of the underside of my cable

[alexm1]

Yaaay, finally someone with a solution. I just reinstalled the drivers and plugged the usb while doing that, now the HWType reads and also the Mprog sees the device. I can now see that the bootloader is disabled.
Can I still flash the FTDI if the bootloader is disabled? I assume the bootloader is disabled only in the ATME ?
643166When booloader is dissabled You need to use Usbasp prog. (for Atmega) and Mprog (for FTDI).

[ely862me]

Yes, I understand now! I am awaiting the usbasp to arrive tomorrow.
Meanwhile I manage to make the cable work by installing the drivers with the usb connected to the laptop. I went to the car, scanned the engine, erased some errors, then I went to the adaptation and managed to play a bit with the IQ. And at the end I tried to enter the ABS module and suprise..the interface is not found !! Say WHAAT? Now at the DeviceManager the device is with the exclamation point and I can't get it to work no matter how many times I tried to install the drivers. More than that, the VID and PID changed from 403 FA24 to 409 0058 . Are these cables possessed or something...?

Can it be something wrong with the car that is messing with the cable?

EDIT: I managed to resolve the exclamation point according to post #8721 . Mprog sees the device but the interface is not found.

[Xaby]

Download loader from kolimer. Check if you have the right vid pid number. If no then flash ftdi with mprog and ept file from loader rar. then flash atmega with usbasp. when you finish interface bootloader will be unlocked and you can flash new version over usb.

[winamax69]

You can rechange it by yourself. You must first check the FTDI chip type on yor cable PCB BM/BL or RL/RQ. And you must choose the appropriate file according to the website below.

https://www.drive2.ru/l/494906127654322212/

You can download the FTDI-MProg3.5 app from this package(you must your cable plugged in to your computer):

https://yadi.sk/d/yHoXJC53UgA6dg

Best Regards

winamax69

[SzymonZy]

Should I cut here at 9th pin of stc? Someone had experience with that?

[ely862me]

They say remove the STC completely , I did it.


Guys, after I flashed the FTDI the VID and PID were restored to 403 and fa24. But after I removed the cable from laptop the VID and PID changed to random numbers.When these change the driver won't recognize them, so from here comes the exclamation point. Have I done something wrong to the interface? BTW, someone advised me to remove R51 too, could that be the problem? All together I have removed the IC8, D7 and R51.

[alexm1]

How should I flash ATMega with STC chip put here:

643315
Should I cut here at 9th pin of stc? Someone had experience with that?If I remeber well for this hw type you do not need to change anything. Anyway, first try as it is, you have nothing to lose. just give it a try and if it works ...you win the figth.

[SzymonZy]

Found something like that: https://mhhauto.com/Thread-VCDS-17-8-1-MULTILANGUAGE-FULL?page=43

[jan4]

use a mm to verify the 5 connections

[kaalis]

New releases for DRV, PCI, AIB, signed august 15th.

[Novason]

Would any keen member be happy to flash my cable for a fee?

I dont have a programmer and my soldering skills are not great, especially on thin lines like these but I would need FW 1.96 flashed into my cable...

[SzymonZy]

USBASP <---------> cable pin header (where 1 red line from usb)
GND<---------> 1 (black line USB GND)
NULL <---------> 2 (USB data line)
NULL <---------> 3 (USB data line)
5V<---------> 4 (red line USB 5V)
SCK <---------> 5 (ATMega 3)
MISO <---------> 6 (ATMega 2)
MOSI <---------> 7 (ATMega 1)
RESET <---------> 8 (ATMega 4)

USBASP_write_0x44.cmd

[Dynamicdk]

I bought a HEX-V2 cable from obd2cartool, but I can't get the disk working, none of the programs working or can be read, I have tried and contact them today, but havent get any answer and I would like to get started :)
anyone who knows where i can get the files

643824643825

[alexm1]

Usually takes ~12 H for them to respond, but allways sent me a reply. About your problem, will be more faster for you to find kolimer zip (read 10-25 pages back)and try to reflash by yourself or wait for them to answer and probablly they will give you a download link.

[SzymonZy]

Is there any hope to read UDS with this interfaces? Should I put it in the trash and buy OBDEleven or brand new VCDS?

[alexm1]

First you post pics with your hw than you indicate conections Atmega to Usbasp prog. but you did not say if you have tried anything about reflashing your cable. Did you have/found kolimer.s zip? Did you tried to run "read" your Atmega by usb to see if your bootloader is on or of?

[SzymonZy]

I reflashed my cable (0x44 newest flash - bootloader is enabled) but during scan got something like:
U1401 00 [008]
informations regarding extended error codes (UDS protocol) is available only when you use newest interfaces. (I translated it into english by myslef).

[alexm1]

What vcds vers. you use and what is the car year?

[SzymonZy]

19.6.1 and MY 2015 and 2017.

[alexm1]

I had no such problems with 18.9.0 . Until now i see that newer vers. brings more problems than benefits. Try with 18.9.0 and see if works different.

[SzymonZy]

Did you use it with UDS modern cars?

[sympho]

Can anyone send me the 9.2 loader please?

[Faanatyk]

Can anyone send me the 9.2 loader please?

https://mega.nz/#F!vQ9mWaaI!9FruIewlPy5l0ykTWM5JWA?LdVkDC7K

[bg17aw]

9.2 can be found here: https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3639906&viewfull=1#post3639906

[Fabio89]

FYI

VCDS 19.6.1 + Loader v9.2 tested in Jetta GLI 2019 and it was working.
Anybody else tested in 2019+ MQB Models ?

[ely862me]

Yahoo! I finally made it! I have flashed my cable with usbasp and it worked! Big thanks to gini80 who's help was more than I needed! Also thanks to liviudiaconu and jan4 and everyone else who responded.

Now I am going to test it on the car!

I am the happy owner of vcds 18.9 !! It's great when you can do something with your hands! Thank you guys who developed these programs !

[Faanatyk]

Hello Guys,

I have HW like in attached photo. Currently i am using VCDS v 11.2 - and all is ok, but i am not able to check newest cars (friend just bought Polo 2014)

After check with HW Type i got :

VID / PID : 0403 / FA20
FT Serial : RT000001
FT Description : Ross-Tech HEX-USB
FT Chip ID : 0x19800400
FW Version : 1.84
HW Version : 0x44
Identification : HEX-OEM
Language : Czech - SVO
Bootloader : Disabled

644176

I know pinout for connection (from top - photo is upside-down):

○ -----> ??
○ -----> ??
○ -----> /RES
○ -----> MOSI
○ -----> MISO
○ -----> SCK
○ -----> USB +5V (Red)
○ -----> USB Data- (White)
○ -----> USB Data+ (Green)
○ -----> USB Ground (Black)

After checking if all is ok - should i just run batch (USBASP_write_0x44.bat) ? And that all or i just missed something ? I have seen that in this HW there is not needed to remove any parts.

Thank you for helping

[Roma77]

Hello Guys,

I have HW like in attached photo. Currently i am using VCDS v 11.2 - and all is ok, but i am not able to check newest cars (friend just bought Polo 2014)

After check with HW Type i got :

VID / PID : 0403 / FA20
FT Serial : RT000001
FT Description : Ross-Tech HEX-USB
FT Chip ID : 0x19800400
FW Version : 1.84
HW Version : 0x44
Identification : HEX-OEM
Language : Czech - SVO
Bootloader : Disabled

644176

I know pinout for connection (from top - photo is upside-down):

○ -----> ??
○ -----> ??
○ -----> /RES
○ -----> MOSI
○ -----> MISO
○ -----> SCK
○ -----> USB +5V (Red)
○ -----> USB Data- (White)
○ -----> USB Data+ (Green)
○ -----> USB Ground (Black)

After checking if all is ok - should i just run batch (USBASP_write_0x44.bat) ? And that all or i just missed something ? I have seen that in this HW there is not needed to remove any parts.

Thank you for helping
You are mistaken, you have an STC chip, you need to remove it and throw it away. Then solve the issue of upgrading the firmware. There is no longer a transistor but ... remove the chip. And you definitely need a programmer.
P.S.
You have a very good logic chip but a very bad KL bus

[ely862me]

Read the Readme pdf. You need to run Progisp. Don't forget to install usbasp drivers,don't forget to have the cable connected to 12v.

[belkor]

try it and see
if not run PROGSIP and go on

[SzymonZy]

@Roma77 No he is not. Don't remove anything.
@Fanatyk Just plug the way I wrote a little bit higher. We have the same hardware. You will do it in a minute. Follow what I did and it will go.

If you have avr studio all required dll's and so on connect the wires as it is described in PDF directly into USBASP plug with jumper wires and that's all. Run cmd that I wrote. And definitelly don't connect it to 12V - it does not make any sense. Connecting to 12V during firmware upgrade is slipping out logic. Just take 5V and GND from USBASP plug. If you can't install USBASP use zadig.
However you will not be able to fully decode UDS codes on 2015+ cars.
I ordered OBDEleven for myself and will throw vcds into bin when it comes.

[Zippair]

Fabio: I did some codings in my2019 Octavia, it is working well

[ely862me]

I don't know about 12v or not, i just followed these steps https://www.car-auto-repair.com/how-to-set-up-vcds-work-on-usbasp-programmer/amp/ and it worked!
scroll down and find this lines :

BE SURE YOU HAVE CONNECTED CORRECT WIRES TOMISO,MOSI,SKC,RST,GND AND THAT YOU HAVE 12V ON YOUR INTERFACE.



I don't understand why after almost 600 pages there isn't a step by step written tutorial for this stuff. Is it because there are so many versions that a tutorial would not be fit for all of them? There is information but the info is not put in a order that the nonprogrammer(like me) would understand.

Anyway, I learn to desolder chips and I did my first programming ! Kudos for everybody who freely and kindly shared their work for this!

[Tib82]

...
I don't understand why after almost 600 pages there isn't a step by step written tutorial for this stuff. Is it because there are so many versions that a tutorial would not be fit for all of them? There is information but the info is not put in a order that the nonprogrammer(like me) would understand.
...
If you're using ҝØlimer's pack, you can find 2 solutions to do the job: a traditional programming content and a quick 1-step-only application. The easiest way to do it with the 1-step-only app, what requires 12V (e.g.: car ODB connection). With it there are no possible wiring mistakes, no wrong Lock or Fuse Bit selection, etc. But if you still want to do it with an USB programmer tool, here is a quick step-by-step guide (wiring, Win driver and programming) how I did it on my old fashioned (H3X-€ɅN) interface what has an inline 6 pin (1x6 pis) programmer connector: #6808 (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3376608&viewfull=1#post3376608) In case of a better quality \/2 has different programmer connector (2x7 pins) but the rest of the job is still the same.

[liviudiaconu]

I don't know about 12v or not[...]

Why i preffer +12V:

1. China clones are China clones. Can appear a "surprise" at all time.
So, a short on +5V or a big consumption or..or.. dangerous for programmer.
2. Once +12 V pressent will see in the same time if 7805 working.
3. Not all clones having pins for programming. Is more easy to connect an OBD2-female connector than solder wires.

[Novason]

I have a nasty chinese clone cable... (see my 2 previous posts for pics) and its been working for many years for my 2008 Audi A4 with VCDS 10.6 but instead of flashing it I decided to buy a new cable from odbtool, hoping that will be easy to flash to FW 1.96

[bg17aw]

Why i preffer +12V:
3. Not all clones having pins for programming. Is more easy to connect an OBD2-female connector than solder wires.
Excellent point. Any step by step tutorial on how to connect the wires from the obd2-female connector to the programmer?

Thanks

Edit: would this be ok? https://www.aliexpress.com/item/32978084833.html

[forum1nick]

3. Not all clones having pins for programming. Is more easy to connect an OBD2-female connector than solder wires.

Or this options:https://uploads.tapatalk-cdn.com/20190820/95cd4730ca7ad0f4decd5e1f810fd61a.jpghttps://uploads.tapatalk-cdn.com/20190820/288a2ff073ae4e94902e74cefb330764.jpghttps://uploads.tapatalk-cdn.com/20190820/0f8d91049d59adfed94d585f7cf050ec.jpg

Sent from my Redmi Note 7 using Tapatalk

[bg17aw]

@forum1nick, I think liviudiaconu was talking about programming the interface using the USBASP programmer

How is your 12v suplly helping you program the interface, where is your programmer?

[liviudiaconu]

Excellent point. Any step by step tutorial on how to connect the wires from the obd2-female connector to the programmer?

Thanks

Edit: would this be ok? https://www.aliexpress.com/item/32978084833.html

No metter if you use USB ISP Programmer or "K0l1mer's solution. In both situations i use +12V.

For USB ISP Programmer use a female OBD2 where pin 16=+12V and pins 4/5 = GND. And GND connected to GND of programmer too.

In this case the cable is powered from external 12V source, 7805 "create" +5V for all "+5V powered components"..and +5V from programmer is not used..
Nothing else.
A..if having a "K" controler and a "CAN" controler, can connect ant testing the cable after programming.

[Kapten]

use molex, there is inside PC, Yellow 12v Black Ground, Black Ground Red 5v

[nextor]

Excellent point. Any step by step tutorial on how to connect the wires from the obd2-female connector to the programmer?

Thanks

Edit: would this be ok? https://www.aliexpress.com/item/32978084833.html

That one is ok, but I would recommend one like this: http://s.click.aliexpress.com/e/2VB5dCyg
It's very easy to power it up using any 12v power adapter that has a barrel connector and everyone probably has one of those in the house.

[liviudiaconu]

Not see in the only one photo if OBD 2 16 pins is realy female. Because they wrote "Mitsu 12 pins male" and the connectror is "female".

Here seems to be OK..
https://www.aliexpress.com/item/32823661938.html?spm=a2g0o.detail.1000014.2.67cc39 c2LeJFbC&gps-id=pcDetailBottomMoreOtherSeller&scm=1007.13338.141929.0&scm_id=1007.13338.141929.0&scm-url=1007.13338.141929.0&pvid=c9b147f0-848a-4549-883c-ea81dbf85b1e

[flavyus1987]

Better then other things.

[jan4]

Hi forum ,

slightly off-topic but ,

Are there any members who made an 'arduino with obd2-shield'-emulator for testing our beloved cables ??

645280645281645282



Is there anyone who has an VAG "optimized " simulator working ??

[flavyus1987]

For testing i use an old airbag module on K line and my personal car CAN line.

[flavyus1987]

With an enabled bootloader the vcds CAN be write by usb.but it can be read by usb?how can extract dump from it?

[vaicekas]

Not possible via USB. If LOCK BIT is enablet - not possible with the programmer as well.

[flavyus1987]

I want to clone an original one and keep it safety and use the clone daily.

[vaicekas]

beautiful dream.... :dancing:

[rak183]

I want to clone an original one and keep it safety and use the clone daily.

Y dont need Original. Just a clone with good chip is same as original.

[makos78]

I have a good clone cable which I bought on AliExpress with version 16.8 more than 2 years ago. It worked fine on my previous MY14 car.
Thanks to this forum I have managed to upgrade my 'old' cable to 18.9.1 with Loader 7.2
With the updated cable I can access and code my brand new car which is a MY19 Skoda Octavia (manufactured in April 2019).
There's a trick to access the modules without the 'Unsupported Vehicle' message (and grayed out Coding and Adaptation buttons): before you enter a module you have to switch off the ignition for a few seconds. Sometimes it's easy and sometimes it's not. For example the 01 module is very difficult to access, because the 'time window' is very small. I had to try it like 30 times. Module 09 is much easier. If you swith back the ignition too early you still get the 'Unsupported Vehicle' message. But if you wait too long the communication times out and you get a 'No response from controller' message.
It's still better than nothing. I have managed to code all my favourite tricks and that's the point. :)
Of course it's impossible to grab a full AutoScan because you can't do the trick right every time VCDS enters a module. But you can still read out the fault codes on the modules one by one.
You can also grab an Adaptation Map with the ignition OFF/ON trick.
The only module that I can't access with my updated clone cable is the Multifunction Control Module (I have LED headlights). It really needs a V2 cable.
Thanks again to this forum!
P.S. I haven't tried the new 19.6.1 yet. 18.9.1 (English) works fine and stable on my MY19 car with these 'limitations'.

Update: I have reflashed my cable with 9.2 and it works absolutely fine with 19.6.1 (English) on my MY19 Octavia. No more "Unsupported Vehicle" messages. :dancing:
I ran a full Autoscan, saved all my 20 Control Module Maps, did some coding and everything worked like normal. I have played more than 50 minutes with VCDS without a single issue.
Big thanks to Kolimer! :congrats::congrats::congrats:

[muscles1960]

Without the Module access trick being needed? Excellent news! Thanks BIG 'K'. Great work.

[heshamzn]

Today I manage to flash my vcds 12 with the latest files with my pc and usb only and didn't connect the cable to 12 v or to the obd2 and done successfully

[alexm1]

When you conect usb to your PC, led is on?

[drag00n]

Hi, I've been reading this forum for some time. I have 2 clone RT from Ali. I'm thinking if I can upgrade it to latest version (if upgradable or should I buy a better clone. Thanks in advance. https://uploads.tapatalk-cdn.com/20190826/0b936739b453f119d0f9a805ef4cb260.jpghttps://uploads.tapatalk-cdn.com/20190826/4256cd5762ac82e425617e301ef2604b.jpghttps://uploads.tapatalk-cdn.com/20190826/08556f5880fd5ba3eb46d72606464874.jpghttps://uploads.tapatalk-cdn.com/20190826/0337cc412cd67c556ee8c35b4ae39654.jpghttps://uploads.tapatalk-cdn.com/20190826/f81ecfd40346ba0bea2f8c39a5fc3d15.jpg

Sent from my SM-N935F using Tapatalk

[alexm1]

You can try to update the "red" one(pcb). Try first to see if your bootloader is enabled, if not you need usbasp programmer. And you need to do your homework reading Info/read me pdf file from Kolimer.s zip, you have there STC on the PCB so you have to cut circuit to R50.

[heshamzn]

When you conect usb to your PC, led is on?
red led not green but it worked ok

[alexm1]

There are some old cables without LM 7805 voltage regulator and Atmega is powered from PC usb. That.s why you do not need 12 v.

[msemafor]

Just to ensure myself - now I have a cable with chip ATMEGA 162, FW version: 1.96, HW version: 0.44, Identification: ROSS-USA, Bootloader: enabled. Use it with 17.1.3. Can I safely use VAGCOM_EEWriteLang from K0limer's pack 9.2 (huge thanks) to update cable firmware and then connect to Octavia 3 1.4 TSI 150 PS CZDA MY2016 with version 19.6.1? Maybe I don't even have to update firmware - just install newest version, save loader in appropriate folder and start it? Won't it brick my cable?

[kaalis]

You have to update firmware, otherwise 9.2 loader won't function as it should.

[msemafor]

You have to update firmware, otherwise 9.2 loader won't function as it should.

Thanks kaalis. Are parameters i mentioned above make my cable ready for firmware update without risk of destroying it? I wouldn't like to stay with nothing except need to buy another one.

[kaalis]

Just try updating it and don't you worry.
Post pictures of PCB both sides and then we can tell in detail how good/bad/so-so is it.

[msemafor]

Just to ensure myself - now I have a cable with chip ATMEGA 162, FW version: 1.96, HW version: 0.44, Identification: ROSS-USA, Bootloader: enabled. Use it with 17.1.3. Can I safely use VAGCOM_EEWriteLang from K0limer's pack 9.2 (huge thanks) to update cable firmware and then connect to Octavia 3 1.4 TSI 150 PS CZDA MY2016 with 19.6.1? Maybe I don't even have to update firmware - just install newest VCDS, save loader in appropriate folder and start it? Won't it brick my cable?

Would like to confirm that I succesfully updated firmware taken from K0limer's pack 9.2 and installed version 19.6.1 AKP. Works great with two Octavias 3 1.4 TSI 150 PS CZDA MY 2016 and MY 2017. Big thanks to all, who adviced me and even bigger thanks to k0limer.
Unfortunately in module "Engine" button "Measuring blocks" is inactive in both mentioned cars. Maybe anyone knows why is that?

[alexm1]

Same thing with Adv. Meas. Values?

[msemafor]

Same thing with Adv. Meas. Values?

Nope, Adv. Meas. Values are active and show actual data.

[alexm1]

In this case is a normal behaviour...
https://uploads.tapatalk-cdn.com/20190827/1174f80233f3808db4dc47a7fab296ec.jpg

[jach0o]

646404
after flashing 9.2 loader i got problem "no coding information" for 5F in A6 C7.5 MY2018 witch was working before(long coding helper). Currently even if i restore to lower loader with different (lower vcds) it still drops same error?? what should i do ?
to be honest 5f is one of most tweaky driver so its importat for me to have possibility to see codings

646400

[msemafor]

In this case is a normal behaviour...
https://uploads.tapatalk-cdn.com/20190827/1174f80233f3808db4dc47a7fab296ec.jpg

I'm not an expert or experienced user of this application but do you mean if I change protocol in options I'll get "Measuring blocks"?

[alexm1]

Nope, this depends about (your )car protocol(you can not change it).
So, at your car what do you see: UDS or KWP? Acordind to this info you will have Meas. Blocks active or you can see same real time info using Adv. Meas. Val.

[tigri007]

I'm not an expert or experienced user of this application but do you mean if I change protocol in options I'll get "Measuring blocks"?

No in new cars UDS protocol is used, so
No more "Measuring Blocks" is possible.
Instead for these Cars you must use "Adv. Meas. Values" with has the same functionality of "Measuring Blocks" also is better because you can search which parameter you want to monitor the values.



Thank you

[onek24]

I would like to thank k0limer for the loader.
But could someone expain to me, why the original 9.2 loader from k0limer creates a "VCDSLoader64.exe" and a "vcds_hook.dll" in C:\Users\...\AppData\Local\Temp?
My SHA1 is(handwritten...):

DA46A17C6CAC86E34B0134E32EF0074B538E6A0D

I guess the dll just unpacks from the loader into the temp folder, but this still is a bit weird.

[taikun]

Welcome


I have two different interface clones to choose


which one will be better for golf gti lift 2018

vers 1

646691

vers 2

646692646693

[liviudiaconu]

First with transistors on Klines, low quality.
Second good quality.
For what you want, test yourself.

[taikun]

First with transistors on Klines, low quality.
Second good quality.
For what you want, test yourself.

For general diagnostics, lamp coding and additional equipment. :)

[liviudiaconu]

Tested 9.2 with 19.6.1 EN,ROJ,HGJ

EN..OK
HGJ..red serial, eeprom not destroyed. Only counters changed
ROJ Green serial and seems to no destroy eeprom. But time to time (said with HW46) no connect to 19 Can GW. 3 times tried to connect, no connect.
After this, tested with a HW44, worked
After again with HW46..worked..
Strange

[Fabio89]

FIY

Tested 9.2 + 19.6.1 ENG in some MY2019 MQB

Jetta MK7 GLI = Working
Tiguan Mk2 = Working
New Polo AW = Not Working :(

[ferdinandus]

i would like to thanks all of you about this great thread. im trying to read it all.

i have three cables, with diferent versions (704, 12.12 and a newer one from two years ago) and the first two ones seems to be 'good' hardware candidate to experiment with them. the last one is bad hardware but its is currently the cable that i use to check issues in my car now.

i will try to update the two first ones.

best regards. ( i will continue reading)

[tino3]

Hello, does anyone have a link to download VCDS 19.6.1. CZ?

[Lolo4321]

Wow im pretty amazed that it works

[ferdinandus]

After reading a lot, i downloaded package.

First, i have checked inside my two 'old' cables. They seem to be hardware 44 due to pcb tracks to GAL/PAL

The first one is date on pcb about 2007. I think it is the 'classic' design. It is a 704 \/XX C0M version

https://i.imgur.com/33qsC6b.jpg

https://i.imgur.com/h105MFJ.jpg

https://i.imgur.com/4OisA0F.jpg


I have check with the tool:


The second one includes 'protection chip' It is 12 12

https://i.imgur.com/cXWjUJm.jpg?1

https://i.imgur.com/9Zt2cqr.jpg

https://i.imgur.com/2MECeYq.jpg




Althout the first one appears with bootloader enable, it have not been able for me to perform upgrade with the tool. It writes, but at the endd appears a window showing some type of no response...

The second one is disabled , not possible. I have started with the second one, cutting the track to R50 resistor and welding small wires for the iscp programming. After welding, prior to do any programming attempt, i have checked again with the HW info application, but no work... ( i do not know why, only cut one track and some wires correctly attached to chip legs) The cable led blinks in red. In order to recheck, I have removed welded wires and renabled the cut track but same behavior... no detection anymore... Probably i have broke it before doing nothing. (or after cutting the track, for some reason the cable get unprog... i do not know)


Well, i will continue with tests, and if no success, i will try at the end with the 704 cable via icsp reprog

[bg17aw]

Tested 9.2 with 19.6.1 EN,ROJ,HGJ
HGJ..red serial, eeprom not destroyed. Only counters changed

can you explain a bit more, what counters, how can the eeprom be destroyed and what do you use to notice that?

[liviudiaconu]

"Eeprom destroy" mean here "eeprom content altered".
RT do this when a "blacklisted" serial found in eeprom.

Test a cable. Will see "x DTC, y adaptations, z coding". Do few DTC erase, adapt or coding. X,y,z will change.
x,y,z = counters, b.e.

[flavyus1987]

Crazy question. How can be read by usb atmega & eeprom?

[MeMBraNe]

Hi, is it possible to update the so I can use it with version 19 of vcds? Bootloader shows disabled. Only programmer I have is bdm100, will it work?

Not sure on chip https://uploads.tapatalk-cdn.com/20190902/663a77efc0384971f0616a6e40c7ba36.jpghttps://uploads.tapatalk-cdn.com/20190902/e93258bb95f07d2704a14d2c14ce9ac9.jpghttps://uploads.tapatalk-cdn.com/20190902/c2d9d5095294ad9e1640455f57e01962.jpghttps://uploads.tapatalk-cdn.com/20190902/b8fbb9c0de7601a56b2fe0a2a153d06e.jpghttps://uploads.tapatalk-cdn.com/20190902/288c9a101a66d8762ad2c1c8d832d8b2.jpg

Sent from my LYA-L09 using Tapatalk

[vortexo]

Unfortunately i don't think so.
It has no atmega processor...

[Tuono]

[QUOTE = kolimer; 3639906] Loader v9.2 veröffentlicht! Es verbessert die Kompatibilität mit nicht englischen Versionen und der VCDS 19.6.0-Version.

http://ge.tt/6I9tkOx2 (http://ge.tt/6I9tkOx2)
https://www101.zippyshare.com/v/biPvu9Lt/file.html (https://www101.zippyshare.com/v/biPvu9Lt/file.html)
https://www.sendspace.com/file/5qr55f (https://www.sendspace.com/file/5qr55f)
https://uptobox.com/l96rbs2lo9h6

Kolimer. .....[/ZITAT]


Hello,
links does not work.
Will you refresh, please?
Regards

[MeMBraNe]

Unfortunately i don't think so.
It has no atmega processor...Damn, so only v17 I can use?

Sent from my LYA-L09 using Tapatalk

[MeMBraNe]

[QUOTE = kolimer; 3639906] Loader v9.2 veröffentlicht! Es verbessert die Kompatibilität mit nicht englischen Versionen und der VCDS 19.6.0-Version.

http://ge.tt/6I9tkOx2 (http://ge.tt/6I9tkOx2)
https://www101.zippyshare.com/v/biPvu9Lt/file.html (https://www101.zippyshare.com/v/biPvu9Lt/file.html)
https://www.sendspace.com/file/5qr55f (https://www.sendspace.com/file/5qr55f)
https://uptobox.com/l96rbs2lo9h6

Kolimer. .....[/ZITAT]


Hello,
links does not work.
Will you refresh, please?
RegardsI downloaded last night

Sent from my LYA-L09 using Tapatalk

[vortexo]

MeMBraNe (https://www.digital-kaos.co.uk/forums/member.php/576095-MeMBraNe)
Use it as it is or buy a good interface

[kaalis]

19.6.1 releases for ITT, PTT and EST.

[MeMBraNe]

Hi thanks for that lol, would you possibly advise which one i should look at buying

[MeMBraNe]

For all of those having problems downloading the v9 loader from the provided links, here is a Mega

https://mega.nz/#!ohEwhAYB!NlXGmvCdtXpItjxmt84pFWiWEcaMt2bvHrqNHrf V5sE

[hid3]

Crazy question. How can be read by usb atmega & eeprom?

Mate, you got all the info regarding your "project" in PM. Other than that, it is impossible. So please stop being a parrot and ask what has already been answered...

[liviudiaconu]

Especialy in "public zone".

[ely862me]

Hi thanks for that , would you possibly advise which one i should look at buying

They say this is the best you can buy.


639829639830

[catalinosonesti]

hy all ,freinds what is the procedure to leran a key 5k0 837 202 ad for a vw tiguan 2014 ,with vcds ?
thx

[ely862me]

This is not the place for this question. But since you already asked: I programmed a key for a Skoda Octavia 2004 using this method : https://youtu.be/xLKNg4yioFk . I am not sure it will work the same for a newer car as yours. And I believe this works only for the remote not for the immo. Immo chip is a different food.

Also Ross-Tech explained the procedure here http://wiki.ross-tech.com/wiki/index.php/Immobilizer_III_Key_Matching_(Cluster) .This works with the 4 digit pin.

[Roma77]

It is possible to read data from FT232 and eeprom Atmegi 162 e-industry by usb, but after reading it is necessary to finalize the editor for use. the program VAGCOM_HWType does this visually for us, the same actions can be performed in a .bin format and edited for use.

[catalinosonesti]

ok ,i read immo with carprog , ,, thx all

[FredrikO]

Hi guys!
You are now reading a legit n00bs first reply in this forum but I hope you'll bear with me :) English isn't my native language either but I hope it's okay.

My friend bought this cable of eBay long ago together with version 15.7.0.2 of VCDS. He lent it to me and I have used it on multiple cars and it has worked great. Now the same friend bought a new car and we need to update VCDS to get Long Coding Helper to work with his vehicle (and it would also be fun to try out a 4 year newer version of VCDS).

I opened the cable up and saw that it says ATMEGA132 which seems like a good thing, right? Here is some pictures of it:
647941647942647946647947647948

So the simple question is, is it possible to get this cable to work with 18.x or 19.x-something VCDS? I would be really happy if you could point me the right direction :)

[liviudiaconu]

Yes, is possible. If read the "Tutorial" wrote by Kolimer and Co..will see exactly what to do.

[FredrikO]

Yes, is possible. If read the "Tutorial" wrote by Kolimer and Co..will see exactly what to do.

Awesome, thanks! I found the tutorial. I read somewhere that you could solder the wires to some holes instead of directly on the ATMEGA162 but can not find where I should solder?

Have I understood this correctly?:
If bootloader is enabled I do not need any USB programmer, I just flash it with the cable connected to the computer?
If bootloader is not enabled I need a USBASP-programmer?

[alexm1]

Your cable has NO header/holes to make your life easier
Read in PDF about STC and R50..you have it on pcb.
And run hw_type.ex to see more details about the bootloader.

[FredrikO]

Would I be able to run any newer VCDS version than 15.7.0.2 with this firmware? Sounds like a pretty small step from 1.94 to 1.96.
648035

[SaraLee]

They say this is the best you can buy.

Is this a good clone to buy? Looks similar to me. 648041

[vcdss]

1.Can someone point me to where can I find 18.9 german/deutsch software, now I have English/france but i would like to have German,

2.are there some other "obscure" languages available, is there a way to make custom translations myself that vcds would use?


3. Also where can I find newer firmware for flashing if i have atmel chip

thank you

[Roma77]

1.Can someone point me to where can I find 18.9 german/deutsch software, now I have English/france but i would like to have German,

2.are there some other "obscure" languages available, is there a way to make custom translations myself that vcds would use?


3. Also where can I find newer firmware for flashing if i have atmel chip

thank you
You should do what the user is doing in this post. #8852 (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3660367&viewfull=1#post3660367)

[kwat]

Hello everyone, colleagues will you help?
VCDS 18.9.0 suddenly stopped working, namely no cable is detected in the device manager, instead of Ross-Tech Direct USB Interface I have Unknown Device all the time. I reinstalled the vcds program, translated it to another computer and the same effect all the time.
The VAGCOM_HWType application also throws an Unknown Device error.
Of course, 12V power supply connected to 16 pin and GND to 4 pin.
Colleagues, will you help with the repair?
Thanks in advance for the hints.

[alexm1]

Post some pics with PCB to see what we have under the plastic caps.
Maybe Ftdi is dead by unknown reason...or usb cable could be defective.
Try to replace the usb cable first.

Led is on when cable is powered to 12v?

[kwat]

Yes, the LED is green, atmega 162 is on board.

[liviudiaconu]

USB cable or FT232 defective

[bg17aw]

"Eeprom destroy" mean here "eeprom content altered".
RT do this when a "blacklisted" serial found in eeprom.

Test a cable. Will see "x DTC, y adaptations, z coding". Do few DTC erase, adapt or coding. X,y,z will change.
x,y,z = counters, b.e.
thanks, how do you test the cable?
Mprog?

[liviudiaconu]

Option->Test, OK, Save, About.

[alexm1]

I have a weird hardware problem:
I get message K1 short to + from time to time, test was taken with cable pluged to obd2 (non vag)car and with external 12v power source- same behaviour.

So, I power up cable with 12v led starts to blink red and I get K1 short to + , k1 ok...

If I disconect the cable and try again led will be green. K1 k2 ok...

If I try again a few times(4 or 5) again I have led blinking red.

I ve replaced T1...T4, replaced usb cable, reflashed Atmega a few times, reflash Ft232BM - no luck...

Any ideas?

https://uploads.tapatalk-cdn.com/20190905/afcc599c512e68cc20f19aa1db1d2d56.jpg

[liviudiaconu]

Use a VAG car or a VAG controller.
Opel Corsa too, will offer good and correct test.

Or, try test only with +12V/GND. K1-K2 will be tested but Can NR

[alexm1]

Was initially tested on Ford Galaxy.

Than I tested on the table, only 12v.

And same thing ...after 4-5 times connect and disconect 12v, I get red blinking led.
I ve changed the order: plugged first to laptop and after to 12v, or viceversa same story...

[kwat]

USB is OK, how can I fix FTDI,
Thanks for the info.

[kaalis]

get another ftdi chip and solder it in place of this one. Piece of cake.

[networkers]

1.Can someone point me to where can I find 18.9 german/deutsch software, now I have English/france but i would like to have German,


http://www.share-online.biz/dl/DLYLT1HP7G9

[apsol]

Hello everyone, i was googling about vcds and found this topic.

I bought a vcds cable some years ago, 17.1 version, and yesterday I read on some forums that this cracked cables/software can damage the car and computer, fry components etc, it got me scared to be honest although nothing happened with mine until now.

So is it true or it's just "marketing" talk ?

Also is it possible to upgrade the software to the latest version I think it is 18.9 with the cable I already have or do I need to buy a new one ? Is it just a matter of installing the most recent one (cracked) ?

Thanks

[Lolo4321]

Cars have fuses for a reason. If you damage your module because of coding its ur fault.

[Novason]

Just got my new cable from ODB2tool, flashed it with Kolmer 9.2 Loader to FW 1.96 and all works now with VCDS 18.9.0

Many thanks for all the help and suggestions!

I did notice that after flashing, the serial# changed... reading it with "HWtype" is that normal?

[hid3]

Hello everyone, i was googling about vcds and found this topic.

I bought a vcds cable some years ago, 17.1 version, and yesterday I read on some forums that this cracked cables/software can damage the car and computer, fry components etc, it got me scared to be honest although nothing happened with mine until now.

So is it true or it's just "marketing" talk ?

Also is it possible to upgrade the software to the latest version I think it is 18.9 with the cable I already have or do I need to buy a new one ? Is it just a matter of installing the most recent one (cracked) ?

Thanks

This is marketing talk spread by R0$$. They even have a dedicated page for that: http://www.ross-tech.com/humor/dust.html
Also, they spread the gossip on "how dangerous memory injections are" but practice shows othervise.

[Novason]

Thanks for suggesting a new cable HID... arrived well and works fine after flashed

[jonny190]

I know that im probably boring with this questions "why this and why that but....Why is this happening...Chip type FT245R?????(attached picture)

Also i have noticed when opening .ept file for FT232RL ("VCDS 908 FT232RL.ept")in Mprog stands for Device Type: FT232BL ....not RL? is it mistake?

Did you manage to find a correct template for this and get it working? i'm in the same boat and feel like i've hit a brick wall

[zillarob]

I hope you guys didnt get me in over my head lol.
My old 10.6 clone finally croaked so just ordered the DK special from obd2cartool with option 2 (hex v2) and the programmer just in case.

Have a few legit Ro$$ Tech cables, but Id prefer to have a less expensive one to take out on the road or leave in somebody's car lol.
Took a while to get the KII setup to do what I want, but what you guys are doing looks like fun, so wth.
Thanks for posting up the info, and wish me luck, I'm goin in lol

https://lh3.googleusercontent.com/J3ipMwpxjzcovpcMUxBQTGBykMGNK3YzVfwE24RleSPHQx6HWE mtjbXjvFkz1CkEKZKkuE93Fjtje0oebxA5J136Bvj4v-LPb6YGW551iYpqhgfrCEKe51huQFRRbNqVkpE0-TU8TZjXJg28ADoeknltsYrUJUQ4HwX_-jiZWXMgdCquZJTDvwt4CtU--3k4rcLHnrh9CTnIKomIFF-cX3LFGhFQ7W2f2zrnwdOQP7-v5P6TJ477-lQ02r49SmAR86R49YZmMlr2jeIMbX5ViBuOi3unRmsqN-JYQ4mEgK5ccXo2XbIVnmve89eDH9TAuDwZM3b59nqr-NH7o-CXKFW9FQkdu4jxMDE_UFx-BJCtX11Rc1dSvQQr-VgzMdAcCvYKpHxrEmWRBgzGmhtxjcI7-Xei80BAUWW9pKaqx1AgZHCa6tnduXljAemF2sAM1NitwLcwypD MvdhSsq_chO1oeGZJphGQ8T8YQOGx7ZweCzdraB7t8MoXKzy4n YWpBwU3nRIAxhTrFo7QB9dWxDafbH7GgSokLbkFzpzjjzFpg_3 9zJWgIVtyhZk2ptv_kqt9rwqwXjNCIhDm_QztA7_7gZdctM562 TecpG5D26woZC6pj9CBulD7w2E-M2nT1u1ijgEIC6jrbUQHIAyEKaHso6f6p6ffFPA59k97JTQH2s vmgKBk3_Q=w1010-h757-no

[zillarob]

Here are the guts to the 10.6.
Look like something worth poking at? Probably good practice anyway, not like I can break it more lol
I did dl a few of the loaders so will plug it in when I get a chance and see what it says.

https://lh3.googleusercontent.com/RDuQpFca6xzjfil1GpxDz7aU4pVKx-LSRTSBm2Xps9tobLdwU7t2perwG7hfX4fpm06cBkJUZ6UWGdaa k3OzbB6OUGbajWVromPicCVFxZZRhBQai89O5qKHpZHBZCmWOh FbKbK78qt7A3WEtwsomc7a7jOUdrC4zQd9c5Jx0JtzcJRyPTHC tI1x_8XsHPniGrLRBxMNVXLG353Ww35Slqr-JckaI3lV53pdU6V5-rRIpYisCVQ8B-qUW_Ae1fEwAvK-VFJVthqgLyWOPMmtgrw8HBpMNe3WcK1oUoI8diOqlIPvY8UnRW exAK331l_soATZtafUOkBqCCCvn0x2tMwUqJjhBZjS7H7sInM9 j_EuWll3DO4FadINH56gKYN4-aW5rmfUwf2GI6h79EYJCWCqz4Rvu4fBv4JRavowuv6A9S_yTHT WMD1oySb-h7jah8c5arCazTF9FB4G0cIuyYGLZX0dDm-LcCFQIFwuS15Bpt5Kmfq6fDbrBSIDMKVMsPBhjwTQWcV6J7ltI gC6NKPWM-7PrWnanoe4ScCS4U6rdCg2jzY5Ly8zVrn66KNmHJ3HdFXZ_yiA yVljtBlVKtMxPNC-5E8UHhMAELkciXvM0ZhMo15ZrNa8Gl_X7pGRz89HTZB21cjLGU My0pXfXF5qYi6WBXdjJPWn24M80FgKQxaN8-lT14A=w1010-h757-no

https://lh3.googleusercontent.com/QnLmBx7Q4Lvl7XKd32Q6MaibRw_FYlT4Ww02uX1OYVieGcDVjf voCcAJr1316_3n62P0TncCX1GHffAG03ALPX2np-pyHhk9jHPBWd1d7o35mPbRk-eZOay1-neDEsiEdYlQwTxQUYI95Lj3ADHlIM7dyrQfQOjL-vbjlprlVVl9FIyFCn7vnSBfEDpmn9Ln14erxgWwzRXFHjCYdNo BgNtpHDLTHFxqz7Ezf8mjlju9UiXnyfZDmCJqk5A8OYi5bIpDi 4Kpo7tCDTf86OldnMm2UXYON7hgF56Esgv-H5XHrsti4qaJd3PvaoNMw3nWbm_7pwnHkxNo4IrvNHW5eBfZXO kDeYEfTMiPvUHQOJeQjVgjBzPrmNQgVLMNMSxTgYtKD0er3-FedYx1ozKxp37pQ5_m-TyxvVbIQgyiSPTAerSHgPZCc_n8NFekwJ5HdzodALcu_C4Kp7c rmSCIxpWoMJj0BDhIia7hvnuj0g6qvtVgolp4TWie6c8zH6ea5 89RNb9GQ7adD5NQ91jTB3ZSevYYVZr7lyZ6bOFOUEWfF237u3A OQ8MbElsgHke5RJj8ayRawGqvUANLyOPmjOgoD_vztr5B3DsHt QAI_AdvQf7J_mK0n1aY3-zvD06idae6QaryfURTli3i4ndCSOfWJU_rG552ZY2jdLX9_fTs ipqLe-3vWeM=w1010-h757-no

[apsol]

Hello again, so I found out my cable has the bootloader locked and I don't want to be fiddling with wires and soldering, I may break it instead of fixing it. lol

So do you recommend any cable that I can update further to 19.6.1 ? I've seen a link here with a discount for members but I don't know if that one needs to solder wires etc in order to work.

Ideally it would be nice a good cable ready to go on latest version or close but if it's just a matter of flashing the eeprom then i think i can do it, there's so many on obd2cartool that I don't know what to choose.

[kaalis]

That discounted cable you found will allow to update without soldering. You may want to buy it together with Uspbasp to change 0x46 to real 0x44.

Sent from my SM-J510FN using Tapatalk

[DrCrazy]

Hi all,
I used perfect until now VCDS ROJ 19.6.1 with loader 9.2, but from 10 min ago the loader is blocked with message: " failed 4 "
You can tell me what's going on?

Many thanks

[FredrikO]

I really need some help from you... and I would be really happy if you can help me.
I have soldered the wires from the USBASP to the HEX-cable like this:

MOSI -> pin 14 MCP2515
VCC -> pin 18 MCP2515
RESET -> pin 4 ATMEGA162
SCK -> pin 13 MCP2515
MISO -> pin 15 MCP2515
GND -> 7805

I have verified with multimeter that it is okay and that the pins not connects to eachother.

I put the USBASP (it's set on 5V) in the computer and start PROGISP, PROGISP finds the USBASP and the LED on the HEX-cable starts blinking red. I click "RD" in PROGISP, the LED stops blinking (still red) but I get the error message Chip Enable Program Error.
If I load the flash and the EEPROM and changes the fuse and lock so it is correct and then clicks "auto" the LED goes green but I still get the "Chip Enable Program Error".

Any suggestions?

Edit: I have tried with different USBASP-drivers and also with eXtreme Burner AVR without luck.

[apsol]

That discounted cable you found will allow to update without soldering. You may want to buy it together with Uspbasp to change 0x46 to real 0x44.

Sent from my SM-J510FN using Tapatalk
And what difference would that make ?

[rak183]

And what difference would that make ?

Its for me also interresting to know this Difference

[Roma77]

And what difference would that make ?


Its for me also interresting to know this Difference
Those who are interested, study the schemes on the platform and know the differences between 0x44 and 0x46, at the moment all Atmega firmwares go 0x46, and there are different boards, and 0x46 and 0x44, it is logical that the seller knows about this and offers to buy a programmer.

[mattock808]

hi man, i have problem with my cable , the cable has stopped working.

led in cable no shine, PC no see cable. NO reaction PC after connecting.
where could be the problem? 650305650306

[Roma77]

hi man, i have problem with my cable , the cable has stopped working.

led in cable no shine, PC no see cable. NO reaction PC after connecting.
where could be the problem? 650305650306
Check 12 volts on the diode D1 and transistor 1705 - at the input of 12 volts at the output of 5 volts.

[mattock808]

thanks, yes i have 12v input 1705, output 1705 i have 5V

[FredrikO]

I really need some help from you... and I would be really happy if you can help me.
I have soldered the wires from the USBASP to the HEX-cable like this:

MOSI -> pin 14 MCP2515
VCC -> pin 18 MCP2515
RESET -> pin 4 ATMEGA162
SCK -> pin 13 MCP2515
MISO -> pin 15 MCP2515
GND -> 7805

I have verified with multimeter that it is okay and that the pins not connects to eachother.

I put the USBASP (it's set on 5V) in the computer and start PROGISP, PROGISP finds the USBASP and the LED on the HEX-cable starts blinking red. I click "RD" in PROGISP, the LED stops blinking (still red) but I get the error message Chip Enable Program Error.
If I load the flash and the EEPROM and changes the fuse and lock so it is correct and then clicks "auto" the LED goes green but I still get the "Chip Enable Program Error".

Any suggestions?

Edit: I have tried with different USBASP-drivers and also with eXtreme Burner AVR without luck.

No one with a suggestion what could be wrong or how to troubleshoot?

[hid3]

thanks, yes i have 12v input 1705, output 1705 i have 5V

Try reflashing the (correct) firmware then, along with proper fuses

[hid3]

No one with a suggestion what could be wrong or how to troubleshoot?

Are you sure you haven't swapped MOSI with MISO when connecting to the programmer?
Also, I'd suggest powering the chip via OBD2 12V circuit and do not power it from the 5V USBASP source (jumper removed)

[mattock808]

yes this action is no problem , with USBasp i flashing firmware no problem - this is done

PC no see cable, no reaction

[hid3]

Do you get red/green LED when plugged into car?

[alexm1]

First- Check usb cable, replace it temporally with printer usb cable.
And if you still do not see anything in Dev. manager , maybe FTDI is dead.

[mattock808]

plugged into car - led no shine

this is fix usb cable and is ok - I checked it with multimeter

no see in dev manager in PC

[hid3]

Something is totall wrong with your cable - both circuits do not work - neither USB circuit, nor the ATmega part. It's quite rare occasion when it fails to such a state. I'd say replace ATmega and replace FTDI but I still hardly believe it got that bad.

Take MProg. Connect the USB part to PC. Can you see anything in MProg (blank or programmed device)? If you can, then try to flash the FTDI's EEPROM with template for RQ/RL and then report back if it became detected or not

[mattock808]

scan with Mprog
blank devices - 0
programmmed devices - 0

[robinbga]

plugged into car - led no shine

this is fix usb cable and is ok - I checked it with multimeter

no see in dev manager in PCHello, I suggest that u get another device and connect to the Pc to see if the problem isn't the usb port like a printer or anything that uses usb port.
Otherwise yo cable will need new chips replaced.

Now I have a problem on my, the licence was revoked.
Any ideas....

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

[mattock808]

another vcds cable / with same version inside ATMEGA/ working in this PC

[ZIPPO4594]

I think FTDI is dead...

[hid3]

Yeah, seems so... But the ATmega part is faulty/failed also, cause he reflashed the firmware and still no LEDs illumination

[jan4]

does he have 5 volt on the atmega ??

[mattock808]

atmega side in now ok, green led shine

or PC not see cable

650769

[alexm1]

Open Dev manager- View-Show hidden devices- and plug / unplug your cable and look for a any device pop-up, if you have a device there , you have a driver issue. VID/PID.https://uploads.tapatalk-cdn.com/20190915/39d3446ed9676fd3edd086c390659b45.jpg

[FredrikO]

Are you sure you haven't swapped MOSI with MISO when connecting to the programmer?
Also, I'd suggest powering the chip via OBD2 12V circuit and do not power it from the 5V USBASP source (jumper removed)

I have tested to power it from OBD 12v also, but no luck. Will check MISO/MOSI today.

[DreamLand69]

I have very good news friends, the obd2cartool store and special thanks to Julie (great2obd) efforts, for all users of our forum there is a special link to 2 products with a big discount and free shipping DIY VAG / VAG V2 Choose option one or option two.
And now think for yourself what to buy: a quality product for a good price with a guarantee and technical support or shit with Ali.

Option 1:

Classic DIY ATMEGA162 + FT232RL + L9637D + 16V8B cable with Bootloader - 19.12 Euro


Option 2:

HEX-V2 DIY ATMEGA162 + FT232RQ + 9241 + 16V8B +ATA6561 cable with Bootloader - 26.97 Evro

https://www.obd2cartool.com/vip-customer-link-classic-v1hex-v2-diy-programming-cable-for-digital-kaos-members-p-1209?zenid=p6ha6dh7md91gh1jgm4016dpr2Euro

does anyone have a picture of the cable electronics? option 1. Thanks

[Roma77]

does anyone have a picture of the cable electronics? option 1. Thanks
inside he is
https://www.obd2cartool.com/vagcom-1684-full-active-vcds-1684-diy-vag-com-1684-can-reprogram-language-and-version-p-1266

[DreamLand69]

Ok Thanks!

[agzdzl]

Today tested Loader v9.2 and VCDS_RUS 19.6.1 at Tiguan 2015. Everything works great.

[robinbga]

Hello everyone,
I need help with my tool.
I bought a good quality Chinese clone that could work even with internet on n could update.
But when version 19.6.0 (which is done automatically) came out, the licence was revoked then functionality was hindered.
When the cable came, it came with its own loader v1.12.
So when it got revoked, I decided to use Kolimer's loader v9.2 but its never detected.
when I use the loader v1.12 i get good results, but when I start using the tool (vcds), it again gets revoked.
When I use Kolimer's loader v9.2, (Port status: ok, interface not found).
Please advise on what I should do.

Thank

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

[liviudiaconu]

In the archive where Loader 9.2, exist more files. One of them is Instructions..
Read it carefully.

[Lolo4321]

Hi does someone have a solution for the OBD2 male connector. When putting it in it feels so much tight compared to the Delphi DS150E connector. Does someone know where to buy the same connector like on Delphi to retrofit on Hex can ?

[blazzelia]

Hi,

I have an older VAG11.11 cable for which I attempted to upgrade the firmware and the eeprom using USBASP. I found some information describing how to detect the hardware version and successfully applied version 1.96 for flash and eeprom. VCSD 19.6 says the port is fine but the interface is missing.

The cable has an STC 12C2052 chip - I found information saying to cut pin 9 before usbasp programming and I did that. Some other information say I should remove the chip completely.

In any case, before programming I saved the old flash and eeprom. Now I tried to revert it back to the original version (1.84) but I'm getting the same message from VCDS 19.6 - port ok, interface missing (before fw upgrade used to detect it properly). I think I didn't pay attention to the original fuse and lock config for 162...

Anyway, there is anyone who can help me with some information so I could make it work after the upgrade or revert to the original setup?

Thanks,

B

[rak183]

Wich pid/vid has the interface? (Ftdi chip)

[hid3]

Hi does someone have a solution for the OBD2 male connector. When putting it in it feels so much tight compared to the Delphi DS150E connector. Does someone know where to buy the same connector like on Delphi to retrofit on Hex can ?

This one: https://www.ebay.com/itm/5X-Car-Black-OBD2-OBDII-16Pin-Male-Connector-Case-Housing-Kit-With-Screws-Plug/253524666878?fits=Make%3ACase&epid=10017261858&hash=item3b073f69fe:g:BjAAAOSwbYdauyOJ

Actually it is the same as R0$$ used on their older gen interfaces (Rev. A with FT232BL chip).
Challenge is finding who is selling those connectrs one by one, not in lots of 5 or even more.

[hid3]

Hi,

I have an older VAG11.11 cable for which I attempted to upgrade the firmware and the eeprom using USBASP. I found some information describing how to detect the hardware version and successfully applied version 1.96 for flash and eeprom. VCSD 19.6 says the port is fine but the interface is missing.

The cable has an STC 12C2052 chip - I found information saying to cut pin 9 before usbasp programming and I did that. Some other information say I should remove the chip completely.

In any case, before programming I saved the old flash and eeprom. Now I tried to revert it back to the original version (1.84) but I'm getting the same message from VCDS 19.6 - port ok, interface missing (before fw upgrade used to detect it properly). I think I didn't pay attention to the original fuse and lock config for 162...

Anyway, there is anyone who can help me with some information so I could make it work after the upgrade or revert to the original setup?

Thanks,

B

First of all, it is impossible to "back up" the firmware and EEPROM content in the conditions you have. What you expect to be a backup, is just a file with random numbers inside it (for curiousity, open it with HEX editor and see if all it contains is 00 01 02 03 ... 0A 0B ... FF FF)

Secondly, please firstly post high-res pics of both sides of your PCB in the shape it looks now.
From that point we can start making constructive comments.

[alexm1]

This one: https://www.ebay.com/itm/5X-Car-Black-OBD2-OBDII-16Pin-Male-Connector-Case-Housing-Kit-With-Screws-Plug/253524666878?fits=Make%3ACase&epid=10017261858&hash=item3b073f69fe:g:BjAAAOSwbYdauyOJ

Actually it is the same as R0$$ used on their older gen interfaces (Rev. A with FT232BL chip).
Challenge is finding who is selling those connectrs one by one, not in lots of 5 or even more.I think here we have the lowest price:

https://s.click.aliexpress.com/e/MHIVsXBS

[Jackson0]

Hi,

I have the attached VCDS HEX V2 clone and the CAN-Bus is not working anymore (Test Status CAN - not OK, K-Line says OK)

Firmware and EEprom is renewed and working, VCDS sayed activated after test.

What can I do? Possible problem with the GAL?

Regards,
Jackson

[Roma77]

Hi,

I have the attached VCDS HEX V2 clone and the CAN-Bus is not working anymore (Test Status CAN - not OK, K-Line says OK)

Firmware and EEprom is renewed and working, VCDS sayed activated after test.

What can I do? Possible problem with the GAL?

Regards,
Jackson
little information, software version, which loader, from which folder they were flashing. Which car passes the test.

[alexm1]

Hi,
Anyone have seen this error (pics below).
Laptop is a Acer win 10, x64

Bitdefender - dissabled

windows defender dissabled

The program starts only without loader. https://uploads.tapatalk-cdn.com/20190920/f44cf138288ac94308d95a842f18d77f.jpg

[blazzelia]

[QUOTE=hid3;3675234]First of all, it is impossible to "back up" the firmware and EEPROM content in the conditions you have. What you expect to be a backup, is just a file with random numbers inside it (for curiousity, open it with HEX editor and see if all it contains is 00 01 02 03 ... 0A 0B ... FF FF)

Hi,

Thanks for replying. You are right, the hex content is totally garbage ...

Anyway, using Kolimer's VCDSLoader V5 I was able to push fw 1.96. I connect the interface to the car, it start the auto-scan, it worked for a while, then it died in about 10 seconds.
Back home I was able to load 1.96 fw again, but I don't know what to do next. I attached the pictures of the interface.

Btw, the interface has STC chip on it...

Thanks,

B

[kaalis]

Read info.pdf from loader archive what to do with STC.

[blazzelia]

Secondly, please firstly post high-res pics of both sides of your PCB in the shape it looks now.
From that point we can start making constructive comments.

So I post the pictures. Cutting pin 9 as per Kolimer info.pdf didn't make any difference. As soon as the interface starts the auto-scan, it stops communicating with the interface after about 10 seconds.

So, to recap, maybe I'm missing something ... Fw 1.96 with VCDS 19.6.1. Is that right?

Thanks,

B

[alexm1]

About the cable in the pics, was working with v17.1.3 and after reflash the LED did not become green as it should(and it was was green before.

At first I did use -hw type- and was identified as x46, Bootloader dissabled, so I use usbasp programmer and after flashing kolimers last release, the led did not return to green. I use FUSE BITS: CD DA F9 CC FFF...

When use Options-Test- I get k1 k2 ok, can not ready(car was 2011 Passat).And I Can not connect to any module.


I tried too with a non-vag car and I can use with succes OBD Generic option to see real time data.

* I see now that FTDI has no marking at all on it ,migth be a clone , but it has nothing to do with programing Atmega.

Any ideea what could happen?

L.E. Led is not flashing Red, after reflashing Atmega, Led stays a second Orange and than goes RED and stays like that.

https://uploads.tapatalk-cdn.com/20190921/ede956e906e2ad07d0c91c427811c890.jpghttps://uploads.tapatalk-cdn.com/20190921/0bfdf5a654d95965c0f780d903a6c15b.jpg

[hid3]

So I post the pictures. Cutting pin 9 as per Kolimer info.pdf didn't make any difference. As soon as the interface starts the auto-scan, it stops communicating with the interface after about 10 seconds.

So, to recap, maybe I'm missing something ... Fw 1.96 with VCDS 19.6.1. Is that right?

Thanks,

B

Firmware 1.96 is the same for all since V(D$ 16.4 I think. It's EEPROM and loader what matters. Make sure you are using the latest package v9.2. Also, you can try with older VCD$ releases

[hid3]

About the cable in the pics, was working with v17.1.3 and after reflash the LED did not become green as it should(and it was was green before.

At first I did use -hw type- and was identified as x46, Bootloader dissabled, so I use usbasp programmer and after flashing kolimers last release, the led did not return to green. I use FUSE BITS: CD DA F9 CC FFF...

When use Options-Test- I get k1 k2 ok, can not ready(car was 2011 Passat).And I Can not connect to any module.


I tried too with a non-vag car and I can use with succes OBD Generic option to see real time data.

* I see now that FTDI has no marking at all on it ,migth be a clone , but it has nothing to do with programing Atmega.

Any ideea what could happen?

L.E. Led is not flashing Red, after reflashing Atmega, Led stays a second Orange and than goes RED and stays like that.



One stupid idea on this.
First of all, yeah, FTDI chip is fake. Replace it on first opportunity.
Secondly, I assume 17.1.3 came from China. It is possible that they used their own firmware so everything worked "its own way". After reflash you flashed original firmware and it started working as it should.
Since the LED is in different package than usual, I suspect such a simple thing as LED soldered incorrectly - mixed green and red LEDs. Use multimeter to trace which ATmega pins each LED connects to.

Finally - this is 0x44 HW. Use 0x44 flash and corresponding fuses.

[Nullos007]

Hello, i try coding on my leon st MY20, all work like a charme !

VCDS 19.6.1 + Loader 9.2

Thanks for the work ! :-)

[alexm1]

I was looking closelly at smd led and I see that it is bi color- red and green.
Conection to Atmega looks like in the edited photo.

I did tried with x44 dumps with coresponding fuse bits, same story.https://uploads.tapatalk-cdn.com/20190921/48988b271aa04bf2290bd6eb5d943166.jpg

[hid3]

Here we go. Custom pinout, probably for custom firmware. You have 3 pins used - 26, 27 and 28. In reality, only two should be used - 27 and 29, as there are only red and green LEDs as per original design. Pin 27 - green, Pin 29 - red <- that's how it should be.

[alexm1]

Meanwhile....having anything better to do I replaced Atmega.
Offcourse you was rigth....same color on led.
With x44 dumps inside, tomorow I will give a try testing on a car. I will reply after.
Thank you Hid3!

[alexm1]

One stupid idea on this.
First of all, yeah, FTDI chip is fake. Replace it on first opportunity.
Secondly, I assume 17.1.3 came from China. It is possible that they used their own firmware so everything worked "its own way". After reflash you flashed original firmware and it started working as it should.
Since the LED is in different package than usual, I suspect such a simple thing as LED soldered incorrectly - mixed green and red LEDs. Use multimeter to trace which ATmega pins each LED connects to.

Finally - this is 0x44 HW. Use 0x44 flash and corresponding fuses.I tried today having x44 dumps and fuse bit set properlly with usbasp:
k1 k2 ok
Can not ready
No module can be accesed.
It is something that I missed?

[flavyus1987]

Check ATxxxx or MPCxxxx, that controlers are responsable with CAN comunication.

[liviudiaconu]

If connect the same pin on both pins of a LED, nothing happend Understand?
Your RED LED seems to be connected with both pins on 26. ????!!!!
This is about your draw where dual-led seems to have common pin on the left or on the right of draw.


I was looking closelly at smd led and I see that it is bi color- red and green.
Conection to Atmega looks like in the edited photo.

I did tried with x44 dumps with coresponding fuse bits, same story.https://uploads.tapatalk-cdn.com/20190921/48988b271aa04bf2290bd6eb5d943166.jpg

[alexm1]

I will check one more time today, now I searched for bi color smd led pinout... and my draw has no logic.
Probablly I switched 26(from rigth side) with 27.

[blazzelia]

Firmware 1.96 is the same for all since V(D$ 16.4 I think. It's EEPROM and loader what matters. Make sure you are using the latest package v9.2. Also, you can try with older VCD$ releases

You were right again. With loder 9.2 it worked justfine.

Thanks,

B

[alexm1]

If connect the same pin on both pins of a LED, nothing happend Understand?
Your RED LED seems to be connected with both pins on 26. ????!!!!
This is about your draw where dual-led seems to have common pin on the left or on the right of draw. My bad, I did not count corectlly.
Now it is 100% reall data.
Ground-28
Red -27
Green -29


So, when I power on at 12v: for 3 seconds I have both color ON (green and red) , after that stays green goes off, only the red will sta ON .

When LED is On, between 28 and 27/29 I have 1.9 volt.
https://uploads.tapatalk-cdn.com/20190923/4f803cf61c888da82cd69ee1cf79cf2b.jpg

[hid3]

Since you double checked & confirmed, I can say for sure that the LED colours are reversed. 27 should be green, 29 should be red. Yours is vice-versa, that's why you have red LED when the interface state is "OK/ready"

[alexm1]

Yes, but , this is not a problem, I could do some tricks to revers the colors.

But that means the circuit could be changed and some other points and migth not work with this dump, rigth?

[hid3]

But that means the circuit could be changed and some other points and migth not work with this dump, rigth?

Very difficult to say - efforts to reverse engineer all the circuit will beat the price of a new cable. Does K-Line at least work on this interface?

[alexm1]

Since I managed to connect to a NON Vag car , using Obd Generic function, I think k line is ok...

[alexm1]

Found a USB to TTL Serial Adapter with an FT232RL probablly fake too, I ve soldered on the cable to see whats happening...
First I manually instaled driver, so in Dev Manager I have "Ross.....hex key usb..."

Now, I can not reprog this FTDI, I tried with Mprog, after Scan(Blank device 1)-Open file- Program - I get Programed Serial Number- A50285BI
Next - Read- but I see same EEPROM content(....U.S.B. U.A.R.T......) as before programing

Vid/pid 0403/6001

Tried again with FT_PROG same story.
https://uploads.tapatalk-cdn.com/20190923/8b1855745205b6af99fc72f109aabbd1.jpg

[hid3]

Doh :( I can see correct VID and PID but the description is definitely not right... Most likely some semi-read-only chip :(

[kssj0001]

There are still some vehicles that are not supported，like T-ROC，show "unsupported vehicle"

[Tib82]

Hi mates :)
Today I got this old cable, and I would like to update it via USB ISP because the bootloader is disabled on it.
654241654242

So R50's wire cutted and I connect all the wires like below, except the GND what was connected into the 7805 back.
654243

After plug in the USB programmer the intercafe's LED started to blink red, so something was wrong.
I was curious so I pushed the ProgISP RD button and it said the chip was read successfully. Windows can recognise cable in the Program Manager.

So my question is what did I wrong, why the red blinking happens?
Thanks for the helping words :)

[hid3]

I faced same situation several times on the cables similar to yours.
One of the reasons for that may be undervoltage. Try powering the board off OBD2 side via 12V power source, not from programmer.
If still problem - desolder STC completely but leave R50 in place.
Erash ATmega, flash with correct dumps and FUSE bits - yours is HW 0x46

[Tib82]

... One of the reasons for that may be undervoltage. Try powering the board off OBD2 side via 12V power source, not from programmer.
If still problem - desolder STC completely but leave R50 in place. Erash ATmega, flash with correct dumps and FUSE bits - yours is HW 0x46
With 12V the situation is the same :( so tomorrow morning I will try to remove STC from the PCB and I'll report what's going on :)

[moffo]

Hello all user,I have request everything can help me.
I have clone vcds actually 18.9.0 German Version,run perfectly with kolimer,now will update my software on higher 19.6.X German version,can anything tell me what I’m must doing and who find this software including Kolimer?
In advance thank you very much


Gesendet von iPhone mit Tapatalk

[jan4]

you got pm !!

[rak183]

moffo has exceeded their stored private messages quota and cannot accept further messages until they clear some space.

[bmw318isblack]

Very interesting thread to read - still a few houndred pages to go - but with many good ideas :) like this one:


I created a booth for checking and repairing scanners yesterday, it turned out great, I bought a CAN from the Passat B6 ($ 9), picked up an old battery from a laptop for three 18650 batteries (lay just like that for me) soldered crocodiles, I recommend it to anyone who needs offline testing (on the table)



And god bless you all

B.

[Tib82]

With 12V the situation is the same :( so tomorrow morning I will try to remove STC from the PCB and I'll report what's going on :)
So R50 cutted, programming wires connected, right HW type (GAL-AT162 chacked) pushed into the cable... after programming it's blinking red. I should remove STC, but I think a hot air gun is required for it (because of the multiple legs) and I"ve got an old fashioned soldering iron. So the STC is leaved on the PCB and I take a try and test it on the HWType. FW and HW type recognised, but nothing else (no loader, bootloader state, etc.). It's not very encouraging situation... but let's try it vith the \/(D$ and test it... And it worked! :)
What is your opinion, why the HWType cannot see the full details of the cable? Because of th STC on the board?

[bmw318isblack]

Hi Tib82,

for removing a chip you still have 2 alternatives

- just simply cut the legs (with something sharp- https://www.youtube.com/watch?time_continue=244&v=L1T8_Vjjrws - :) )
- or use low melt solder removal alloy like Chip Quik (you can find videos on YouTube )

There is no hot air gun required.

B.

[hirez]

Hi,

I have a atmega 162 obd2 china cable that I have paired with a 2019 skoda octavia. It came with modified software and loader 1.12. In the beginning it was activated, but i never used it to do much other than scan and read coding as I had little time to do any "real work".
When I got around to attempting some work on the car with the cable I must have used unmodified software or something as the interface would not work anymore. the software said it was unregistered and the car unsupported and completely useless. At the time I thought my cable was older and my car too now and I did not find any 'fix' for my problem.
However a recent search has lead me here and renewed my hope of some fun with my interface. Here are the details:
I have this cable654811654812

HWtype gave this info: 0x46 with bootloader enabled
654828

So it would seem I don't need a programmer. (I am just a little disappointing as I was looking forward to a little soldering fun :P) Although the board is of a layout I have not seen in any of my searching. Is anyone familiar with it?

So just to be sure I am good to go, and with kolimer vsds loader v9.2 and VAGCOM_EEWriteLang.exe I can reflash and run the latest 19.6.1 with the included loader?

[Lolo4321]

yes u can run 19.6.1 with Kolimer V9.2 and re-flash. Your cable needs to be plugged in or connected do 12v just follow the pdf guide.

[liviudiaconu]

@ hirez: But..you have in fact hw44 cable.

[winamax69]

@ hirez
right HW type GAL-AT162 chacked? When GAL connected to the Atmega162, then you have a HW44 type cable.

[hirez]

@ hirez: But..you have in fact hw44 cable.


OK, I thought so looking at the PCB, but was not sure. Is that good or bad? But the HWtype tool shows it as 0x46 so I just though that should be right.
Either way the EEflash will auto detect and flash the correct firmware?

[Tib82]

@ hirez
right HW type GAL-AT162 chacked? When GAL connected to the Atmega162, then you have a HW44 type cable.
Both type's ATmega162 microcontroller connected to the GAL chip, but the difference is the number of the connected pins. In the case of HW 0x44 type pin 34-35-36-37, while in the case of HW 0x46 type only pin 36-37 are connected to the GAL.


OK, I thought so looking at the PCB, but was not sure. Is that good or bad? But the HWtype tool shows it as 0x46 so I just though that should be right.
Either way the EEflash will auto detect and flash the correct firmware?
No worries about it, just plug it into your car and into your laptop, ignition on (for 12V), and run the \/AG(0M_EEWr!teL@ng app :) and it will do the rest of the job :)

[hirez]

Both type's ATmega162 microcontroller connected to the GAL chip, but the difference is the number of the connected pins. In the case of HW 0x44 type pin 34-35-36-37, while in the case of HW 0x46 type only pin 36-37 are connected to the GAL.


No worries about it, just plug it into your car and into your laptop, ignition on (for 12V), and run the \/AG(0M_EEWr!teL@ng app :) and it will do the rest of the job :)


Thanks!
I will check the pins. It never hunts to be thorough, and I would rather not break anything.

so... autoflash, run loader9.2 on original fresh 19.6.1, play at will?


Edit: just checked and like the PCB would indicate, the PA0, PA1,PA2,PA3 pins are indeed connected to my PALCE16V8. That is a 0x44 and a good thing? :)

Also: Does it mean anything important that my PID reads FA20 and not FA24?

[liviudiaconu]

OK, I thought so looking at the PCB, but was not sure. Is that good or bad? But the HWtype tool shows it as 0x46 so I just though that should be right.
Either way the EEflash will auto detect and flash the correct firmware?

1. For correct functionality must write correct version of Fw and EEPROM.
Must use USB ISP programmer.
2. The response 0x44 or 0x46 is about Fw already wrote in AT162. Not hardware respond 0x44 or 0x46.
So if you have in your Hw44 wrote Fw46 will see "0x46". Not OK.
But, only for test your cable can use EEWriter.

[robinbga]

Can't someone come up with a video of how to flash and share it to those who need it like me n hirez, the video should show how to use Kolimer's loader and other flashing tools like eewriter etc.
I would help a lot.
I had the same problem but I ended up using the same loader v1.12.
However, Hires if u contact me, I will share with u what I did to solve mine bcoz I have a similar cable.
I would prefer to use Kolimer's loader v9 due the it functionality, I looked at how it loads vcds and all I can say is its genius.
Keep it up

Cheers
Robin B

WhatsApp: +256752474714
Skype: robin_bga83

Kess V2 . K-Tag
MiniPro . UPA . VVDI2
https://uploads.tapatalk-cdn.com/20190930/babc7be0c36d3d4b44ab2b24cf283de3.jpghttps://uploads.tapatalk-cdn.com/20190930/45684f6d57b6dc53a77fba6c56344ecb.jpg

[Lolo4321]

Is your bootloader unlocked ?

[robinbga]

Yes

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

[Lolo4321]

Ok,
First step:
Plug in the HEX CAN cable into the laptop
Install Ross Tech software downloaded from their site 19.6.1 (HEX CAN must be plugged in during installation)
-( During install accept installation of drivers)
Don't open VCDS after install.
Go into you car and plug in the HEX CAN cable ( Ignition on)

Open Kolimer v9.2 folder
Run VAGCOM_HWType.exe - to confirm that your bootloader is unlocked
After that run
VAGCOM_EEWriteLang.exe
(HEX CAN must be plugged into the car, or supplied 12 V on the bench setup)

after that Open the directory in which u installed Ross Tech software
Copy the loader from Kolimer V9.2 folder into the Ross tech directory
VCDSLoader.exe - Right click on it and -> Send to desktop.
Close all folder, and run VCDSLoader from desktop
enjoy

[robinbga]

I tried that at some point and its refused to be detected by 19.6.1.
I did exactly that.
When I opened eewritelang, I selected English I think 0x46 bcoz the original loader said that.
It failed to work

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

[Lolo4321]

I tried that at some point and its refused to be detected by 19.6.1.
I did exactly that.
When I opened eewritelang, I selected English I think 0x46 bcoz the original loader said that.
It failed to work

Kess V2 . K-Tag


MiniPro . UPA . VVDI2

Uninstall all software and remove Hex Can from hardware...
Than try again.

[robinbga]

Uninstall all software and remove Hex Can from hardware...
Than try again.I really don't know what u mean, remove hex can from hardware.

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

[skydoy]

Loader v9.2 released! It improves compatibility with non English versions and VCDS 19.6.0 version.

http://ge.tt/6I9tkOx2
https://www101.zippyshare.com/v/biPvu9Lt/file.html
https://www.sendspace.com/file/5qr55f
https://uptobox.com/l96rbs2lo9h6

Kolimer ......

Dear Kolimer

The 19.6.2 Is out, Did you noticed? I´m eager to test the new version on my Car to see if im lucky :D

[hirez]

Can't someone come up with a video of how to flash and share it to those who need it like me n hirez, the video should show how to use Kolimer's loader and other flashing tools like eewriter etc.


I don't see a need for a video. The given instruction and info here are more than sufficient.

But I did just see a new post stating the the cable should be plugged in when installing the 19.6.1software. This I did not do and it seems to work fine so not sure it is necessary.

[hirez]

1. For correct functionality must write correct version of Fw and EEPROM.
Must use USB ISP programmer.
2. The response 0x44 or 0x46 is about Fw already wrote in AT162. Not hardware respond 0x44 or 0x46.
So if you have in your Hw44 wrote Fw46 will see "0x46". Not OK.
But, only for test your cable can use EEWriter.

this means i have the wrong firmware for my hardware (cable)? then should i do a manual write and make sure to select the 0x44 flash? I have not tried it yet as I want to get as much confirmation I have the right hardware/software as not to screw anything up:)
also should i have FA24?

[Roma77]

Can't someone come up with a video of how to flash and share it to those who need it like me n hirez, the video should show how to use Kolimer's loader and other flashing tools like eewriter etc.
I would help a lot.
I had the same problem but I ended up using the same loader v1.12.
However, Hires if u contact me, I will share with u what I did to solve mine bcoz I have a similar cable.
I would prefer to use Kolimer's loader v9 due the it functionality, I looked at how it loads vcds and all I can say is its genius.
Keep it up

Cheers
Robin B

WhatsApp: +256752474714
Skype: robin_bga83

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

there is a video, you just need to read to find it # 8271 (https://www.digital-kaos.co.uk/forums/showthread.php/99750-VAG-COM-VCDS-EVERYTHING?p=3574522&viewfull=1#post3574522)

[Roma77]

Dear Kolimer

The 19.6.2 Is out, Did you noticed? I´m eager to test the new version on my Car to see if im lucky :D
English 19.6.2 works with the loader 9.2, everything is ok.655022

[liviudiaconu]

[...]
But I did just see a new post stating the the cable should be plugged in when installing the 19.6.1software. This I did not do and it seems to work fine so not sure it is necessary.

No need plugin usb. Mandatory not.


this means i have the wrong firmware for my hardware (cable)? then should i do a manual write and make sure to select the 0x44 flash? I have not tried it yet as I want to get as much confirmation I have the right hardware/software as not to screw anything up:)
also should i have FA24?

That mean you must use an external programmer.
I said: only for test, you can use EEWriter..
But for sure, for further use is necesary write Fw1.96 hw44 and eeprom 44 inside.


@Roma77: made too few adaptations and LONG CODING operations?

Because Options->Test->OK->About->Green serial not mean all ok.

[Lolo4321]

But I did just see a new post stating the the cable should be plugged in when installing the 19.6.1software. This I did not do and it seems to work fine so not sure it is necessary.

Well if it's the first time, and cable has fw on it.
This happened to me, but a friend from forum helped me fix it. ( I didn't plug in the cable during install...)

[moffo]

moffo has exceeded their stored private messages quota and cannot accept further messages until they clear some space.

Space free my friend ;-)


Gesendet von iPhone mit Tapatalk

[skydoy]

English 19.6.2 works with the loader 9.2, everything is ok.655022

I Instaled the vcds 19.6.2 but when i place the crack says the version is 19.6.1 and is outdated

[skydoy]

My Mistake Solved the issue :D

[vmcs22]

Hello there,
655149655150655151655152
I have this 16.8.3 cable, it came with a CD, which has a EN and CN 16.8.3 installer and a RT-USB.dll file on it. I use it with the EN 16.8.3 version, and it works perfectly.
However, when I try to use v9.1 eewritelang.exe, it says Invalid Bootloader, and won't write eeprom.
My question would be if my cable is capable of updating or not?

Thanks for your answer!

[gini80]

yes it can be updated

[vmcs22]

If so, what are my options?
Do I have to flash atmega chip too? Why does it say "invalid bootloader"? Has anyone ever encountered this problem?
I already did the FT232RQ chip with Mprog, although I didn't have to, because it said RT000001. I don't have usbasp programmer, only ch341a, which is not compatible I think.

[hid3]

You need to reflash ATmega. Yours is HW 0x46. It says pretty straight forward - bootloader is invalid.

[skydoy]

Still no luck with 19.6.2 With My Car
but The 9.2 Loader works like a charm in 19.6.2

[rak183]

Wich hardware type is this interface.
https://www.obd2cartool.com/atmega162-vag-com-178-vagcom-178-full-active-enfr-vag-hex-can-crack-cable-p-1516?zenid=m9sgic1oflh6tdilehb116vdh7