We've seen a couple of threads recently where a map download has crashed part-way through and appears irrecoverable
A strong caution on taking a careful look at what cable you have purchased - there are many clones out there, built with low-cost chip-sets and not genuine FTDI
I have made this point before about how it's not how they LOOK
it's what they ARE
Take this one for example:
It actually looks
(outwardly) identical to one I have used personally.
If you read the reviews you will find several Triumph users who said it worked for them and were actually very happy.
you will also find these reviews -
The cable I ordered was not from FTDI and did not work with the FTDI drivers. OBD-HOTSALES was trying to help me but could not provide the correct drivers.
After some research if found out it is a Nanjing Qinheng Electronics USB-Serial adapter, type CH-340 or HL-340.
Vendor ID: 1A86
Product ID: 7523
You can check these VID and PID via Device Manager > Properties > Details.
Those wishing to purchase this cable to use with Tune ECU be aware that this cable does not contain the FTDI chipset.. This cable would not work with my 2007 Triumph Tiger and the latest FTDI CDM (D2XX) drivers. The vendor ID shows the code belong to QinHeng Electronics. This cable uses the HL-340 USB-Serial adapter chipset - not FTDI.
Purchased one of this cables, looks exactly like the picture but it seems there are different versions of the cable (diffident internal parts). Some seem to work, according to previous reviewers. Others, like mine, DONT.
Mine does NOT work with TUNEECU
Tested in different computers with the correct driver, is not an issue of the computer nor the driver.
I needed this cable to use the TuneECM software on my Triumph motorcycle; other Amazon reviews indicated that this cable has worked for others doing the same. The first cable I received seemed to load the CDM20814 drivers okay (NOT the ones supplied with the cable), but TuneECM failed to connect to the Triumph's computer; there appeared to be some fault in the cable, so I sent the first cable back and ordered a second cable. The second cable looked different than the first one, and it failed to load drivers at all; its properties showed its name as "USB2.0-Serial". Using a utility called USBView, I discovered that the second cable did not contain the necessary FTDI chip, but instead was from QinHeng Electronics, and used their HL-340 USB-Serial adapter chipset. I sent the second cable back to Amazon. With advice from the Triumph Rat Motorcycle Forum, I ordered a proper cable from Lonelec in London, UK ( [...] ); it cost twice as much, but it works.
What I would suggest to all, is that BEFORE you attempt to DOWNLOAD
(your cable may appear to be working just fine in Diagnostic), verify that you indeed have a genuine FTDI Chipset
in your cable.
Here's how you can validate, courtesy of Tom Hamburg
Originally Posted by Tom Hamburg
The chip detection, can be accomplished much easier.
Download from the FTDI site, the tool "FT Prog v 2.6.8" and unpack it.
Now simply start the "FT_Prog.exe" and press in the program the "F5 key".
Now be, in the upper right window the chip-type and additional information displayed.
Originally Posted by Tom Hamburg
Here is the way described how from Jonathan, but in Windows 7
open device manager
select the cable (double-click on usb-serial-converter)
select the tab "Driver" and now select "from bus reported device description
You can also use this Utility USBView
(download link directly from FTDI website)