TuneECU -- HOW TO

[dougl]

Yeah, I followed the driver install instructions closely but when I kept getting, "there is no driver for you device", I did some more digging and discovered that this cable has the CH341 chipset. Bit of a bummer.

I got the cable from e-bay:

http://rover.ebay.com/rover/1/711-5...0001&campid=5335943355&icep_item=251088284958

It's the same cable that pops up first on amazon for "all departments" when you type in tuneecu cable.

 

[Scuba Craig]

Has anyone had problems with the newer 2.5.5 or so Tune ecu? I always update my tune ecu software as it changes on both of my computers. Neither one is advance my main home one has Vista and the net book I use for the bikes had XP. This time when I updated I was able to link up with my bike and load a map after that I have never been able to link up with the bike. I have older versions on the net book which immediately link up and load maps successfully. I suppose I should see if my Tune boy cable acts any different but I must admit I have not tried it since the tune ecu cable has always worked. Just in case it matters this is not a Rocket it is a Sprint I cannot use tune ecu on my Rocket because of the advanced High rpm mapping system I use in it. Still it should not matter.

I had a very similar problem. Connected first time; updated map; then could not get the connection with the ECU.

I am not sure whether my tinkering with the settings corrected the problem, or if it was just a problem related to the phase of the moon. Anyways, what I did was ...

1. Disabled VCP (virtual Com Port) in the driver. There is a post about it somewhere. I could look it up if need be.
2. In TuneECU I made sure I was set to connect to the USB port, not any of the Com ports.

I connected to the ECU immediately after making these changes.

Also try Display Logs in TuneECU to see if it gives any meaningful hints.

 

[dave64]

There is a definite difference in cables , i bought a cheap ebay one and tried everything no go . So i bought the cable from lonelec from the link on here plugged in and worked straight away on windows 8.1 it searched and loaded drivers, on the older XP laptop the new hard ware folder popped up and went through loading . Then all was good .

 

[wildchild]

So, I got the Lonelec cable and I'm 99% sure I downloaded the drivers and I'm positive I've successfully downloaded the newest version of TuneEcu along with the library file. So I think I'm ready to do this. I've read so many posts that I think I know what to do, but I got that nervous feeling in my gut. I guess I am a bit concerned about f***ng up my bike. I mean, who wouldn't be, right? I don't want to own the biggest paper weight ever. I guess I'd like to follow a set of steps that guide me through the process. I know I have to:

-disconnect headlamp fuse
-make sure battery is hooked up to a charger. (mine is fully charged indicated on my trickle charger)
-turn ignition on, kill switch in the position where I can start the bike if I wanted to

When do I actually connect the cable to the ECU adapter? Before or after these things?
Let's presume I get stuck after accessing the ecu. How does one back out of the process? Simply unplug cable?

LOL who's coming over to my house to show me how?

 

[Scuba Craig]

... When do I actually connect the cable to the ECU adapter? Before or after these things?
Let's presume I get stuck after accessing the ecu. How does one back out of the process? Simply unplug cable?

I have always connected the cable at both ends before switching the ignition on.

Just practice reading and saving the existing map from your ECU if you want to get confidence.

 

[wildchild]

Thanks Scuba!

 

[ThingKing]

This is what I did last week:

Following the instructions, I connected a battery charger and removed the fuse for headlight, first.
I connected the cable to the laptop and the bike, then started the laptop and Tuneecu, and finally switched ignition on.
Tuneecu connected automatically with the ecu, and i clicked to import the map from the bike.
I was surprised that it needed around 20mins to load the map into Tuneecu, so the whole party lasted for about an hour on the first day.

On the second day, I was confident enough to do changes.
With Tuneecu connected, I changed max rpm to 6700 and topspeed to 260 in the map.
I opened up the secondaries to 100% in all the fields, then saved the map on the laptop. Finally I downloaded it to the bike, which only needed a minute.
I closed Tuneecu, switched the ignition off and shut the laptop down. I removed the cables and smoked a cigarette.

After this, I did the 12 minute tune. TPS was green in Tuneecu when done.

