[Jono]

With Mprog you can program the ftdi chip.
Program the Atmega again with good FuseBits.

Install official VCDS version 17.3.1, 17.8.0.
Use the good loader.

Regards

[barto39]

With Mprog you can program the ftdi chip.
Program the Atmega again with good FuseBits.

Install official VCDS version 17.3.1, 17.8.0.
Use the good loader.

Regards

Thanks for answering
I try to run my interface and I can not
Any tutorial to program ftdi chip, for my interface ??
This programmer is good to program ftdi chip
http://www.ebay.es/itm/FTDI-FT232RL-USB-...OSwH1NZfJr-


Thank you

[Jono]

Put your VCDS cabel in the computer.
Start Mprog and scan in the program to find your cabel.
Then load your file out the directery Template and program your cabel.
You have nothing to by.
Don't remove the jumpers from the PCB

Regards

[barto39]

Put your VCDS cabel in the computer.
Start Mprog and scan in the program to find your cabel.
Then load your file out the directery Template and program your cabel.
You have nothing to by.
Don't remove the jumpers from the PCB

Regards

Hello
Thank you for helping
I commented the steps: first flashing without removing pin 34 and 35 from atmega, to run with vcds VCDS-Release-14.10.2-SPA
When I install vcds VCDS-ROJ-17080-Installer 20170818 I stopped detecting the interface
Second: try to flash interface with pin 34 and 35 removed perfect but does not detect the interface
Look at the photo with interface connected to the pc and does not detect, try on other pc and nothing
Check the cables and they are OK (sometimes it detects, but only a second and disappears)
Someone says that you should remove the atmega chip from the interface and try !!!! (now only pin 34 and 35 is removed)
My question is: may, after first falsifying first without removing pin 34 and 35 and trying another vcds to stop the driver and it is blocked and in my case the interface can not be repaired ?????
thanks to all

[uh60]

I have 3 cables at here, one FTDI232BL chip, the other with RQ, I use external prog for the BL one, works great now, RQ also okay, however, there is an issue with the software 17.8.0, when I put it on bench and go to airbag it detects the faults incorrectly and gives oxygen sensor fault, when 17.1.3 is used - no problem. Anyone else having hte same issue and knows how I can get in touch with Kolimer to say thanks ?

---

Put your VCDS cabel in the computer.
Start Mprog and scan in the program to find your cabel.
Then load your file out the directery Template and program your cabel.
You have nothing to by.
Don't remove the jumpers from the PCB

Regards

Hello
Thank you for helping
I commented the steps: first flashing without removing pin 34 and 35 from atmega, to run with vcds VCDS-Release-14.10.2-SPA
When I install vcds VCDS-ROJ-17080-Installer 20170818 I stopped detecting the interface
Second: try to flash interface with pin 34 and 35 removed perfect but does not detect the interface
Look at the photo with interface connected to the pc and does not detect, try on other pc and nothing
Check the cables and they are OK (sometimes it detects, but only a second and disappears)
Someone says that you should remove the atmega chip from the interface and try !!!! (now only pin 34 and 35 is removed)
My question is: may, after first falsifying first without removing pin 34 and 35 and trying another vcds to stop the driver and it is blocked and in my case the interface can not be repaired ?????
thanks to all

About pin 34 and 35 , what are these that you are referring to , with the pony prog you should be able to program a 10.6.4 cable without any problem, can you give photos of both parts of your board ?

[barto39]

Hi guys
thanks to you, I update several cable vag by usb and another one with usbasp (Thanks DTech, fantomel for your tutorials)
The other cable vag 17.1 that gives me problem after updating and the pc does not detect the interface
Find problem: FTDI FT232RL is deprogrammed or blocked
Testing with usbview:
Device Descriptor:
bcdUSB: 0x0000
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x00 (0)
idVendor: 0x0000
idProduct: 0x0000
bcdDevice: 0x0000
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x00

ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
My question, can you reprogram FTDI FT232RL and what are the steps to reprogram ???
Thank you

[rch11]

Hi guys
thanks to you, I update several cable vag by usb and another one with usbasp (Thanks DTech, fantomel for your tutorials)
The other cable vag 17.1 that gives me problem after updating and the pc does not detect the interface
Find problem: FTDI FT232RL is deprogrammed or blocked
Testing with usbview:
Device Descriptor:
bcdUSB: 0x0000
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x00 (0)
idVendor: 0x0000
idProduct: 0x0000
bcdDevice: 0x0000
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x00

ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
My question, can you reprogram FTDI FT232RL and what are the steps to reprogram ???
Thank you

Try this

[barto39]

Hi guys
thanks to you, I update several cable vag by usb and another one with usbasp (Thanks DTech, fantomel for your tutorials)
The other cable vag 17.1 that gives me problem after updating and the pc does not detect the interface
Find problem: FTDI FT232RL is deprogrammed or blocked
Testing with usbview:
Device Descriptor:
bcdUSB: 0x0000
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x00 (0)
idVendor: 0x0000
idProduct: 0x0000
bcdDevice: 0x0000
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x00

ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
My question, can you reprogram FTDI FT232RL and what are the steps to reprogram ???
Thank you

Try this

Thanks for answer and help rch11
My pc and two other PCs I have at home does not detect the interface (sometimes it detects it but for 2 seconds)
When I power the 12V interface, the green light
I think the FTDI is deprogrammed and when it is deprogrammed the pc does not detect the interface

Thank you all

[rch11]

Hi guys
thanks to you, I update several cable vag by usb and another one with usbasp (Thanks DTech, fantomel for your tutorials)
The other cable vag 17.1 that gives me problem after updating and the pc does not detect the interface
Find problem: FTDI FT232RL is deprogrammed or blocked
Testing with usbview:
Device Descriptor:
bcdUSB: 0x0000
bDeviceClass: 0x00
bDeviceSubClass: 0x00
bDeviceProtocol: 0x00
bMaxPacketSize0: 0x00 (0)
idVendor: 0x0000
idProduct: 0x0000
bcdDevice: 0x0000
iManufacturer: 0x00
iProduct: 0x00
iSerialNumber: 0x00
bNumConfigurations: 0x00

ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
My question, can you reprogram FTDI FT232RL and what are the steps to reprogram ???
Thank you

Try this

Thanks for answer and help rch11
My pc and two other PCs I have at home does not detect the interface (sometimes it detects it but for 2 seconds)
When I power the 12V interface, the green light
I think the FTDI is deprogrammed and when it is deprogrammed the pc does not detect the interface

Thank you all

See what pid and vid you have.

[Jono]

Perhaps your USB cable is defective.
Try another cable.

Regards