Claviger
Aspiring Student
- Joined
- Jul 25, 2014
- Messages
- 6,934
- Location
- Olympia Washington
- Ride
- '21 Z H2, '14 R3R, '02 Daytona 955i
The easiest fix is to start in selective boot up mode and disable driver signature enforcement.
TuneECU -- HOW TO
- Thread starter Power-Tripp
- Start date
cr0ft
Living Legend
You need to install and download the FTDi driver manually to be sure it's on there.
D2XX Direct Drivers - download the first one, the WHQL certified. As of this writing, the link should be http://www.ftdichip.com/Drivers/CDM/CDM21216_Setup.exe
Install it with the cable unplugged. Once you have that installed, plug in the cable. You then need to figure out which "COM port" the cable is on. As you know, in the TuneECU you have to pick the right one.
Here's a tutorial from another site that shows you how to track down what COM port number you got. Though really, to just see what it is and not go changing stuff, go to the start menu, find the "Run..." entry and click it and type this in in the window that pops up and then hit enter:
devmgmt.msc
Look under "Ports" to find something that should be marked "USB serial" something or other, see the first image in the link below.
Overview | How to Find Hidden COM Ports | Adafruit Learning System
Once you have the driver installed, and the right COM port selected in TuneECU, you should be able to hit connect and (after a little while) get the green blink and not the red. And once you get there you're good to go.
The most likely failure points I would guess to be 1. no FTDi driver installed properly, and 2. choosing the wrong COM port in TuneECU (or choosing no COM port and trusting to fate, and she's a fickle b-tch).
D2XX Direct Drivers - download the first one, the WHQL certified. As of this writing, the link should be http://www.ftdichip.com/Drivers/CDM/CDM21216_Setup.exe
Install it with the cable unplugged. Once you have that installed, plug in the cable. You then need to figure out which "COM port" the cable is on. As you know, in the TuneECU you have to pick the right one.
Here's a tutorial from another site that shows you how to track down what COM port number you got. Though really, to just see what it is and not go changing stuff, go to the start menu, find the "Run..." entry and click it and type this in in the window that pops up and then hit enter:
devmgmt.msc
Look under "Ports" to find something that should be marked "USB serial" something or other, see the first image in the link below.
Overview | How to Find Hidden COM Ports | Adafruit Learning System
Once you have the driver installed, and the right COM port selected in TuneECU, you should be able to hit connect and (after a little while) get the green blink and not the red. And once you get there you're good to go.
The most likely failure points I would guess to be 1. no FTDi driver installed properly, and 2. choosing the wrong COM port in TuneECU (or choosing no COM port and trusting to fate, and she's a fickle b-tch).
Last edited:
Claviger
Aspiring Student
- Joined
- Jul 25, 2014
- Messages
- 6,934
- Location
- Olympia Washington
- Ride
- '21 Z H2, '14 R3R, '02 Daytona 955i
The drivers are also not signed properly, this creates issues depending on windows settings in 8,8.1, and 10.
See my earlier post if you've done as croft describes but still can't get it to work. Googleing will give the steps to get into selective startup and disable driver signature enforcement for your particular OS.
See my earlier post if you've done as croft describes but still can't get it to work. Googleing will give the steps to get into selective startup and disable driver signature enforcement for your particular OS.
Tripps
Retired superhero
- Joined
- Oct 9, 2010
- Messages
- 11,435
- Location
- Florida and NY
- Ride
- R3T,Sprintona,K1200GT, Blackbird,r/65 hack
I just had the problem of not connecting to a Thruxton, after never having any problem with my own 3 Triumphs, second day he came over, I had him try starting the bike, and it connected right away, after that it connected several times with just the key on with no problem.
????No idea why that worked, but worth a try.
????No idea why that worked, but worth a try.
cr0ft
Living Legend
I recall reading that getting voltage drop when working on the ECU is a bad thing, which is why the recommendation is to unplug the headlight fuse to keep power drain to a minimum.
Personally I did that *and* put a battery charger on the bike while I as working on the ECU just to make sure it remained at high voltage at all times. When you fire up the bike it kicks the whole electrical system up over 14 volts, so that may have been involved somehow.
Personally I did that *and* put a battery charger on the bike while I as working on the ECU just to make sure it remained at high voltage at all times. When you fire up the bike it kicks the whole electrical system up over 14 volts, so that may have been involved somehow.
Joesmoe
IMOKUR2
***************
I am running Windows 10 Home.
I downloaded the FTDI driver, and it installed.
I plugged in the cable. Of its lights, the far right one is red. No matter what I've done, no other lights come on, except when first plugging in the cable, there is brief couple of orange lights, as if trying to establish comms, and those go out.
Looking at Device Manager, the only thing listed under COM is a "Prolific USB-to-serial COM Port" listing, and depending on in which of the three USB ports on the laptop I have the cable plugged, that adapter shows them as COM 4, 5, and 6, respectively.
Opening Tune ECU, and looking under 'Options', and 'Interface': the USB option is grayed out, and the only option open is Serial, and clicking on that, there is only COM 3 with a check mark. I can't uncheck it. It seems to be "hardwired" to that option.
Suggestion?
You have to install the driver manually. Disconnect from the net and have the ftdi driver folder on your hard drive. The driver has to be installed in two places, as a com device and as a usb device. When you plug in the cable, a line will appear in both places. Check the properties and look at the driver. It should be ftdi 2.8.08 if you got the driver package from the link on the TuneECU site. If it isn't, update the driver manually.
cr0ft
Living Legend
Go back up a bit in this thread and look at Claviger's post. It seems likely that it's Windows 10 that's messing with you due to the driver not being "signed".
Joesmoe
IMOKUR2
I went on line this morning to the Tune ECU site, and see they have updated the software to v2.5.7.
The challenge is I don't understand where signing is involved -- Windows did ask if I insisted on running Tune ECU -- no such challenge for the FTDI driver package --and Tune ECU shows only COM 3 with no way to change it, and the Device Manager is showing the three USB ports as COM 4, 5, and 6, and apparently no way to change those. So I'm stuck, seemingly.
The challenge is I don't understand where signing is involved -- Windows did ask if I insisted on running Tune ECU -- no such challenge for the FTDI driver package --and Tune ECU shows only COM 3 with no way to change it, and the Device Manager is showing the three USB ports as COM 4, 5, and 6, and apparently no way to change those. So I'm stuck, seemingly.
Similar threads
