[bmwadriatic]

Any experience with interface from post 204? Really so good? Works it with official German version ? (DRV)

[darek_naprawa]

It is very cheap, so you do not risk much.
Works with the official version.

[bmwadriatic]

Is it best clone at moment ?

[valdirld]

Hi, i have HW46 interface, upgraded by upa-usb, all is ok, but says not plugged into car, but i am connected to the car, wath can be wrong?

[darkdll]

Hello, I have this cable with the old 11.11 and I would like to update it, I have used the program VAGCOM_HWType but it does not recognize it, I leave some photos here to see if I can reprogram it.

   
   
   
   
   

Some chip info:

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

I also have this USB programmer for my projects in arduino, would it be used to reprogram the cable?

Hrph 3.3V 5.5V FT232RL FTDI Usb a TTL
   

Thanks =) and good work in this post!

EDIT:

OK after read and test:

Programmed FTDI with success:

1) Opened MProg 3.5 and clicked on Device -> Scan.
2) Number of Programmed Devices = 1
3) Tools -> Read and Parse
4) File -> Save (Save backup)
5) File -> Open and load "ftdi_mprog_RLRQ.EPT"
6) Device -> Program

Now VAGCOM_HWTYPE.exe works

Updated firmware with VAGCOM_EEWrite.exe

Installed latest VCDS (18.1.0), update firmware to latest

Used loader and first test, all working OK!

Autoscan OK at first...

FAIL in middle of autoscan.

I close all windows and restart windows itself.

Now cable led is flashing in red, when I try to access it with VCDS or VAGCOM_HWTYPE.exe led freeze in red color.

In VCDS: Interface found but Not plugged into Car!

   

I've done something wrong? now i can't reflash it nor use it

[BWF]

I think it is for vcds18.1
Vcds 17.8.1 works well

Enviado desde mi Redmi 3 mediante Tapatalk

[darkdll]

I think it is for vcds18.1
Vcds 17.8.1 works well

Enviado desde mi Redmi 3 mediante Tapatalk

I think not, I downloaded version 17.8.1 and the same error occurs, the problem is not only VCDS, "VAGCOM_HWType.exe" doesn't read the values either.

[tomaxsas]

I think you should not use 18.1 version of vcds in first place, now your interface may be bricked.

[darkdll]

I think you should not use 18.1 version of vcds in first place, now your interface may be bricked.

Can I reflash it using USBasp programmer? Or reset status?

EDIT: Ok, read in another forum:

Current version: Release 18.1.0 Data Version 20180122

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.

   
   

So a new USBasp programmer is coming on eBay

[gyenge]

I cannot install vcds 17 on windows XP . got an error "the specified location does not contain information about your hardware"?

Someone knows why?