TuneECU, ECU on Roadster is not responding anymore

[jaredmt]

Ok, here is my painful update:
Note, the laptop is actually Vista 32-bit (yuck). Problem continues ... I try a recovery ... just sits there forever, no progress bar movement (stays at 0%).
Bike battery, etc is fully powered, fuses pulled, etc.
I also tried w/ XP ... same story ... recovery goes no where.

What are the chances that the bug that was fixed in 1.6.4 has returned in 1.6.5? Bug regression is quite common. I ask because this is very much like the problem some guys were having w/ the Roadster with the version just before 1.6.4.

Does anyone have 1.6.4? Maybe worth trying? Other ideas? Having a GiPro connected to my bike shouldn't affect things right? (no problems in reading the data from the bike) Right now I have a $14k paper-weight.

 

[MikaK]

Ok, here is my painful update:
Does anyone have 1.6.4? Maybe worth trying? Other ideas? Having a GiPro connected to my bike shouldn't affect things right? (no problems in reading the data from the bike) Right now I have a $14k paper-weight.

I managed to read original map from ECU, make my modifications and then download the modified map back to ECU with version 1.6.4. without any problems. Earlier version (1.6.1 if I remember correctly) caused me worries similar to yours. I got my bike back alive after several recovery attempts.

I'm running WinXP Sp3 on my laptop.

Mika

 

[Leif Almberg]

Tom, do you have 1.6.4 available for the poor guy?
I think I have it on the laptop in the garage, but I'm at work not for quite some hours.
1.6.4 should work, no problems what so ever.

sorry to hear that you've been the guinea pig for 1.6.5

I will notify Alain abouth potential 1.6.5 problems.

 

[MikaK]

I have 1.6.4 installed in case someone might need it.

Mika

 

[Tom-Hamburg]

Yes, I have, here the Link

http://www.tomhamburg.net/Tunes_in_Hex_and_dat/TuneECU/TuneECUv1.6.4.zip

Note:

Alain has yesterday released a revision, version 1.6.5b, but this is undocumented, if you download now to 1.6.5, that's the revision.


BR, Tom

Tom, do you have 1.6.4 available for the poor guy?
I think I have it on the laptop in the garage, but I'm at work not for quite some hours.
1.6.4 should work, no problems what so ever.

sorry to hear that you've been the guinea pig for 1.6.5

I will notify Alain abouth potential 1.6.5 problems.

 

[jaredmt]

This is nuts. Something is going on here ... so no change w/ 1.6.4. Says I need a recovery .. click ok. It then either says it failed after 15 or so seconds, or it sits at 0% forever (I've waited 5-10 minutes, no change).
Not sure what's up.
Running XP w/ SP3 and the suggested drivers.
Laptop plugged in. Bike charger on; battery topped off; headlight/running light fuses out.
Have tried w/ 1.6.4 and 1.6.5 (not the 1.6.5 that was put up last night).
Bike has been dead for about 20 hrs now. I am going to go nuts.

 

[MikaK]

This is nuts. Something is going on here ... so no change w/ 1.6.4. Says I need a recovery .. click ok. It then either says it failed after 15 or so seconds, or it sits at 0% forever (I've waited 5-10 minutes, no change).
Not sure what's up.
Running XP w/ SP3 and the suggested drivers.
Laptop plugged in. Bike charger on; battery topped off; headlight/running light fuses out.
Have tried w/ 1.6.4 and 1.6.5 (not the 1.6.5 that was put up last night).
Bike has been dead for about 20 hrs now. I am going to go nuts.

In my case the recovery procedure seemed to complete just fine but the ECU remained unresponding. I had to run "Recover ECU" several times before I got my bike back alive.
However, the procedure always started, never stopped at any point. This happened with version 1.6.1.

Could it be your problems might be computer or cable related? Faulty USB port or cable?
Some virus scanners monitor also USB ports, so you could try recovery unloading your virus scanner first. Lots of possible causes, I know, but eliminating then one by one won't do any harm, anyway.

Mika

 

[jaredmt]

If the procedure never 'stopped', then when did you manually stop it?
I've tried with two PCs, one on XP and the other on Vista. So USB ports, for example, should be fine.
The cable is new and the only one I have. I was able to read the tables just fine. I then adjusted the secondaries and tried to download to the bike. I've been stuck here ever since.

NOTE: I've tested w/ 1.6.6 as well (having tried 1.6.4 ... 1.6.5 and 1.6.6 makes me think whatever I have going on it isn't TuneECU .. I guess)

 

[Tom-Hamburg]

!!!N E W S !!!

Version 1.6.6 is released.

Note:

• Add F-L Switch table for Daytona 675
• The MAP value is now in hPa (it was in mmhg by mistake)
• I3 & I4 ignition table for Rocket III instead Ign(TP) & Ign(Map)
• Minimun screen size require is 1024x576 (Netbook 16:9)
• Map may be corrupted when modified on Comparison mode, fixed
• TPS active axis now resolved in some S3/Sprint Maps
• 2008x 'base map' signature now added to the program file
• TPS/RPM axes now 'live' in Fuel Trim table

Download from here: http://www.tomhamburg.net/Tunes_in_Hex_and_dat/TuneECU/TuneECUv1.6.6.zip


BR, Tom

 

[MikaK]

If the procedure never 'stopped', then when did you manually stop it?
I've tried with two PCs, one on XP and the other on Vista. So USB ports, for example, should be fine.
The cable is new and the only one I have. I was able to read the tables just fine. I then adjusted the secondaries and tried to download to the bike. I've been stuck here ever since.

The procedure ran through and gave a pop up "ECU recovery successful" (or something like that) Sorry for not mentioning this earlier. Despite of the pop up ECU remained "connected but unresponding". I had to run "Recover ECU" three or four times before everything was OK again.

Mika