Results 1 to 7 of 7

Thread: Fuel trim tuning

  1. #1
    Tuner in Training
    Join Date
    Jan 2019
    Location
    NH
    Posts
    23

    Fuel trim tuning

    So how do you guys set up fuel trim data logs to match X and Y axis of the Speed Density Calculator? What PID's are you using? MAP is inferred in my car so I assume I should be plotting MAF vs RPM? Or is MAP calculated accurate enough?

    I have MP monitoring setup so I can tell what MP I'm in relative to fuel trim event.

    I'm I missing anything else?


    Thanks Guys

  2. #2
    Advanced Tuner
    Join Date
    Feb 2012
    Location
    TEXAS
    Posts
    631
    Maf vs Peroid
    STFT + LTFT
    wb eq bank 1
    wb eq bank 2
    eq ratio commanded

  3. #3
    Tuner in Training
    Join Date
    Jan 2019
    Location
    NH
    Posts
    23
    mstang_man

    I assume you're doing STFT + LTFT vs RPM so you can transfer/copy past into Speed Density Calculator? If so, how did you set up your X and Y axis?

  4. #4
    Advanced Tuner
    Join Date
    Feb 2012
    Location
    TEXAS
    Posts
    631
    The speed density calculator was broken so i never had a chance to use it, You'll notice the table is RPM vs. MAP vs. Load. The idea is, you hit a target RPM and MAP in steady state, and adjust the load to either the actual load if you're a MAF car, or adjust it based on fuel trims assuming your fuel model is correct if you're an SD car.
    Lock your car in a given Mapped Point, or use the logged parameters to make sure you update the correct mapped point.

    For example, if we're on a MAF Equipped Coyote, and we hit steady state, we may notice the load in our table is off from what we actually have measured via our installed MAP sensor and actual load. If we dial this in, we improve airflow anticipation and throttle control as the ECU can more accurately calculate airflows downstream of the MAF. By remaining in steady state, we aim to take out the effect any transient corrections based on the current model may have. Without a physical MAP sensor, this calibration is also just guess and check at that point. You cannot use the inferred MAP to try to correct it, as that's what you're trying to correct!

    For SD cars, this is all you have to estimate cylinder airflow! You need this dialed in as it is the vehicles air model, which everything else based on load is based off of. Its the only way the engine knows how much air is actually entering the cylinders.
    Last edited by mstang_man; 05-23-2019 at 07:51 PM. Reason: SPELLING

  5. #5
    Tuner in Training
    Join Date
    Jan 2019
    Location
    NH
    Posts
    23
    It sounds like my plan has holes then. I have my datalog set up showing mapped point weight% 0 through OP in the channels. I see it does indicate % as I log showing real time what MP is being used at the time either in whole or shared between MP's. I have absolute load vs RPM histograming STFT + LTFT. So as I play though the log, highlighted trim cells correlate to used MP points. I planned to go into speed density calculator and edit the respective cell vs MP to edit the Quadratic, slop, offset terms. The problem is no dyno. I though just driving around would collect enough data to trim out the fuel trims. I can see your point though that transient enrichment may taint my STFT + LTFT histogram data, or will it if I raise my count number to 10 or higher to increase the averaging of my collected data.

  6. #6
    Advanced Tuner
    Join Date
    Feb 2016
    Posts
    482
    Any pids set up for fuel trims ?

  7. #7
    Senior Tuner CCS86's Avatar
    Join Date
    Nov 2017
    Location
    Austin
    Posts
    1,089
    You don't use fuel trims to correct speed density tables, at least on Coyotes. SD tables do affect fueling, but that isn't an accurate way to correct them, because many other things affect fueling.

    Just setup a chart to match the SD calculator table, using calculated MAP and RPM for your axis values, and plot air load.

    You can then duplicate that chart and filter by MP weight.