Regarding 2006 Triumph Tiger and TuneECU:
Are all the OBD2 to USB cables the same?
Found one on Amazon for less than $9.00 US....
http://www.amazon.com/Obdii-Diagnostic-Adapter-Converter-Cable/dp/B002WIN8VQ/ref=pd_sxp_f_pt
I don't think so as some people have had problems with some of the Chinese ones. I use my Tuneboy cable so have never needed to buy one. However, I notice that the page linked to by Tom specifies the type of cable needed by TuneECU.
I couldn't find any info about what cable....
Quote from: Fe Man on September 24, 2014, 12:34:31 AM
I couldn't find any info about what cable....
:icon_rolleyes:
Copied from the TuneECU Android front page, near the bottom:
1.1 Configuration required :
• Smartphone or Tablet Android version 4.0 minimum, dual Core 1.2 Ghz mini.
• Cable USB OBD2 FTDI (The cable is the same as the windows version)
• Adapter USB/micro (cable OTG) if needed
• Optional: Interface Bluetooth ELM327, as of version 1.4
Thanks Bob!
It never occurred to me to look into Android/Bluetooth when I was planning to use a hardwired connection to my laptop...
:icon_scratch:
Fe Man,
Sources for USB_OBD2-cable and/or Plug Adaptor, can be found here: http://www.tuneecu.com/TuneECU_En/links.html
Regards,
Tom
Thanks Tom, useful info. I'm going to install app on my HTC one this weekend,
Are there set mapping data on the app, for instance I've removed the plate in my airbox which restricts the air flow, and I'm going to be fitting an aftermarket can this weekend, will there be a Map to suit on the app?
The cable supplied by Triumph Twin Power works fine.
You'll need a micro USB male to standard USB female to hook up to your phone.... waiting for mine coming :nod
The ability to carry everything you need for a remap, reset etc on your phone + a cable I find comforting somehow.... :icon_rolleyes:
Same here, got the app and ordered the cables....I take it the app will automatically find the map I've downloaded.
So I ordered a cable from Amazon that according to the reviews, works on the Triumph and TuneECU.
Well no such luck!
Had to download software to open the DLL files.
Updated drivers, nothing.
I hate this computer bullshit! All I want to do is fix my Tiger!!!!!
It's never easy.
Does anyone have an Amazon link for a cable that works? Amazon Prime gets it here tomorrow!
Are you using Android or your laptop?
It does mention that its for 2009 onwards....
Quote from: TT on September 26, 2014, 12:16:43 AM
Are you using Android or your laptop?
Laptop. I have one working Windows XP laptop in the house otherwise all Macs.
My daughter has an Android tablet however.
Under the TuneECU software, the option tab allows for one to select either serial or USB but I'm unable to change it as it appears to not recognize the cable plugged into the USB port.
I'd give someone $500 to fix my bike and me not have to play with computers!
I think if you download the Android app on your phone the app will have built in drivers (software required for it to recognise the cable) but if use Windows I think you need to Download the driver for the laptop to recognise the cable you've bought.
Google FTDI drivers.
Quote from: TT on September 26, 2014, 12:36:21 AM
Google FTDI drivers.
Downloaded the FTDI drivers from the TuneECU links, nothing...
Hey Fe Man !! just a thought, you do have NET Framework Vers. 2.0 and upwards (XP only) on yer laptop ?
i was :BangHead when i first tried to get it to connect but it all falls into place and is worth every :icon_scratch:
i thank the guys at TuneECU for all the work they put into this :eusa_clap :notworthy :icon_salut:
KK
Quote from: KuzzinKenny on September 26, 2014, 02:59:43 AM
Hey Fe Man !! just a thought, you do have NET Framework Vers. 2.0 and upwards (XP only) on yer laptop ?
i was :BangHead when i first tried to get it to connect but it all falls into place and is worth every :icon_scratch:
i thank the guys at TuneECU for all the work they put into this :eusa_clap :notworthy :icon_salut:
KK
Yes and I downloaded that dot net crap which did nothing,
Xp can be finicky and understand the frustrations. Some observations/tips for XP laptop use:
If the $9 cable is the one you purchased off Amazon, many reviews state that they are not happy with it. You may want to spring for Amazon's $12 cable (which of all things is titled as "USB Cable for Triumph ECU Program"). Several positive reviews that this one works. If you elect to purchase this cable, I would also recommend you download the FTDI drivers using the link from the Tune-Ecu link page @ http://tuneecu.com/TuneECU_En/links.html. My cable worked just fine by using these drivers. I would recommend you save the drivers temporarily to your desktop so you can find them if needed for the finicky XP driver issue(discussed later)
KuzzinKenny is right on the mark with .Net framework
Ensure you have .Net 2.0 sevice pack 2; .Net 3.0 and higher is not needed running XP to use the FTDI drivers. Link for this can be found on the Tune-Ecu link page @ http://tuneecu.com/TuneECU_En/links.html
The finicky part of XP is that sometimes the drivers do not properly load or associate for the usb device. You would check to ensure this by exploring "Device Manager" see if you have an unrecognized device within "device manager". If this occurs and you have an "unknown device", click upon the "unknown device" icon in device manager and then double-click on the device list in the newly opened "tree". A tab at the top of this newly opened pop-up should state "driver" and the box marked "update driver" allows you to associate the driver to this device (a few steps to accomplish). If you did save the FTDI drivers to you "desktop" this will allow you to find them easily when you associate them to the device.
Yes, computers are a pain in the ass, .Net is a pain in the ass, and while the Android Tune-Ecu is cool- the laptop is the way to go for what you want to do to fix that Tiger.
Thanks Stitch! I'm just very frustrated at this point.
I know it's an $8 cable and I didn't expect much honestly. I'm going to take a deep breath and start over today. Maybe I'll order one of the cables from the TuneECU provided links and wait till it arrives.
This has been such a PITA to track down. The bike was fine before the "spark plug incident" and the "miss" and fuel consumption issue manifested itself immediately upon reassembly. I still think it is ignition (or lack thereof) related.
I absolutely am unable to get the appropriate drivers installed and recognized.
I am beaten.
Burn it.
Quote from: Fe Man on September 26, 2014, 07:19:47 PM
I absolutely am unable to get the appropriate drivers installed and recognized.
I am beaten.
Hey Fe Man !! don't give up yet :nono as Stitch said computers are a PITA and you might have loaded the wrong driver first :icon_scratch:
i would uninstall and start again :icon_confused: do the cable stuff last !!
http://www.tigertriple.com/forum/index.php/topic,8852.msg63239.html#msg63239
just found this............
http://www.tigertriple.com/forum/index.php?topic=12234.0
remember this - battery must be fully charged - headlights must be switched off or fuse pulled :thumbsup
good kuck
KK
ps did i find a missing link or was that just me :icon_scratch: :ImaPoser
I feel your pain....to clarify: you are using the new $12 cable and have shit canned the $8 one?; you have downloaded the FTDI drivers to your desktop from the Tune-Ecu site?; Device manager of your XP laptop "sees" the device meaning in device manager there are no symbols that are a yellow question mark ?
Even if you have a recognized device, do the driver update as described to ensure the drivers associate to the device (Windows likes adding default ones instead of the ones you want).
Use the laptop with XP, I know that works.
Download the TuneECU cable drivers from the TuneECU website
Since you've already tried the cable it will have loaded some drivers that won't work.
Plug in cable, got to Control Panel / System / hardware manager. There should e a USB device you can recognise as the cable. Click on it and uninstall the drivers.
Unplug the cable. Plug the cable back in. When it says found new hardware, select to install the drivers from a specific location. Direct it to wherever you put the TuneECU drivers you downloaded and install them.
The cable will now work with TueECU.
Quote from: Stitch on September 27, 2014, 05:20:10 AM
I feel your pain....to clarify: you are using the new $12 cable and have shit canned the $8 one?; you have downloaded the FTDI drivers to your desktop from the Tune-Ecu site?; Device manager of your XP laptop "sees" the device meaning in device manager there are no symbols that are a yellow question mark ?
Even if you have a recognized device, do the driver update as described to ensure the drivers associate to the device (Windows likes adding default ones instead of the ones you want).
I'm going to try and get another cable ASAP otherwise its kickstand up on Friday and I'll just ride it like it is.
Thanks for everyone trying to help!
Quote from: Fe Man on September 26, 2014, 03:56:38 PM
The bike was fine before the "spark plug incident" and the "miss" and fuel consumption issue manifested itself immediately upon reassembly. I still think it is ignition (or lack thereof) related.
I don't ......
My gut feeling is it's all related and you have a cylinder head / valve problem ......not ignition .
sounds more like a valve seat problem .
have you done a compression test ? especially on the cylinder that ate the valve . did you get a new seat cut to match the replaced valve ?
are you sure the valve timing is right after reassembly ?
Valve work was performed by a good friend, master mechanic, genius, engine builder, etc. I'm pretty sure its "right" if he did it. Timing is correct, very careful dis-assembly and reassembly. The bike actually runs great, pulls hard, etc., just has a really rough idle when cold and throttle surging/wandering issues at lower RPMs. When the bike is initially started, fast idle seems fine but when it drops back to "idle" it stumbles and even stalls when it is cold out. I pulled all of the coil packs out and they are firing. I measured the impedance across the inputs and all were the same but the values didn't correlate to any spec I have seen but I re-installed them and kept going.
I found a huge vacuum leak in the hard line going back to ECU and repaired it. The connection at the air box seems sloppy but I RTV'd the grommet into the box and its better. The bike seems to run a bit better and maybe fuel consumption is a bit better but the original issue remains.
Thanks!
Take the air filter plate off the airbox, remove the filter and have a look at the seating of the IACV gasket to airbox seal. Mine didn't (seal that is) and needed some additional 3mm dense foam to sort it. It's not going to be the root of your problems but it will help.
New cable, same fucking problems.
This cable is claimed to be specifically for using with the TuneECU software! Dot what the fuck ever has been downloaded, latest drivers downloaded, etc. Same story
"ECU not responding"
"Check cable connection and turn engine off and on"
Well I did that! About 20 times!
Did you laptop recognize the cable which can be seen within XP's Device manager? Even if it did, click on the device and make sure it has the dot WTF drivers which is also done through the Device Manager. If you haven't done these steps, then the old POS crap cable drivers will prevent it from working, especially with XP on your laptop.
It appears so however I can not specifically select the usb cable in the TuneECU software
FINALLY!!!!!
Was able to connect, reset TPS, starts and idles like a dream!
So with regard to maps, I'm running 10172, stone stock bike. Anything I need to do while I have Pandora's box unlocked?
The only thing I would do is copy the reading values so that you have a base-line in case you need to perform troubleshooting in the future. This way you know what works or "what it should look like" with the bike running well. Glad it's sorted.
:eusa_clap