PSA - TuneECU might have a weakness on 2014+ R3s.

Should work fine on a 16. If you haven't yet used tuneecu on it, I'd suggest validating with the tuneecu guys that triumph didn't lock the 2016 ECUs, but I doubt they did. Just the first 16 iv heard of trying tuneecu.
 
No word back from the guys at TuneECU yet.

If the ECU is unlocked, should I be able to connect, read and copy the stock map to my laptop? Or does the lock only stop one from downloading new tunes to the ECU?
 
No word back from the guys at TuneECU yet.

If the ECU is unlocked, should I be able to connect, read and copy the stock map to my laptop? Or does the lock only stop one from downloading new tunes to the ECU?
The TuneECU web site shows the models you can't mess with. Supposedly, if the ECU is "locked" it will lock up if you try to hack it. It will be DOA. Not sure if it can be unlocked by Triumph or if you gave to buy a new ECU.
 
The TuneECU shows the models you can't mess with...assuming they are aware of the fact Triumph locked the ECU so they can list it.

The locked ECUs were never known until people started having DOA ECUs because they were trying to flash them, multiple victims, viewable on multiple forums.

This is why I suggest each model year verify with TuneECU (Tom) that they are safe to fiddle with before saying "yeah go ahead its fine".

2016s haven't been out long.
 
I'm in no real hurry and saw they updated the site for some other things today but no update on the model year for the Rockets.

Thanks for the info.
 
Still no response having used the contact link on the TuneECU site. Any other ways to try contacting them?
 
Hmm, not as far as I know. I'm confident that the 16 will be compatible, however, I don't know for sure. If it's not compatible, it'll trigger a protect mode preventing it from starting requiring a dealer reflash.

Up to you if you want to roll the dice and risk a tow to the dealer or just keep emailing the TuneECU guys.
 
I may just bite the bullet and hope for the best.
Chasing part numbers for the ecu shows they have used the same hardware since the roadster came out. I know that is not indicative of software locks. I should be able to find a used 2015 or older to replace it if needed. The wife will frown, but she knows me.

Being an IT professional, having a piece of electronics I can't fiddle with is the worst part about it. The bike runs great, I just love, or I am addicted to, tinkering
 
After much logging and some dyno time I have come to the conclusion that all 20776/20773 based tunes with the 2.5.5 version of TuneECU that I have ever worked with have an anomaly at 5800 RPM and higher.

As a result I am pulling every TuneECU tune I have made down, and advising all owners to seek out other means (PC-V, Dobeck, Tuneboy) of tuning their bikes.



The Long of it:

The TuneECU software allows you to adjust the RPM limit, however, the fuel cut is still active to a certain degree. The AFR from 5800+ swings very very lean (dangerously so), so it would hold a nice solid 12.8:1 or there about up to 5800, then swing into the 14 or 15 to 1 range, regardless of inputs into the fuel tables. My suspicion is the revlimit adjustment only moves the hard cut (full fuel cut) to the RPM you specify, and the soft cut is still in place at 5800.

The only way I was able to catch it was a dyno print out where the sensor was suspect. Then datalogged on the road in 4th and found the same issue, so its not a sensor malfunction, its the bike.

Tunes based on 20776 or 20773 have both yielded this anomaly, but tuneboy does not using the live tune, pretty definitively isolating the problem to TuneECU and not an anomaly with the 2014+ bikes, but the software specifically.

YIKES! This sounds like what is most likely happening to mine...what was the fix to this?

Have you seen my post about it Claviger? Here is my dyno sheet...Unfortunately the A/F was not working on the dyno that day.
 

Attachments

  • rocketdyno.jpg
    rocketdyno.jpg
    64.7 KB · Views: 4
Back
Top