TuneECU, ECU on Roadster is not responding anymore

[Tom-Hamburg]

jaredmt,

Which driver for the cable you use?


BR, Tom

 

[jaredmt]

Two ... both posted here in these forums. Currently using the one you suggested:
http://www.ftdichip.com/Drivers/CDM/CDM%202.06.00%20WHQL%20Certified.zip

 

[Leif Almberg]

MikaK and jaredmt,

You have already heard that there give a new version? version 1.6.6

BR, Tom

but if I read the "Historique" correct this version only approves something for the Speed Triple:
1.6.6 Affichage des valeurs TPS & RPM dans la table Correction F
Ajout de la signature de la map 2008x (Speed triple).

 

[Tom-Hamburg]

The following have you tested?

http://www.tomhamburg.net/Tunes_in_Hex_and_dat/TuneECU/CDM2.04.06WHQL_Certified.zip

BR, Tom

Two ... both posted here in these forums. Currently using the one you suggested:
http://www.ftdichip.com/Drivers/CDM/CDM 2.06.00 WHQL Certified.zip

 

[Tom-Hamburg]

I'm not sure that Alain always documented everything. Just try.

BR, Tom

but if I read the "Historique" correct this version only approves something for the Speed Triple:
1.6.6 Affichage des valeurs TPS & RPM dans la table Correction F
Ajout de la signature de la map 2008x (Speed triple).

 

[jaredmt]

Tom ... I have now tested that driver too, on both the XP and Vista machines. No change. At this point I'm really suspicious of that cable, from process of elimination alone it's just looking pretty guilty. I am HOPING the new one arrives tomorrow as having my bike dead is killing me.
I'm happy to try any ideas until then ... for my part, I'm out of them (I've been alternating between using 1.6.4 and 1.6.6).

 

[Tom-Hamburg]

Then we can only hope it is really just the cable.

And do not kill yourself. I can see no blood.

BR, Tom

Tom ... I have now tested that driver too, on both the XP and Vista machines. No change. At this point I'm really suspicious of that cable, from process of elimination alone it's just looking pretty guilty. I am HOPING the new one arrives tomorrow as having my bike dead is killing me.
I'm happy to try any ideas until then ... for my part, I'm out of them (I've been alternating between using 1.6.4 and 1.6.6).

 

[MikaK]

I just took bull by the horns and altered a map (copied ignition table I4 to I3 and I2) modified earlier with ver. 1.6.4 with ver. 1.6.6.

Everything went smoothly! The map downloaded to ECU nice and quick and bike was alive and kicking after the operation. Version 1.6.6 seems to work fine according to my experiment!

Mika

 

[Leif Almberg]

you beat me by 2 hours! I will do the ignition tables change tonight. good not to be first everytime though..

 

[jaredmt]

Alright gentlemen ... the saga continues. The new cable arrived today ... and so far, no real changes. I get the timeout message each time I try. Tried w/ 1.6.4 and 1.6.6 on XP and Vista.
May I assume the goop in the bike's connector is protective grease that is supposed to be there? (I've assumed so thus far, but I'm grasping at straws now)
Any other way of trying to talk w/ the ECU?
I have a general vehicle OBD II unit. It won't talk to the bike (no surprise, surely isn't set to do so). It does stay linked to ISO9141 first though, if that means anything to anyone.

Out of ideas here guys. Anyone?