NefMoto

I've been looking around for a straight forward answer on this but I can't manage to find exactly what I'm looking for. Basically I've noticed a lot of various lamfa tables have their column changed to something like 50 / 65 / 75 / 85 / 90 / 97... Or something to that effect... My lamfa table stock (06A906032DL) is: 50 / 60 / 90 / 95 / 98 / 100... I remember reading something about the ECU always using the last value in the table all the time if the lamfa column isnt changed to something less than 100? or maybe I'm thinking of something else...

In the end what I would like to know is, to achieve the best results, should I adjust the values in "lamfa column" or leave them?
What is everyone else doing with lamfa? I've already made appropriate adjustments to kflbts for higher loads.

Thanks in advance!  :)

Some stock files have a lamfa that isn't used, and their axis (not "column") data is wrong (possibly due to oversight). Not your file.


If you don't know why the axis data isn't right for you, don't touch it.

(https://docs.google.com/uc?export=&id=0B1m5COB73xgEZXRIREFlMkdUcjA)

Well would I at least be correct to assume that in regards to the table I posted above, whenever lamfa is being used for fueling, the ecu will use the values in the first horizontal column all the way up to the 2nd value in the X axis? which in this case would be 60.01.. And so forth..

So with that being said, would changing the values in the X axis only affect the set point in which the ecu will switch over to the next column? So if my understanding is correct, 1 - 60.01 follows the 1st column in the X asis, 60.01 - 90.01 follows the 2nd column, 90.01 - 95.01 follows 3rd... etc. So finally if everything I just said is correct, I have one or two final questions.

Would it be beneficial for me to make some minor adjustments to the X axis on my lamfa table? and if so, will changing the values in the X axis (not "column")  :P have any affect on other maps? and what changes would need to be made to reflect the changes made to the X axis?

Thank you nyet, and thanks in advance to anyone who helps out.  :)

No, the ECU interpolates between columns; so you need to keep everything smooth.

Lamfa is pedal position as you'd know, so it follows what you fuel with a given pedal (so at WOT, (100% pedal)) you'll follow that last column. 

I don't like LAMFA because of it's resolution so I fuel using BTS.

For Stage 1, that table is fine IMO; consider having more fuel (so smaller numbers) at higher RPM for when you run more boost/timing.

Yeah but your the Royal Gargle Pop KING of East Dunbartonshire! 8) your demands might be met more efficiently by utilizing KFLBTS primarily as your preferred weapon of choice.  :D

Thank you for the tip on going a bit richer towards the higher end of the RPM range in my lamfa table...  I greatly appreciate that suggestion you rock Adam!

It's just because of the lack of resolution.  While it works, it doesn't work on load, and I'd rather fuel by load and have more range.

Just remember to monitor knock.  If you have no knock, you've got room for more boost and timing.  :)

right now I am logging the following:

"IgnitionRetardCyl1","IgnitionRetardCyl4","IgnitionRetardCyl2","IgnitionRetardCyl3","DynamicFactorO2S","NumberFaults","LambdaControl","AdaptationPartial","CountMisfireTotal","SelectedGear","LambdaPartProtection","TargetAFRDriverRequest","AirFuelRatioDesired","AirFuelRatioCurrent","BoostPID-I-Min","BoostPID I-Max","BoostCorrectFactorPIDIRange1","ChargeLimitPIDI","WastegateDutyCycle","EngineLossTorque","RequestedTorqueTractionControl","DriverRequestedRelTorque","MassAirFlow","EngineSpeed","MAXLoad","BoostPressureDesired","BoostPressureDesired","BaroPressure","BoostPressureActual","BoostPressureActual","AdaptationIdle","EngineLoad","EngineLoad","EngineLoadCorrected","EngineLoadSpecified","EngineLoadRequested","IntakeAirTemperature","EGTSensorBank2","EGTSensor","EffInjectionTime","FuelInjectorOnTime","TheorMaxInjectionTime","VehicleSpeed","ThrottlePlateAngle","AvgIgnitionRetardKnockControl","AccelPedalPosition","IgnitionTimingAngle","IgnitionTimingAngleOverall","CondOverboostActive",

I need to take a couple minutes tonight and clean it up a bit. If you have a spare moment would you mind helping me out with what, in your opinion, is necessary and what you think is basically dead weight? I'm confused as to what I should do about parameters that appear twice, one with _w at the end, one without... Which is the one I should log?
 Thanks adam.

Always the ones with w, they are 16 bit values vs. 8