Hondata

test ce 26 janvier 2011 version 1.4.5

Sometimes when I'm accessing a calibration I get an error. I also had this error every 30 seconds while datalogging today.

The error reads,

ERROR MESSAGE wrote:"Access Violation at address 00430853 in mobile 'MKanager.exe". Write of address 00000024".

doms22 wrote:ok with 1.4.1 close loop ok

You will have to use the non-beta version then until we can see what is causing this in the beta version.

ok thanks spunkster

Anybody else having problems with the ecu not reading the values on the map. Example when I do a wot datalog the cam angles start falling after vtec. Instead of goin to 50 deg they drop to around 35 and go down. Also I had to reload the map a few times this morning in order for vtec to even engage. This is not working for this new problem. It also seems that the fuel map isn't being read either. The tune is the same tune ive been running for over a year and a half...it is a good tune until today. I'm using 1.4.5 version.

For those of us that is already tuned to a certain type of gas(93 octane for me) should we go ahead and enable Stock Knock Control Logic and leave all the other tables alone so we have an added safety in case we get a bad-batch of gas and reduce knocking?

or we have to go in and change the knock control tables to be better suited for boost? I am assuming the knock limits and etc would be different for a stock k20 vs a boosted k20, therefore the tables needs to be adjusted for each car?

How are you guys getting on with the reported bugs?

Is there any chance of a future release where the wideband input from the ELD can be used for the lamda targets? I understand that currently the ELD input is only for display and datalogging purposes only, but for almost all S2000 users, the current implementation limits the functionality of Kpro.

I realize that this may be a small subset of your user base, but it would fully unlock the Kpro for everyone. Not sure how much recoding would be required, but I believe it is at least worth taking a look at and letting us know the feasibility of it.

I also would like to see wideband readings used for closed-loop operation if possible. Depending on how much wiggle room you have as far as EPROM size, writing an algorithm that utilizes wideband input could provide much more reliable and precise operation - a wideband can tell "how far" from the target lambda it's running and adjust accordingly, rather than just saying "ok I'm rich time to inject less fuel, I don't eally know how much less though"

It is worth noting, though, that I haven't tried or even downloaded the new version yet. The release notes mention that you added some user control over the closed loop tables. Does this mean we can specify a target AFR? If so, this would really imply that you're using the wideband reading for closed loop operation already.

Floppie wrote: It is worth noting, though, that I haven't tried or even downloaded the new version yet. The release notes mention that you added some user control over the closed loop tables. Does this mean we can specify a target AFR? If so, this would really imply that you're using the wideband reading for closed loop operation already.

The stock k20 o2 is a wideband which is what they're referring to in their nonmenclature. My request was specific to the aftermarket wideband support present in the ELD input

The stock sensor outputs both a wideband signal (for datalogging/tuning, I'd imagine the stock purpose is so that the ECU can throw a code if it detects an extremely rich/lean condition) and a narrowband signal, which is what's used for closed loop operation.

Floppie wrote:The stock sensor outputs both a wideband signal (for datalogging/tuning, I'd imagine the stock purpose is so that the ECU can throw a code if it detects an extremely rich/lean condition) and a narrowband signal, which is what's used for closed loop operation.

Please do not post information as fact if you do not know the facts.

The stock RSX primary O2 sensor is wideband. It does not give both wideband and narrow band signals.

Hi,
Is there an update due soon as I still can't get the the latest beta to work correctly?

Cheers,

Hey Spunkster,

has anybody had issues with disabling the hondata boost controller and having weird boost creep only in 3rd gear from around 3000rpms?? It only happens in that condition ever since I uploaded the kal from the new kmanager.. HEre is a datalog