VAG-COM/VCDS EVERYTHING

[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.

[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.
cable1.jpgcable2.jpg

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

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_c...&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 cableDSC_0316.JPGDSC_0313.JPG

HWtype gave this info: 0x46 with bootloader enabled
VCDSLoaderv9.2 HWinfo2.jpg

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?