Couldn't wait to jump on the bike. It was rainy and cold, but after that ride I can tell that I successfully removed those limitations.
Maybe my butt dyno needs a reset too, but I felt like the bike actually ran better in every gear, and all over the rev band. Don't know why, could have something to do with the relation of the ecu and the PCIII dynotune, or with the 12 min tune. The way it goes from 50 to 110mph in 3rd within a few seconds, really struck me.

So I am very happy I did it, and thanks to everybody here for contributing to my confidence.

 

[wildchild]

This is what I did last week:

Following the instructions, I connected a battery charger and removed the fuse for headlight, first.
I connected the cable to the laptop and the bike, then started the laptop and Tuneecu, and finally switched ignition on.
Tuneecu connected automatically with the ecu, and i clicked to import the map from the bike.
I was surprised that it needed around 20mins to load the map into Tuneecu, so the whole party lasted for about an hour on the first day.

On the second day, I was confident enough to do changes.
With Tuneecu connected, I changed max rpm to 6700 and topspeed to 260 in the map.
I opened up the secondaries to 100% in all the fields, then saved the map on the laptop. Finally I downloaded it to the bike, which only needed a minute.
I closed Tuneecu, switched the ignition off and shut the laptop down. I removed the cables and smoked a cigarette.

After this, I did the 12 minute tune. TPS was green in Tuneecu when done.

Couldn't wait to jump on the bike. It was rainy and cold, but after that ride I can tell that I successfully removed those limitations.
Maybe my butt dyno needs a reset too, but I felt like the bike actually ran better in every gear, and all over the rev band. Don't know why, could have something to do with the relation of the ecu and the PCIII dynotune, or with the 12 min tune. The way it goes from 50 to 110mph in 3rd within a few seconds, really struck me.

So I am very happy I did it, and thanks to everybody here for contributing to my confidence.

I'll savor a cold beer after I remove the cables...your experience is very helpful. Thanks for the write up.

 

[Gregger]

This is what I did last week:

Following the instructions, I connected a battery charger and removed the fuse for headlight, first.
I connected the cable to the laptop and the bike, then started the laptop and Tuneecu, and finally switched ignition on.
Tuneecu connected automatically with the ecu, and i clicked to import the map from the bike.
I was surprised that it needed around 20mins to load the map into Tuneecu, so the whole party lasted for about an hour on the first day.

On the second day, I was confident enough to do changes.
With Tuneecu connected, I changed max rpm to 6700 and topspeed to 260 in the map.
I opened up the secondaries to 100% in all the fields, then saved the map on the laptop. Finally I downloaded it to the bike, which only needed a minute.
I closed Tuneecu, switched the ignition off and shut the laptop down. I removed the cables and smoked a cigarette.

After this, I did the 12 minute tune. TPS was green in Tuneecu when done.

Couldn't wait to jump on the bike. It was rainy and cold, but after that ride I can tell that I successfully removed those limitations.
Maybe my butt dyno needs a reset too, but I felt like the bike actually ran better in every gear, and all over the rev band. Don't know why, could have something to do with the relation of the ecu and the PCIII dynotune, or with the 12 min tune. The way it goes from 50 to 110mph in 3rd within a few seconds, really struck me.

So I am very happy I did it, and thanks to everybody here for contributing to my confidence.

Now all you need to do is add the +5% or +10% fuel map Hanso has made to further increase the grunt and get rid of any decel popping.

 

[ThingKing]

Now all you need to do is add the +5% or +10% fuel map Hanso has made to further increase the grunt and get rid of any decel popping.

My PCIII was custom tuned on a dyno, so on my rather poor level of expertise it's probably better not to touch the fuel maps in TuneEcu, on top of that. There is no decel popping anyway, which should be a good sign.

One interesting question would be: what happens between 6300 and 6700? My PCIII was dyno tuned when the original TORs map was in place. Rev Limit had not yet been changed at that time, so the PCIII might not be set up for those additional revs. Could I run lean over 6300? I don't know, it seems to run fine on top end though.
Maybe @HansO can tell?

I do realize as well, that after doing those changes and revving out to 6700 several times, my TORs are getting noticably louder. And the power band seems to change with that, it gets increasingly divided between the part under 3500 and the high revs. So it seems I have to sacrifice some of the low-end grunt for the increased peak power.