Cool FlashPro Easter Egg!
the most ideal thing to do if you want to target leaner afr's would be to mess with the closed loop target lambda tables like hondata themselves said. but the thing is that they don't work. they've had those tables for a while now and they never work. on the last update they said that it works but it still doesn't. i was tuning a civic si with flashpro the other day and i tried targeting leaner afr's at part throttle and the ecu still wants to target stoich.
i have messed with the wot lambda adjustment table and i've noticed that if i went too lean on the afr targets in the full throttle columns, the ecu would stay in closed loop even in full throttle which i don't like. i'd rather leave the ecu in open loop at full throttle and to be honest, if it were up to me, i'd leave it open loop the entire time.
on cars running k-pro i usually leave the ecu in open loop. they also have the same closed loop target lambda tables on the k-manager software, but those also don't work on the k-manager software.
i have messed with the wot lambda adjustment table and i've noticed that if i went too lean on the afr targets in the full throttle columns, the ecu would stay in closed loop even in full throttle which i don't like. i'd rather leave the ecu in open loop at full throttle and to be honest, if it were up to me, i'd leave it open loop the entire time.
on cars running k-pro i usually leave the ecu in open loop. they also have the same closed loop target lambda tables on the k-manager software, but those also don't work on the k-manager software.
my very question is how can we control the fuel system in closed-loop?
closed-loop operation is really closed
we only have a target AFR parameter with low load/high load crossover vacuum level (and that is ~50kPa as far as the FlashPro Manager helpo file says). we are rather unsure that this hi/lo divided target AFR mechanism does not work properly, instead targeting to 14.7(=closed loop target lambda setting for all loads). for instance, we can not set low load zone for 15.3 (which is trying to lean out the system for low loads). am i correct?
since we do not have much left with target AFR, we can increase/decrease specific zones at the fuel table. say, i am targeting 14.7 in general. but for specific zones of the fuel map i want to be rich (say 13.7), and for some zones i want to be lean (say 15.3). and please note that all of these zones are in low-cam operation, and nearly all in closed loop.
will ECU trim (STFT) the specifically adjusted zones of the fuel map so that it targets 14.7 immediately?
i was happy with gernby's previous easter egg
because it was just the feature that i need for the above configuration...
closed-loop operation is really closed
we only have a target AFR parameter with low load/high load crossover vacuum level (and that is ~50kPa as far as the FlashPro Manager helpo file says). we are rather unsure that this hi/lo divided target AFR mechanism does not work properly, instead targeting to 14.7(=closed loop target lambda setting for all loads). for instance, we can not set low load zone for 15.3 (which is trying to lean out the system for low loads). am i correct?since we do not have much left with target AFR, we can increase/decrease specific zones at the fuel table. say, i am targeting 14.7 in general. but for specific zones of the fuel map i want to be rich (say 13.7), and for some zones i want to be lean (say 15.3). and please note that all of these zones are in low-cam operation, and nearly all in closed loop.
will ECU trim (STFT) the specifically adjusted zones of the fuel map so that it targets 14.7 immediately?
i was happy with gernby's previous easter egg
because it was just the feature that i need for the above configuration...
For the ECU to change the target lambda from 14.7, all three tables and the overall target must be changed. Just changing the overall target will not have any effect.
i can not say that i understand the above 100%. we have 3 different AFR parameters but two different zones, etc...
i tried making those 3 changes the same afr and it was only targeting stoich, no matter what the value.





