Page 1 of 2

Fuel Volumetric Efficiency map tuning problem

Posted: Sat May 17, 2014 1:25 am
by Jaape
I’ve got tuning problem with a Nistune. ECU do not response right when I’m trying to tune Fuel Volumetric Efficiency map. For example if I want to tune idle mixture I have to adjust values about 1000rpm lower and higher Load values. Here is a example picture.
Nistune problem.jpg
(241.13 KiB) Downloaded 5160 times
Same problem occurs everywhere in this Fuel Volumetric Efficiency map. The car is European model -98 Nissan Primera GT with SR20DE engine.

-Jarno

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Sat May 17, 2014 2:24 am
by raddy
hi there,unfortunatelly this is known issue and we are waiting for correction for quite long time. Hope that Matt will investigate it soon.

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Sat May 17, 2014 4:55 am
by UNISA JECS
Yup you are not alone I have this same problem with my B14 SR20DE Type 4 ECU, once this is fixed its going to be awesome!

I actually made a video of the problem, as you can see I change the values in the cell's and you can watch my air fuel ratios change albeit the highlighted cells remain the same.

http://youtu.be/BfINxg2yIIs

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Sat May 17, 2014 6:45 am
by Jaape
Nice video! Let's hope the problem gets fixed soon.

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Tue May 27, 2014 7:49 am
by unreal-
This makes things MUCH easier to understand. Been wondering why in the world i couldnt fine tune my idle mix with the VE table when editing the values that were highlighted. Seems that The VE table is the last key to a lot of problems that have been popping up around the forums. Once the tracing of it gets fixed, then i can improve my tune. Not exactly sure why its taken so long to fix this, but im sure it will be corrected soon.

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Tue May 27, 2014 2:15 pm
by Matt
Should be in about two weeks. Almost finished other work now

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Thu Jun 19, 2014 6:34 pm
by Matt
Just a heads up that I'm starting work on this one now. At the moment I'm looking at the P11 VE table and adding feature pack to this one whilst doing the code disassembly since I'll be adding the final injection multiplier to this one for a customer. More to follow. There is a lot of disassembly work going on in the background with these models and takes time!

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Thu Jun 19, 2014 7:22 pm
by raddy
thats good news Matt. Just hope that ve map correction doesnt need base image update...

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Fri Jun 20, 2014 11:19 am
by Matt
No its only a column tracing fix within the software

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Sat Jun 21, 2014 4:55 am
by UNISA JECS
:) :D

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Thu Jul 17, 2014 5:33 pm
by Matt
Update now in 1.2.8 version

I'm now reading the TPS index directly from the ECU (instead of consult TPS parameter). I've got most ECUs in there now but tested so far S14 KA24DE, P11 SR20DE and ER34 RB25DET

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Thu Aug 28, 2014 9:20 pm
by Jaape
I tried ver. 1.2.14 and 1.2.15. VE tuning still isn't working correctly. Those versions work just like the older version of Nistune.

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Fri Aug 29, 2014 10:36 pm
by Matt
ok does the injector time change on the trace cell? I tested P11 ecu here on the bench. What rpm/tps area are you adjusting to test?

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Sat Aug 30, 2014 12:34 am
by Jaape
I just adjust idle fuel mixture. Lambda was changing when I tuned exactly same cells as in a picture at the start of this topic. Does ilde situation affect how the VE map works?

Re: Fuel Volumetric Efficiency map tuning problem

Posted: Sat Aug 30, 2014 12:33 pm
by Matt
Havent looked into idle with VE. Have to see if it looks at tps idle. Try increasing latency or tp min table