Hondata

You are hitting a rev limit. Try disabling the lean protection.


Tried it...no help.

Lean Protection shouldn't be in effect anyway, since I have that set for "Engine Load is over 89 kPa"...and this is happening at minimal MAP levels.

I also tried "Disable Fuel Overrun Cut-off Delay" ...no help ...

Looking for advice on what else to try for smoothing out this symptom. At very low throttle inputs in cruise conditions, the engine goes in and out of overrun cutoff resulting in a surging/bucking of the car.

Contributing factors: high compression (12.5), big cams (Kelford 179-B), big injectors ...

Quick update…at a different track today. Unchecked the 100hz logging box and went to original kal with VSS and closed loop turned on.

No issues.

So it appears to be only a logging issue, not a engine control problem.

I'm starting to wonder if this is a real engine control problem, or just a datalogging problem.

Previously with V3, I've datalogged at the max of 20hz. Now I'm at 100. It's the only change I can think of.

I'm open to suggestions on things to try.

I'll be on track again Friday and Saturday for ...

What I really didn't like was that the datalogs showed the AFR's to spike incredibly lean in a couple of tables spots during these episodes. Not sure if real or not, so I tried running open loop with no VSS. Still same result at same place.

Thinking that maybe the VSS was the cause (signal drops out causing car to think it is not moving and pulling cam timing to 0, etc)...so I disabled the VSS.

Same result...though you can see the VSS being held at a constant 49mph (as it should) ...and then dropping to zero.

Note that the car seemed to be running fine through all of this.

I went back a couple days later with a plan to be more consistent and try testing some possible causes.

Session 1 was run as before, and got same result at 6:29.

Second session out, I start getting weirdness. VSS, MAP, TPS all drop in unison. ECU then commands weird CAM angles.

First starts at 5:33, then again at 6:19 and 6:29.

Greetings,

I recently sent in my PRB ECU to be upgraded from V3 to V4 KPro. It came back with firmware installed that required me to move to the current Beta version of KManager (4.5.8.0).

Since then, I have been seeing regular sensor dropouts in the datalogs. Nothing else has changed on the car ...

How's about supporting closed loop and lean protection from widebands connected via the V3 Analog Inputs connector? That input is much cleaner than the existing options, as there is no concern for cutting out resistors, checking for capacitor presence and the like with the existing original four ...

You need to show the tables under boost as well, as it is interpolating a lower value from the higher columns. Everything looks pretty normal.

Bingo!

Yep, that's it. While it is a naturally aspirated motor, at these speeds (140+) it is getting a little bit of positive pressure due to my new cold ...

Greetings,

Had something weird show up during a track day over the weekend.

My high cam table is set entirely to 30 degrees cam advance, yet I am seeing CAMCMD values less than that periodically at WOT. The datalog snippet shows this most noticeably at 1:38 timestamp. That one may be related to ...

It appears that there is only one set of supplied Knock tables for all existing base .kals. Further, it appears that the tables are position-based, rather than RPM-based. There tend to be two high speed RPM scales typically used in the supplied kals, one which goes from 3000-11000, and the other ...

It is either a cable problem or a problem with the seedometer in the cluster as that is where the VSS is located. This should be fixed.

For sure, I do intend to fix it. And I'm pretty sure it is the cable not the speedo, since the needle wavers on two different speedos I've had in there (one with ...

Greetings,

Just got my KPro and am doing some basic street tuning off a base map until my favorite dyno shop comes back on line (they've had to move). One thing I noticed is that my VSS signal is quite erratic. I'm fairly certain this is due to a sticking speedo cable, as I also see a little bit of ...