I checked it out, it looks like something I could use as well later on when the warranty has expired and I am in a position to fiddle with the tuning, but I really wanted a simple tester just to identify faults at this stage, and not only on my bike, but also on my Wifes CBF. Thanks for the input though.

I have one of them as well as two pieces of software that do similar things but far more comprehensively and a lot easier.

The first is "DealerTool" This is OK for most servicing, throttle body synch and seeing what the sensors are reading, idle speed setting, etc, but "Tune ECU" knocks them both into a cocked hat.

Once the initial difficulties of loading the correct FTDI driver, downloading NETframework for Windows etc and finding a reliable cable, all made easier if the instructions and advice here and in the software's site are thoroughly read first, things are plain sailing.

Just because TuneECU can get into the ECU in a deep manner it doesn't mean you have to. If you're afraid to delve, just use the Diagnostics and tests facilities on it. It's superb.

For what it's worth, read my opinions of these items, starting with the OBDII code reader/scanner and its limitations (important things like throttle body synchronisation and second O2 sensor and second MAP sensor readings are absent) in paragraph 5 of this post:

I have one of them as well as two pieces of software that do similar things but far more comprehensively and a lot easier.

The first is "DealerTool" This is OK for most servicing, throttle body synch and seeing what the sensors are reading, idle speed setting, etc, but "Tune ECU" knocks them both into a cocked hat.

Once the initial difficulties of loading the correct FTDI driver, downloading NETframework for Windows etc and finding a reliable cable, all made easier if the instructions and advice here and in the software's site are thoroughly read first, things are plain sailing.

Just because TuneECU can get into the ECU in a deep manner it doesn't mean you have to. If you're afraid to delve, just use the Diagnostics and tests facilities on it. It's superb.

For what it's worth, read my opinions of these items, starting with the OBDII code reader/scanner and its limitations (important things like throttle body synchronisation and second O2 sensor and second MAP sensor readings are absent) in paragraph 5 of this post:

Thanks for that, I have downloaded TuneEcu and am now studying it. It's amazing what these Engine Management systems do! I will get a lead. Unfortunately, my prior experience of bike systems was limited to a fault finding kit that comprised of a strobe light, multimeter, and a lightbulb with 2 bits of wire soldered to it.....back to school I go!!!

If you can open the program it means that your PC already has NETframework installed correctly, I think. The only hurdle left is the cable driver. The ones that come with the cable or the one that windows will insist on loading won't work. It has to be the driver recommended on the stickies here or in TuneECU site.

Just for laughs download a sample tune from the site, say 20191 which is a standard Factory tune , open it in TuneECU and see all those numbers, airflow, ignition timing curves, etc pop up. It's a bit frightening at first to realise how easy it is to change those figures (and indeed cock everything up...).

I have one of them as well as two pieces of software that do similar things but far more comprehensively and a lot easier.

The first is "DealerTool" This is OK for most servicing, throttle body synch and seeing what the sensors are reading, idle speed setting, etc, but "Tune ECU" knocks them both into a cocked hat.

Once the initial difficulties of loading the correct FTDI driver, downloading NETframework for Windows etc and finding a reliable cable, all made easier if the instructions and advice here and in the software's site are thoroughly read first, things are plain sailing.

Just because TuneECU can get into the ECU in a deep manner it doesn't mean you have to. If you're afraid to delve, just use the Diagnostics and tests facilities on it. It's superb.

For what it's worth, read my opinions of these items, starting with the OBDII code reader/scanner and its limitations (important things like throttle body synchronisation and second O2 sensor and second MAP sensor readings are absent) in paragraph 5 of this post:

Register Now

In order to be able to post messages on the Triumph Forum: Triumph Rat Motorcycle Forums forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.

User Name:

Password

Please enter a password for your user account. Note that passwords are case-sensitive.

Password:

Confirm Password:

Email Address

Please enter your valid email address, that can receive an automated confirmation message. Otherwise, you won't be able to gain full access.

Email Address:

Location

City and/or country where you live

Main Motorcycle

Your First Name

Please insert your first name

Log-in

User Name

Remember Me?

Password

Human Verification

In order to verify that you are a human and not a spam bot, please enter the answer into the following box below based on the instructions contained in the graphic.