VAG-COM/VCDS EVERYTHING

[tucano79]

Change bouth l9637d

Thank you I'll but it and I'll try

[jakuza]

Does anybody can share GAL16V8 dump for VCDS with FTDI RL chip?
It look like different then for VCDS with FTDI BL?

This have been resolved long time ago. GAL dump is always the same, regardless FTDI.

[jakuza]

VID/PID does not change, this means the FTDI is not affected. The status LED is green always. Shows this error.
Also the same with HW44 and HW46, and with RL and BL.
Afterwards, Atmega can not be rewritten via USB, only with an external programmer.
We will be waiting for the Kolimer step

Maybe it will help a little. I compared the EEPROM readed after a fault with the working.
FLASH not changed.
Attachment 502094Attachment 502116

As I see program changed EEPROM but did not change CHECKSUMS. That means that every test it will show not plugged into car-because of wrong checksum.
Also, obviously if wrong checksum was written than it can not be rewritten using USB. Maybe this cheksum check can be avoid so Atmega can be rewritten regardless earlier EEPROM...

[liviudiaconu]

This have been resolved long time ago. GAL dump is always the same, regardless FTDI.

Are you sure 100%?

[magadan]

GAL dump is always the same, regardless FTDI.

Files "*.jed" is differ. Logic of operation of these chips different. But differences is minimum therefore chips work correctly sometimes.

PS
I wrote about GAL-ATF chips for adapters with a firmware 44 and 46. It not for adapters with chips of FT232B and FT232R.

[mattock808]

hi , for cable HEX-V2 is the same version program and drivers as HEX-CAN cable ?
thnks

[xoom]

hi , for cable HEX-V2 is the same version program and drivers as HEX-CAN cable ?
thnks

drivers depends on what hardware is.. make photos if can't setup drivers

[kaalis]

Do you mean fake V2 clones 17.8? They are quite similar with the main parts to the 17.1.x

[mattock808]

with czech version 17.1.3 , quite often an alert will pop up : This feature is only available with the original and activated HEX-xxx cable

which can cause this problem?

[networkers]

which can cause this problem?

Maybe read Pages around 336 to 338 in this thread.

[mattock808]

thanks, i read page 336-338 , i did not find the answer ....

if I shut down program and start again work some time works well.

[networkers]

thanks, i read page 336-338 , i did not find the answer ....

Don't understand me wrong, but the main statement is: This hardware is not very good and not recommended.

[kaalis]

This happens with 16.8 an 17.x cables (tend to loose licence status) that has NEC D79F... chips. Reconnecting cable from car and computer or using special utility program reset usually helped till next time after couple minutes Just my observations...

[darkdll]

Better do not try this version!
I have tried - damaging the cable. Shows that everything is activated, trying to work correctly and after a few seconds writes that the cable is not connected in the car. And after that the VAGCOM_EEWrite.exe also does not recognize it!

I fixed it only with an external programmer.

VID/PID does not change, this means the FTDI is not affected. The status LED is green always. Shows this error.
Also the same with HW44 and HW46, and with RL and BL.
Afterwards, Atmega can not be rewritten via USB, only with an external programmer.
We will be waiting for the Kolimer step

Maybe it will help a little. I compared the EEPROM readed after a fault with the working.
FLASH not changed.
Attachment 502094Attachment 502116

The same happened to me using v18, in my case interface HW46 with:

MCP2515 130482J
MCP2551 SN1308
ATMEL ATMEGA 162 16AU
FTDI 1240 C FT232RLHW

LED flashes red until attempted use, device freezes when this occurs

Same message

connect.jpg

A video:



I bought a programmer and I'll try to reprogram it.

[Domi]

LED flashes red = Bad Flash FW