Results 1 to 8 of 8

Thread: Commanded lambda problems. Commanding 1.2 and over at WOT

  1. #1
    Advanced Tuner
    Join Date
    Mar 2018
    Posts
    447

    Commanded lambda problems. Commanding 1.2 and over at WOT

    Title says it all.

    I put a new air box to manifold tube on the car and I noticed this. I then put the stock air tube back on and the problem did not go away.

    I cannot figure this out so please help.
    Attached Images Attached Images
    Attached Files Attached Files

  2. #2
    Senior Tuner
    Join Date
    Jan 2013
    Location
    Hawaii
    Posts
    2,101
    From your fuel trims and FDCO areas it looks like a scanner issue. When you switch the command units to Phi instead of lambda it looks correct. The difference matches fuel trims and on DFCO it goes to .85 not 1.177. Make sure you have the latest VCM and update if needed. If that doesnt fix it reach out to support and see if they can correct the units calculation.

    For now if you right click the channel and select units Phi, it should correct the numbers. Then use Phi in all your maths, charts, and graphs.

    Lambda2 Phi.PNG

  3. #3
    Advanced Tuner
    Join Date
    Mar 2018
    Posts
    447
    If I change the WB EQ ratio to Phi it then shows 1.20.

    Should I be concerned?

  4. #4
    Senior Tuner
    Join Date
    Jan 2013
    Location
    Hawaii
    Posts
    2,101
    WB EQ ratio looks right in lambda. ITs only the commanded that looks wrong until you switch it to Phi.

    Did you update your software to the latest?

  5. #5
    Advanced Tuner
    Join Date
    Mar 2018
    Posts
    447
    Yes I did, The first post is with the current beta and I'm posting a second log using the current stable version.
    Attached Images Attached Images
    Attached Files Attached Files

  6. #6
    Advanced Tuner
    Join Date
    Mar 2018
    Posts
    447
    I'll use the thumb drive version next.

  7. #7
    Advanced Tuner
    Join Date
    Mar 2018
    Posts
    447
    Double
    Last edited by K44; 05-01-2021 at 04:08 PM.

  8. #8
    Advanced Tuner
    Join Date
    Mar 2018
    Posts
    447
    It is a scanner issue, I re-loaded version 4.6.3 and it reads correctly.

    Thanks Mark, no telling how long it would have taken me to figure this out.

    Next question, anyone else have this issue?