Page 1 of 2
KManager Beta V1.3.2.0
Posted: Thu Dec 20, 2007 1:31 pm
by Hondata
This is a beta release of KManager. The major change is to the Display window, which now has sensor displays similar to HondaLogger. More information can be found in the Help file, under 'Display Window'.
KManagerV1-2-3-0.exe
With the Beta it is possible that future updates will not be able to load the saved display settings, so don't put too much effort into your screens at this point.
Here are some diplay templates you can begin with:
Posted: Mon Dec 31, 2007 12:32 am
by Razathorn
What would be extra super cool would be if we could setup audio alerts for certain conditions. That way, if you're street tuning, a pair of headphones could let you know if you're lean or knocking.
Posted: Wed Jan 02, 2008 9:51 am
by mike93hatch
it has audible alerts...
Posted: Wed Jan 09, 2008 2:46 pm
by mucter
Can we do gauges like a fighter jet ala the Lamborghini Revent?n ?? heh
Posted: Wed Jan 09, 2008 8:36 pm
by 06 nbp type s
two things, need to be able to change the colors of the text in the guages and when i load a pre made set, it cuts the right side of the display off even if i make it full screen
Posted: Thu Jan 10, 2008 7:37 pm
by nzitr
I have a PRC ECU on my 2001 JDM DC5R and I have an ignition timing issue when I run this version of KManager.
Openloop mode above 5900 rpm produces a 10 degree retard in timing.
I've checked my calibration and I can't see any issues that would cause this. Going back to the previous version sorts the issue out. I've tried several times with the same result.
Do you want/need any files from me?
Cheers,
David.
Posted: Mon Jan 14, 2008 11:27 am
by Hondata
Yes, a datalog and calibration would be good. There were no changes made to the ECU code in the beta - what versions are you comparing?
Posted: Mon Jan 14, 2008 12:02 pm
by nzitr
I am running 1.2.2.9 normally.
First thing I have to do is fix the temp conversion tables. I suspect there has been a change to the way they are stored based upon the conversion that occurs.
I will need to do another datalog and post that up as I only have 20min duration ones currently. I'll try and get it done later today.
Cheers.
Posted: Mon Jan 14, 2008 11:33 pm
by nzitr
- serial number
3050
- what sort of vehicle you have
2001 JDM DC5R
- what sort of ECU you are using
PRC
- Problem Report
Above 5900 rpm open loop (or high load perhaps) approx 10 degree ignition retard compared to the map. Have tried installing 1.2.3.0 3 times with the same result. Going back to 1.2.2.9 fixes the issue. Today tried downloading calibration from ecu and it appeared to match the one I uploaded.
Looking at the timing in general it does look 2 degrees retarded compared to the map so I wonder if the un-checked nitrous 1 & 2 retard settings are coming into play as they total -8 degrees? I might zero them out and try it.
The tune is still a work in progress and car is fairly standard bar Mugen Intake/Header/Twinloop.
Regards,
David
Posted: Tue Jan 15, 2008 12:10 am
by nzitr
Just tried a run with zero values in the nitrous tables and there was no difference. I got a better datalog of the change at 5900rpm though.
Posted: Tue Jan 15, 2008 10:23 am
by Hondata
Ok, we're looking at it.
Posted: Tue Jan 15, 2008 2:57 pm
by Hondata
It is a problem with the IAT ignition retard table, where the highest value is too low. The quick solution is to open the calibration with notepad, and remove the two sections [IATRetardLow] and [IATRetardHigh] (remove the whole section group - delete 6 lines for each section).
Posted: Tue Jan 15, 2008 4:11 pm
by nzitr
I will try that thanks.
I did notice an interesting behaviour around the temp conversion moving from 1.2.2.9 to 1.2.3.0
I run with degrees C as my unit. When I open a file saved under 1.2.2.9 in 1.2.3.0 the temp conversion points get modified. They appear to be going through a degrees F to C conversion so they end up really low. The actual compensation factors stay as before. I had modified these points up to where they were in my 1.2.2.9 cal.
Regards, David.
Posted: Tue Jan 15, 2008 4:38 pm
by nzitr
I've just deleted out the IAT retard tables as you suggested and re-opened and saved the file and the new values are much higher.
I take it these are now saved as degrees F and that the cal is now saved consistently despite the units used.
Have tried it and there is no more timing retard. Thanks for your speedy efforts.
Posted: Wed Feb 20, 2008 3:29 pm
by Stuart
Hondata wrote:It is a problem with the IAT ignition retard table, where the highest value is too low. The quick solution is to open the calibration with notepad, and remove the two sections [IATRetardLow] and [IATRetardHigh] (remove the whole section group - delete 6 lines for each section).
just spotted this...
is this the temp related ign table?
what's the syntax of this table, been looking for this function...
any chance of adding it to Kmanager?
PS. whilst your at it, it would be nice to ba able to calibrate a different AIT than the stock one (as the fast acting ones are different resistance)