Post missing
This post could not be recovered from the original forum.
TuneEcu with Windows 7
33 posts · Started by Reb · 01 Dec 2010
Post 2 by Colonel_Klinck,
#2Yep, problems here too. I'm sure my biggest one is lack of knowledge. I've got a new laptop running win 7 64bit. Got ver 1.7.8. and downloaded the drivers from Tune ECU site. Powercell cable, so that should be good.
When I connect to the bike I get...nothing.
How do you tell if the drivers are doing their thing.
Tried to follow Powercells tutorial on changing the port settings, but mine does not have the COM4 setting thingo in the list.
No doubt this is a great peice of software, but if its not easy to install and use without a computer science degree, its just a friggin headache.
When I connect to the bike I get...nothing.
How do you tell if the drivers are doing their thing.
Tried to follow Powercells tutorial on changing the port settings, but mine does not have the COM4 setting thingo in the list.
No doubt this is a great peice of software, but if its not easy to install and use without a computer science degree, its just a friggin headache.
Post 3 by BASH69,
#3Ok guys when you download the drivers to run the cable there is no actual .exe installer. The best thing to do is make sure you are not connected to the internet. Plug in the cable and you should get a window come up about New Hardware found. The problem if you are connected to the internet and have the PC set to download and install stuff automatically is it will do exactly that but its the wrong drivers that are installed. So make sure you are not connected. When the new hardware window pops up browse to the folder that contains the correct drivers and select. This will then install the correct drivers and the cable will work. You will know as the port will appear in the Hardware Device window and you can just the settings on it.
Hope that helps
Hope that helps
Post 4 by Reb,
#4Post missing
This post could not be recovered from the original forum.
Post 5 by RED ZX,
#5Post missing
This post could not be recovered from the original forum.
Post 6 by RED ZX,
#6OK, so I tried to download Net Framework 3.5. Got it downloaded but it did'nt install properly. Read the instructions which say if running 64 bit ver. to upgrade to Visual Studio 2008 sp1. So, downloaded that. Did'nt install.
Presumably because I dont have Visual Studio 2008 to begin with.
Are we having fun yet.
Cant find a free download of VS 2008 and I refuse to pay for it just to run one program.
I'm the first to admit I'm not the sharpest tool in the shed with computer shit, but I've just about had enough of this Tune ECU crap.
Presumably because I dont have Visual Studio 2008 to begin with.
Are we having fun yet.
Cant find a free download of VS 2008 and I refuse to pay for it just to run one program.
I'm the first to admit I'm not the sharpest tool in the shed with computer shit, but I've just about had enough of this Tune ECU crap.
Post 7 by ktmguy,
#7I just love using windows 7. Every time I upgrade my operating system it just keep getting more user friendly. Can't wait for windows 8. Lol.
Maybe Tom will chime in with what's needed. Or have the programer update it so it works on are ver. of window only. Ha!
"Time is money, money is time. I've spent a lot of money on this free program"
Maybe Tom will chime in with what's needed. Or have the programer update it so it works on are ver. of window only. Ha!
"Time is money, money is time. I've spent a lot of money on this free program"
Post 8 by Reb,
#8Post missing
This post could not be recovered from the original forum.
Post 9 by BASH69,
#9Post missing
This post could not be recovered from the original forum.
Post 10 by ktmguy,
#10Post missing
This post could not be recovered from the original forum.
Post 11 by Bert,
#11Post missing
This post could not be recovered from the original forum.
Post 12 by BASH69,
#12Post missing
This post could not be recovered from the original forum.
Post 13 by Reb,
#13Post missing
This post could not be recovered from the original forum.
Post 14 by ktmguy,
#14Post missing
This post could not be recovered from the original forum.
Post 15 by Imageseekr,
#15Post missing
This post could not be recovered from the original forum.
Post 16 by Reb,
#16Post missing
This post could not be recovered from the original forum.
Post 17 by Reb,
#17Post missing
This post could not be recovered from the original forum.
Post 18 by Imageseekr,
#18Post missing
This post could not be recovered from the original forum.
Post 19 by BASH69,
#19Post missing
This post could not be recovered from the original forum.
Post 20 by Reb,
#20[quote="bigash]
Are you sure your running windows 7?
The only pc i have that doesnt show the ports tab is running Vista (Microsoft in thier infinate wisdom decided to do away with it for some reason?!)[/quote]
Yep, currently running Windows 7 Home Premium.
Are you sure your running windows 7?
The only pc i have that doesnt show the ports tab is running Vista (Microsoft in thier infinate wisdom decided to do away with it for some reason?!)[/quote]
Yep, currently running Windows 7 Home Premium.
Post 21 by Reb,
#21Post missing
This post could not be recovered from the original forum.
Post 22 by Reb,
#22Post missing
This post could not be recovered from the original forum.
Post 23 by BASH69,
#23Post missing
This post could not be recovered from the original forum.
Post 24 by Reb,
#24Post missing
This post could not be recovered from the original forum.
Post 25 by jcozine,
#25Post missing
This post could not be recovered from the original forum.
Post 26 by NolaNomad,
#26Post missing
This post could not be recovered from the original forum.
Post 27 by ktmguy,
#27Just wanted to resurrect this thread since I had some of the same problems with my TuneECU cable (a cheap one off amazon) not showing up in my device manager list at all after driver installation, and I'm also using Windows 7 Home Premium 64-bit. Actually the first time I tried to connect something corrupted the ever living shit out of my computer, and I ended up having to wipe my machine clean and re-install the OS. However the first time I did it I did everything wrong, leaving my wi-fi on, letting it install drivers automatically, and trying to start the bike with everything connected. Not sure if it was the drivers or a power spike that screwed me over, but I would recommend doing none of those things.
The installation instructions on the FTDI site showing how to display inactive devices in Device Manager saved me. Did that so the cable showed up greyed out, uninstalled the drivers and re-installed the drivers a couple times a few different ways, and the computer finally recognized it correctly as both a USB Serial Port (Com3) under Ports and as a USB Serial Converter under USB Controllers. There are two different installation files you can choose from on the FTDI site, but the only one I had luck with was the executable in "CDM v2.08.30 WHQL Certified.zip" after it was unzipped and the zip file inside it was also unzipped, not "CDM20830_Setup.exe" even though it's supposed to be the same thing. When I ran it I also had to right-click and select "Run as administrator"; even though I am the administrator on my own computer, apparently this makes a difference, since Bill Gates doesn't trust you with his product. Totally straight forward, right?
I also noticed that my craptop wouldn't recognize the cable if it was plugged into the bike first - even though that's how the TuneECU site says to do it. Instead I had to connect in the following order:
1. Plug the adapter into the laptop. If it doesn't show up as a Com3 port, unplug it and keep messing with the drivers until it does.
2. Power on the bike (not necessary to start it though)
3. Start the TuneECU application
4. Plug the adapter into the bike
5. Select Connect in TuneECU, in case auto-connect isn't already selected (I think it'll work either way though)
6. Load an awesome map
7. Braaaap!
The installation instructions on the FTDI site showing how to display inactive devices in Device Manager saved me. Did that so the cable showed up greyed out, uninstalled the drivers and re-installed the drivers a couple times a few different ways, and the computer finally recognized it correctly as both a USB Serial Port (Com3) under Ports and as a USB Serial Converter under USB Controllers. There are two different installation files you can choose from on the FTDI site, but the only one I had luck with was the executable in "CDM v2.08.30 WHQL Certified.zip" after it was unzipped and the zip file inside it was also unzipped, not "CDM20830_Setup.exe" even though it's supposed to be the same thing. When I ran it I also had to right-click and select "Run as administrator"; even though I am the administrator on my own computer, apparently this makes a difference, since Bill Gates doesn't trust you with his product. Totally straight forward, right?
I also noticed that my craptop wouldn't recognize the cable if it was plugged into the bike first - even though that's how the TuneECU site says to do it. Instead I had to connect in the following order:
1. Plug the adapter into the laptop. If it doesn't show up as a Com3 port, unplug it and keep messing with the drivers until it does.
2. Power on the bike (not necessary to start it though)
3. Start the TuneECU application
4. Plug the adapter into the bike
5. Select Connect in TuneECU, in case auto-connect isn't already selected (I think it'll work either way though)
6. Load an awesome map
7. Braaaap!
Post 28 by ktmguy,
#28My battle with Tuneecu vs. Win7, running on Paralles over the top of my MacHD, is 8 months in.
I've gotten to the point where I can get the Tuneecu program to show up but shows only a Triumph dash and no red or green blinking light in the screens' corner(?)
Anyone know what gives?
I've gotten to the point where I can get the Tuneecu program to show up but shows only a Triumph dash and no red or green blinking light in the screens' corner(?)
Anyone know what gives?
Post 29 by NolaNomad,
#29Post missing
This post could not be recovered from the original forum.
Post 30 by ktmguy,
#30Post missing
This post could not be recovered from the original forum.
Post 31 by Jim H,
#31Post missing
This post could not be recovered from the original forum.
Post 32 by jcozine,
#32Post missing
This post could not be recovered from the original forum.
Post 33 by jcozine,
#33No mention here of booting in diagnostic mode. Click start, type msconfig and load diagnostic startup or selective startup. Not done this myself but thought it's worth a mention particularly to eliminate existing hardware/software/driver conflict. If it works you know there's a conflict but you'll also know how to rule it out. Running a basic OS may help is all I'm saying.
End of archived topic · Posting is closedBack to top ↑
← Back to Technical - Dr F's Words of Wisdom