TuneEcu Connection Problem

[DRMD421]

I had the same problem. I reinstalled the Tune ECU software , and the drivers. Deleted the old ones first. Took about 10 minutes .

I tried to connect to uneEcu. Plugged cable into bike, blue light comes on, connect USB into laptop and get the "dadonk" sound. TuneEcu is already on screen, turn ignition switch on. Now heres the problem. I don't get the lower right hand corner to show I've linked to the program, never get the flashing red let alone amber and green. I bought the cable from Powertripp and it's worked in the past. Does this indicate that the cable has gone bad? Is there a way to test it? Or is there another step by step process that I should try? Just want to know before I buy another cable and then find out I'm doing something out of sequence.

I ran into the same problem. Turns out, I forgot to flip the kill switch back to "run".

 

[ROCKETOUR]

Hey, thanks to all for their contributions regarding my inability to achieve a connection. I kept trying that day and discovered something very interesting. I don't know if this is just my bike (08 R3T) or common with other R3T owners.
I'm sure a huge number of us have seen the great Youtube video online of the chap installing a tune onto his Triumph.
He plugs into the bike, with TuneEcu already loaded on his laptop, then plugs the USB cable into his laptop. I did it exactly as he did. On my bike THIS DOES NOT WORK AT ALL! I went to the TuneEcu website and read their instructions and tried that (which is a different order of steps to connect). It connected the very first time out. The file provided by PowerTripp downloaded quickly, reset TPS (and got green light after about 6-7 minutes of running). The bike seems to like the tune. Solo cruise yielded 38.5 MPG! Two up, loaded and interstate speeds got me about 33 MPG. It runs nice, seems to have a little less vibration in the mirrors at road speed. Anyone know why it wouldn't connect using the Youtube guy's method? Could this be hampering others using that method? If so, refer to the TuneEcu website under the "TASKS" heading and follow those instructions.

 

[cr0ft]

There's a lot of stuff all over the place about TuneECU and the Triumph ECU's wanting a cable with an FTDi chipset. Since I'm in Europe anyway, I hit up Lonelec in the UK who claim to be highly compatible and had no issues - installed the drivers first, then fired up TuneECU, connected the cable up to the bike, turned the bike on, connected the cable to the computer USB port and presto, automatically connected.

Most likely your laptop was doing something driver-related when you plugged the cable in, but I think if you first install TuneECU, then download and install the cable drivers, hook the cable to the computer so it activates the drivers for it and then go into the garage, you'll be good.

 

[rjkusse]

Has anyone tried it on a MY15? I've been able to successfully connect once...

 

[Bedifferent]

There's a lot of stuff all over the place about TuneECU and the Triumph ECU's wanting a cable with an FTDi chipset. Since I'm in Europe anyway, I hit up Lonelec in the UK who claim to be highly compatible and had no issues - installed the drivers first, then fired up TuneECU, connected the cable up to the bike, turned the bike on, connected the cable to the computer USB port and presto, automatically connected.

Most likely your laptop was doing something driver-related when you plugged the cable in, but I think if you first install TuneECU, then download and install the cable drivers, hook the cable to the computer so it activates the drivers for it and then go into the garage, you'll be good.

I'm with you, the Lonelec cable is the way to go. It seems to be the gold standard as cables go. My advice to everyone is forget the bargain buy off from Amazon. You're uploading critical information to your ECU so why take a chance on a failed installed or problems connecting. Having to attempt some sort of recovery and the cost of a damaged ECU is flat out scary.

 

[dougl]

It's very easy to get the driver installation wrong.

 

[Bedifferent]

It's very easy to get the driver installation wrong.

I think that is especially true if you are technologically illiterate when it comes to computers. Having worked in IT tech support for almost 10 years after my teaching career, it became obvious that most people just don't know what they are doing. There was a acronym we use to have for that...we called them "picnic" errors...Problem In Chair, Not In Computer.

I will say, however, that the directions are pretty good on the Tunecu site, but it can be very dark territory if you don't know how to check and make sure the drivers have been installed. If in doubt, pay someone who knows what they are doing to setup the program, .dll file and the chipset drivers. A reliable cable is also a must or you're just spinning your wheels trying to figure out why things are not working properly.

 

[dougl]

I think that is especially true if you are technologically illiterate when it comes to computers. Having worked in IT tech support for almost 10 years after my teaching career, it became obvious that most people just don't know what they are doing. There was a acronym we use to have for that...we called them "picnic" errors...Problem In Chair, Not In Computer.

I will say, however, that the directions are pretty good on the Tunecu site, but it can be very dark territory if you don't know how to check and make sure the drivers have been installed. If in doubt, pay someone who knows what they are doing to setup the program, .dll file and the chipset drivers. A reliable cable is also a must or you're just spinning your wheels trying to figure out why things are not working properly.

You have to be intimate with the device manager.