Triumph Rat Motorcycle Forums banner
  • Hey everyone! Enter your ride HERE to be a part of this month's Bike of the Month Challenge!

1 - 4 of 4 Posts

·
Registered
Joined
·
112 Posts
Discussion Starter #1
Hi

I have Lonelec cable and HP Laptot.
I have used this combination with TuneECU couple of years with Triumph America.
Everything worked well until I updated the laptop from win7 to win10.

It does not connect to ECU anymore.
Red/orange traffic light blinking on TuneECU dashboard. Some times even green but no actual connection.

TuneECU version 2.5.8
FTDI 2.12.28.0

Help?
 

·
Registered
Joined
·
2,255 Posts
Hi

I have Lonelec cable and HP Laptot.
I have used this combination with TuneECU couple of years with Triumph America.
Everything worked well until I updated the laptop from win7 to win10.

It does not connect to ECU anymore.
Red/orange traffic light blinking on TuneECU dashboard. Some times even green but no actual connection.

TuneECU version 2.5.8
FTDI 2.12.28.0

Help?
I recently got a new Windows 10 laptop. Have used TuneECU for some time with my old Windows XP dinosaur of a laptop. Could not get the new one to connect after loading the app and cable driver. *My cable actualy came with a kit for my Audi but worked fine with TuneECU. I found I had to change a setting in the properties of the USB serial converter in the Device Manager. Had to disable the "load VCP" option (Virtual Comm Port). Then connecting the cable before launching TuneECU and it now connects as expected.
 
  • Like
Reactions: DEcosse

·
Registered
Joined
·
112 Posts
Discussion Starter #3
Thanks for the tip!

I'll test it when I get back to home next week.
In the meanwhile i loaded the Android version of TuneEcu to my Samsung tablet an it works like a dream with bluetooth reader.
 

·
Registered
Joined
·
112 Posts
Discussion Starter #4
I was going to test it today.

First I connected the USB cable and turned the ignition on.
TuneEcu started to load parameter as it should.
I didn't make the intended changes to port parameters.

Maybe this issue was fixed by some automatic windows or driver update. Or something....
 
1 - 4 of 4 Posts
Top