VAG-COM/VCDS EVERYTHING

[hid3]

You can get a donor cable for GAL
Sometimes I say "keep this cable for spares" for cables with NEC chip etc.
So a perfect example when you need a spare.

A new/quality cable from Obd2CarTool's shop is around $24 shipped worldwide, so one might consider if it's worth the effort "to give it last chance".

K-lines are used on old(er) cars, which did not have CAN.
Honestly, I don't have a single car with K-lines, nor any of my friends do.

[Domi]

Gal its for dual K line
http://www.digital-kaos.co.uk/forums...p/t-97550.html

[oddyutza]

well i have updated my 12.12 cable using usbasp and 0x44 firmware, all went good
i've installed VCDS 17.8.0 and extracted kolimer 6.3 loader in c:\ross-tech\vcds folder

There are no drivers installed, and the new "cable" shows un device manager as " Ross-Tech HEX-USB "
vcds started with loader does not prompt for firmware update and on the test screen shows:
Ross-Tech USB interface not found
USB Library Version: 03.02.07
Interface not found

Shall i do something else besides usbasp > new vcds version installation > kolimer and start?

Please advise

Regards

[hid3]

So there were drivers installed or not?
What are VID & PID IDs in device manager when you conenct the interface?

[oddyutza]

under XP the drivers were installed and the device name is : Ross-Tech Direct USB interface
VID=0403
PID=FA30

any thoughts?

[hid3]

PID=FA30??

You need to correct it to PID=FA20 is it's 232BL and FA24 if it's RT232R* chip inside.

Is this was a typo, then watch in device manager what happens when you plug the cable in. Does it get detected properly and appears in dev manager without any exclamation marks?
Also, why didn't you use latest version of \/CDS?

[oddyutza]

Not a typo, how to correct the pid?

[hid3]

Use Mprog. In Kolimer's pack there are prepared files:
ftdi_mprog_BMBL.ept
and
ftdi_mprog_RLRQ.ept

For interfaces with BL/BM chips, use first one, for RL/RQ, use 2nd. This is very easy.

[oddyutza]

here's the view from linux
will do the Mprog part
[ 58.772080] usb 1-4: new full-speed USB device number 7 using xhci_hcd
[ 59.325790] usb 1-4: New USB device found, idVendor=0403, idProduct=fa30
[ 59.325792] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 59.325794] usb 1-4: Product: Ross-Tech HEX-USB
[ 59.325795] usb 1-4: Manufacturer: Ross-Tech

LE: Mprog done, looks good on the bench, have to figure out with the latest version and windows 10 will provide feedback and beer in the end

Thanks so much

regards

[hid3]

Oh, yeah, a mistake for sure
BTW, if you'd post the pics of the PCB, it would be possible to tell you exactly which ept file to use.

[guyguy307]

hello friend i search for testing loader 6.3 to kolimer i have read lot off page in this thread but i find only 6.1


thanks you

[Mario6]

hello friend i search for testing loader 6.3 to kolimer i have read lot off page in this thread but i find only 6.1


thanks you

Kolimers V6.3 loader is on page 389 post 5823.

[oddyutza]

Oh, yeah, a mistake for sure
BTW, if you'd post the pics of the PCB, it would be possible to tell you exactly which ept file to use.

Already used mprog all fine in the test on the bench using windows xp(old piece of hardware lying arround)

I've already uploaded pics with the pcb a few pages back, i can do it again if needed

[hid3]

Your hardware is HW 0x44, you should be using that dump.
For Mprog, use RL/RQ file.
In fact, you need to set correct VID/PID settings

[lion83]

I think I just bricked an HW 0x46 cable. The cable never worked properly, so I decided to flash it using VAGCOM_EEWriteLang.exe. First I used VAGCOM_HWType.exe to detect it and it confirmed hw type 0x46, chip ATmega162 + FT232RL (confirmed by opening the cable). I connected the cable to the OBD2 port of the car, led turned green, start flashing with EEWriteLang but after a while it has thrown out errors and the interface remained stuck with red led. Now when I connect the cable to the laptop it gets detected as Ross-Tech USB interface but if I connect it to the car the led remains red and HWType does not detect any interface. VCDS also does not detect any cable.

Did I just lose my cable or can I re-flash it using an usbasp programmer? The cable does have a programming header pin so it should be easy to do.. but before I go ahead and buy an usbasp programmer I wanted to know if I stand a chance or if I should just buy a new cable.