KManager V1.4.5.7 Beta

VT-Doo · Post by **VT-Doo** » Thu Mar 03, 2011 12:17 am

Hondata wrote:rikitaun & VT-Doo : do you still get the access violation error with the beta version?

If so, then please can you email us the KManager.ini file?

Will do.
With the time difference and the fact I've just started work it may seem like I'm taking my time about it :roll:

Hondata wrote:
VT-Doo wrote:English UK is foreign :?:
Scottish sure as hell is.

Oh, fighting talk...you should see us after a wee swally :lol:

rikitaun · Post by **rikitaun** » Thu Mar 03, 2011 2:43 pm

The .INI file has :

TableType=0
TableCamAngleIndex=3
TableHighSpeedCam=0

Change by zero but didn't work.. acces violation again... :(

Corey872 · Post by **Corey872** » Thu Mar 03, 2011 6:24 pm

Not to hijack the thread, but when does the .ini file get written to the directory? When I install 1.4.5 and look in the directory mentioned earlier, there is no Kmanager.ini file at all. Should it be written at the install, or only once Kmanager opens?

As mentioned in my earlier thread, I can't get 1.4.5 to open on this windows 7 / 64 bit machine.

Post by **Hondata** » Fri Mar 04, 2011 10:49 am

rikitaun: What version of windows are you using (including the language?)

Corey872: We've answered your question in your thread - anti virus software is deleting KManager upon install.

ruloSI · Post by **ruloSI** » Sat Mar 05, 2011 2:28 pm

Hondata wrote:rikitaun: What version of windows are you using (including the language?)

Corey872: We've answered your question in your thread - anti virus software is deleting KManager upon install.

What's going one with the action violation "xhexmessage" happening once you start datalogging for a bit.

I'm also having an issue with Lambda overlay function, I keep having to go in and going into setting once I start datalogging to see the % changes. Thanks for your support.

Best regards,

Rulo

gtuning · Post by **gtuning** » Sun Mar 06, 2011 11:09 am

SN 8998
K 1.4.5.0
TYPE R EP3
ECU: PRA

After kmanager update from 1.4.1.0 to 1.4.5.0 hardware version change from 2.16 to 121.16. Is that problem or it is normal ? I have not noticed any other problem (communication ili adjustment ecu).
Thanks in advance for your reply

rikitaun · Post by **rikitaun** » Sun Mar 06, 2011 12:15 pm

Hondata wrote:rikitaun: What version of windows are you using (including the language?)

I use win xp version 2002 service pack 3, Spanish language.

Post by **Hondata** » Mon Mar 07, 2011 12:51 pm

ruloSI: Can you give use the address and describe what conditions are necessary to bring up the error?

gtuning: Seems to be a USB driver problem. I'd suggest un-installing the USB drivers, and then re-installing them.

gtuning · Post by **gtuning** » Wed Mar 09, 2011 12:32 pm

Hondata wrote:ruloSI: Can you give use the address and describe what conditions are necessary to bring up the error?

gtuning: Seems to be a USB driver problem. I'd suggest un-installing the USB drivers, and then re-installing them.

Thanks for the advice but it did not fix the problem

VT-Doo · Post by **VT-Doo** » Fri Mar 11, 2011 1:48 pm

Hondata,

Is this version of KManager compatible with Apple's operating :?:

Post by **Spunkster** » Fri Mar 11, 2011 2:06 pm

No, our software will only run in Windows XP, Vista or 7.

Corey872 · Post by **Corey872** » Fri Mar 18, 2011 7:30 am

Clearing out some of the comments in my 'notes' bin:

For the new version is any of this possible or maybe already incorporated?:

Ask about unsaved datalogs when closing, similar to unsaved cals. (Possibly option to turn either one off/on)

Option to keep cursor centered on graph and scroll data during datalog playback, instead of static data and cursor running off screen.

Possible to zoom in/out on graph with Ctrl+ '+' and Ctrl+ '-'. Or even better, a section where various shortcut keys can be assigned by the user.

Possible to have parameter tracing follow idle/light and medium/heavy load as well? (where applicable) Tracing Low/high cam would be nice, too - though it is a little more obvious when that transition is made.

Also (at least up to 1.4.1) when I trigger datalog, the "on" button never triggers in the sensor list. Is this only for onboard datalogging? Could it be expanded for all datalogging - I've put an indicator directly on the display panel, but it never lights up because the sensor never 'triggers'.

eXceed · Post by **eXceed** » Sun Mar 27, 2011 3:46 pm

Any news on a new version? Been almost 2 months without an update :o lol.

VT-Doo · Post by **VT-Doo** » Fri Apr 01, 2011 5:31 am

rikitaun wrote:The .INI file has :

TableType=0
TableCamAngleIndex=3
TableHighSpeedCam=0

Change by zero but didn't work.. acces violation again... :(

I did the same last night and still the problem persists.

I am using a new netbook running Windows 7 32-bit starter edition. English UK.

The error even appeared without being connected to the car. I was editing a new Display and every time I moved the mouse the error appeared...then it stopped...

The error mainly appears when I'm datalogging, every few minutes. It does not affect the ECU nor does it affect the datalog itself.

On a separate note;
I run with temperatures showing in Celsius, however, the figures under the Advanced tab do not change accordingly. You can only change the target air/fuel ratios at temperatures which are too high and unfortunately useless (over 100degC). The temperature figures can not be changed.

Why are the standard air/fuel targets 14.59 rather than 14.7 ?

Thanks,

Post by **Hondata** » Fri Apr 01, 2011 9:54 pm

Just to confirm, are you getting the access violation at the same address?

I believe it is related to the regional settings and have spent some time fixing the way localization works, which may or may not help the problem but had to be done anyhow.

I have fixed the display of temperature units for the target lambda.

Although the stoichiometric ratio for gasoline is often given as 14.68:1, actual pump gasoline ratios are usually less. Honda uses 14.58:1 in some places, and 14.7:1 in others. For the 10% corn ethanol blend used in the US true stoichiometric must be around 14.15:1. It's easier to measure as a lambda ratio, which is always going to be 1.0 at stoichiometry. Everything the ECU does is as a lambda ratio rather than the air/fuel ratio, as the air/fuel ratio cannot be measured by the oxygen sensor; only the lambda can.