2005 and KManager

[Hondata]

Send the ECU to us.

[640k]

Send the ECU to us.

I plan to but I need an answer of projected downtime. I'll be without a car.

Thanks.

[Spunkster]

Once we receive it it will go out the same day as long as it is received early in the day.

[640k]

Send the ECU to us.

Will be sent overnight tonight. Thanks.

[640k]

I show the package delivered:

Tracking summary
Current Status Shipment delivered.
Delivered on 5/17/2006 9:27 am
Delivered to Receptionist
Signed for by D STEVENS

Let me know how it goes. I'm interested in seeing if you are able to determine if anything else is wrong...

Thanks!

[640k]

So I did what Matt said and created a new log from scratch (File-New). I'm still getting jumps in my speedometer. They don't seem to be happening as often but they still happen. Also, my cruise control is erratic around 80mph and almost impossible to use (I haven't tried lower speeds yet) and most of the time it cuts out and has to be reset.

It was explained to me that no one else is experiencing this issue, but the early 05 ECUs all seemed to have had this problem (what made them magically go away)?

Could it be the wire harness? Maybe a loose speed sensor wire? The jumps don't get logged in datalogs, but I certainly see it on the speedo.

[Hondata]

Did the behaviour improve at all? The very early (first 5 or so) 05 ECUs had a different resistor value (222 vs 471 near RM760), which is why the first 05 adapters had some problems.

First, make sure else that nothing is wired into the speed sensor signal (turbo timer, car alarm, gauges etc).

Second, datalog while cruising and make sure that the speed signal as reported by the ECU is steady.

If you're still having issues we would like to modify the ECU further to add an amplifier into the speed signal output.

[640k]

The behaviour has definitely improved, although the cruise control has not and I have no aftermarket gagues, etc. Also, the speedo doesn't blip as violently as before. Now its only 5 or so mph, whereas before it could be 10+.

There are a few people on CRSX who are reporting the problems (especially with the cruise). Does cruise adjust based on the value the ECU is sending to the cluster? If so, that would explain the issue with the cruise.

Has anyone thought about monitoring the difference in voltage from the speed sensor going to and from the ECU? If there are inconsistencies, I could see the need for an amplified signal, but I would hate to put any additional stress on the ECU with something like that.

Would it be possible to get a temporary replacement ECU while Hondata works with my ECU to determine the trouble?

Thanks.

[Hondata]

Can you work through the steps outlined in my above post first?

[640k]

Did the behaviour improve at all? The very early (first 5 or so) 05 ECUs had a different resistor value (222 vs 471 near RM760), which is why the first 05 adapters had some problems.

The behaviour improved, but is still existant. Cruise control has not improved.

First, make sure else that nothing is wired into the speed sensor signal (turbo timer, car alarm, gauges etc).

I have no aftermarket anything on my car that would interfere with the speed signal. All I have is KPRO, IMG, JRRH and CAI.

Second, datalog while cruising and make sure that the speed signal as reported by the ECU is steady.

I've posted datalogs before and the signal is constant. I have recently performed datalogs and the speed signal appears to be constant.

If you're still having issues we would like to modify the ECU further to add an amplifier into the speed signal output.

See my post above.

Thanks.

[Funkmobile]

Any updates on the speedo issue here?

All I have in my car is CAI and Header and I have speedo blipping as well.

[Hondata]

Here's some more information. The cruise control unit uses a PID algorithm to adjust the throttle based on the vehicle speed and past throttle histry. There is some delay factor for the cruise control to adjust the throttle, then another delay for the vehicle to change speed, and another delay for the speed to be reported to the cruise control unit.

These time delays and the response of the vehicle is dependent on a gazzilion factors, down to tire pressure, elevation, engine output, incline, gearing, head wind, tire size, sensor variation, vehicle load, ac status etc, but unfortunately, the cruise control unit only knows the vehicle speed and throttle angle. Thus when things do wrong, the cruise control over compensates due to the delays above not matching the PID algorithm settings.

Testing on several different vehicles, I am fairly sure that the output signal is ok, and the problem lies with fluctuation / averaging the speed output. The problem is that the real solution is to change the PID parameters in the cruise control unit, which is out of scope for a solution, so the changes in the ECU are only a partial solution.

I have made a KManager beta (V1.2.1.7), which you can download here It has a different damping factor on the speed supplied to the gauges, and might help.

If you try the beta version, please provide useful feedback (like datalogs) rather than vauge symptomatic descriptions.

PS Cruise control only works betweem 25 and 125 mph.

[640k]

Here's some more information. The cruise control unit uses a PID algorithm to adjust the throttle based on the vehicle speed and past throttle histry. There is some delay factor for the cruise control to adjust the throttle, then another delay for the vehicle to change speed, and another delay for the speed to be reported to the cruise control unit.

These time delays and the response of the vehicle is dependent on a gazzilion factors, down to tire pressure, elevation, engine output, incline, gearing, head wind, tire size, sensor variation, vehicle load, ac status etc, but unfortunately, the cruise control unit only knows the vehicle speed and throttle angle. Thus when things do wrong, the cruise control over compensates due to the delays above not matching the PID algorithm settings.

Testing on several different vehicles, I am fairly sure that the output signal is ok, and the problem lies with fluctuation / averaging the speed output. The problem is that the real solution is to change the PID parameters in the cruise control unit, which is out of scope for a solution, so the changes in the ECU are only a partial solution.

I have made a KManager beta (V1.2.1.7), which you can download here It has a different damping factor on the speed supplied to the gauges, and might help.

If you try the beta version, please provide useful feedback (like datalogs) rather than vauge symptomatic descriptions.

PS Cruise control only works betweem 25 and 125 mph.

Does this affect the speedo blip? I've never seen the speedo blip while on cruise control, however, I have had the cruise control cancel as if there was a blip.

If timing is a big factor in how the cruise control responds, why does it cancel?

[Ratio]

I have been having the same problems. I will try to get a datalog soon. I have had sometimes very rapid and frequent jumps in the speedo. Just like 640k I have had my speedo jump significantly twice in one 3rd gear datalog but I do not have the log anymore. Should I be sending my ECU to you guys? I also do have a 5.06 final drive and noticed that gearing could cause some of it.

[640k]

I've updated to 1.2.1.8 and am still having CC and speedo blip issues. I plan on datalogging soon as well as recording video of the occurrances.