KManager V1.4.5.7 Beta

[Corey872]

Hondata - Thanks for looking into the target AFR issue when you get the chance.

I did some testing a few years ago with a small circuit I built to provide an offset to the O2 sensor. It would essentially give the same thing Kmanager is delivering now...a closed loop target AFR leaner than 14.7. I found definite reductions in injector firing times when switching between 14.7 and ~15.7 AFR given very controlled and equivalent on-road driving conditions. Though there were always enough environmental changes from tank-to-tank I was never able to pin down an exact mpg savings.

Based on the injector times it looked like a solid 3-5% reduction in fuel going to the engine, sometimes close to 10% in ideal conditions. Though considering a person may spend 50% of the time in 'lean burn' and maybe 10-15% under 'ideal lean burn', the overall effect may only add 2-4% mpg gain. This may only add 6-12 miles to the range of a 300mile tank of gas. But with $4.00+ premium gas (or almost $3.00/gallon on E85) the overall savings still add up pretty quick.

One thing I've come to appreciate after 18 years in the R&D industry and dealing with many fuel efficiency projects is the great difficulty in pinning down small, but consistent fuel economy improvements over the wide range of operating and atmospheric conditions encountered over several tank-fulls of fuel.

Anyway, just wanted to pass along a few bits of info. Keep up the good work and many thanks for the continued improvements!

Corey

[doms22]

Here I tested the V 1.4.5.4 in my PRA ecu
Works very well : closed loop, Ignition Knock Control OK

Thanks :)

[Corey872]

PS - Did just get my highest mpg tank yet using the Target AFR around 1.06 lambda. Went 373 miles on 12.9 gallons = 28.9 mpg on E85! Average of the previous two tanks at target lambda 1.00 was 26.6 mpg. Will be interesting to see if the trend continues or if this was a one time event due to favorable driving conditions.

[magnEsium]

Getting the following error a lot.. Especially when I try and input custom values in to the wideband setting in Options

Application: Hondata KManager 1.4.5.4 - C:\Documents and Settings\magnEsium\Desktop\06_TypeS_t3t4(21).kal
Time: 4/20/2011 9:20:31 PM
Expection: EAccessViolation
Message: Access violation at address 0058068A in module 'KManager.exe'. Read of address 00000008
Class: TApplication
Form: TableForm
Control:
Stack trace: 0x0058068a 0x004a129c 0x00409d9c 0x0053518b 0x004db0a2 0x7e418734 0x7e418816 0x7e428ea0 0x7e428eec 0x7c90e473 0x02e100a6

[Hondata]

Corey: That's great.

magnEsium: Fixed for the next release. Thanks for the report.

[Crxmanror]

I was wondering if there could be some changes made to the two step. The two step currently on the K-Pro is pretty slow compaired to other two steps on the market. Is there any way the two step on the k-pro can be sped up?

[Hondata]

I'll add it to the request list (this should have been a new topic).

[Crxmanror]

I'll add it to the request list (this should have been a new topic).

Thanks... that would help out so much.

[magnEsium]

If this helps, here is another one, I could do this all day lol

File>New and Selecting the factory PRA calibration:


Application: Hondata KManager 1.4.5.4 - untitled
Time: 4/22/2011 10:58:12 AM
Expection: EAccessViolation
Message: Access violation at address 00456333 in module 'KManager.exe'. Read of address 00000050
Class: TTableGrid
Form: ExceptionForm_1




Application: Hondata KManager 1.4.5.4
Time: 4/22/2011 11:09:26 AM
Calibration loaded: Yes
Stack trace: 0x00430B1E 0x004116E7 0x00410161 0x004DAA3A 0x00548840 0x00548978 0x00548840 0x005484BB 0x004DB0A2 0x7E418734 0x7E418816 0x7E42927B 0x7E4292E3 0x773F735F 0x773F7441 0x773F9746 0x7E418734 0x7E418816 0x7E42A013 0x02DC012E 0x00548924 0x00548840 0x004DB0A2 0x7E418734 0x7E418816 0x7E4189CD 0x02E00A0D 0x00534E68 0x00401B54 0x0057BBAF
Table information:
Number of tables: 16
Table type: 2
High speed: 0
Table 0: Type 0 High 0 'Ignition low speed'
Table 1: Type 0 High 1 'Ignition high speed'
Table 2: Type 1 High 0 'Fuel low speed'
Table 3: Type 1 High 1 'Fuel high speed'
Table 4: Type 2 High 1 'Cam angle low speed'
Table 5: Type 2 High 1 'Cam angle high speed'
Table 6: Type 4 High 0 'WOT comp low speed'
Table 7: Type 4 High 1 'WOT comp high speed'
Table 8: Type 5 High 0 'WOT comp (cat protect) low speed'
Table 9: Type 5 High 1 'WOT comp (cat protect) high speed'
Table 10: Type 3 High 0 'Knock ignition limit low speed'
Table 11: Type 3 High 1 'Knock ignition limit high speed'
Table 12: Type 6 High 0 'Knock sensitivity low speed'
Table 13: Type 6 High 1 'Knock sensitivity high speed'
Table 14: Type 7 High 0 'Knock retard low speed'
Table 15: Type 7 High 1 'Knock retard high speed'



Application: Hondata KManager 1.4.5.4 - untitled
Time: 4/22/2011 11:10:38 AM
Expection: EAccessViolation
Message: Access violation at address 00455862 in module 'KManager.exe'. Read of address 00000008
Class: TTableGrid
Form: ExceptionForm
Control: memExceptionDetails
Stack trace: 0x00455862 0x00435754 0x0049e506 0x00518a5e 0x00518f8f 0x0049c116 0x0054c891 0x005489d8 0x00548ea8 0x0054c829 0x00545813

[Hondata]

Thank you. I have found the issue - in some calibrations the low speed cam table has a setting of 'high speed'.

The workaround is to edit the calibration and change the table4 definition to HighSpeed=0:

[Table4]
Rows=20
Cols=16
NumCamTables=1
HighSpeed=1

[Table4]
Rows=20
Cols=16
NumCamTables=1
HighSpeed=0

I will make a new beta release shortly.

[Hondata]

This issue has now been fixed, and a new beta is available.

[KnightX]

i just try to DL the new bata but after the install it wont open up... no error sign just nothing happens... help?

[Corey872]

i just try to DL the new bata but after the install it wont open up... no error sign just nothing happens... help?

'Can't seem to get 1.4.5.(x) working in Win 7 64bit'
viewtopic.php?f=12&t=12256

[Spunkster]

Who is the manufacturer of your computer?

[rikitaun]

This issue has now been fixed, and a new beta is available.

at last!!! lol..lol..lol

this version runs perfect... many thanks