Sale ends todayGet 30% off any course (excluding packages)
Ends in --- --- ---
Hey guys, I bought a RHD Mk4 ( 2jzge-non-VVTI-NA-T) that's reasonably built. Previous owner added some bigger injectors and changed a few things around before taking it back to the tuner. I live at altitude, and waited to drive it here until I had a chance to get into the maps and clean it up. Ended up just being as simple as updating injector specs.
Having gone through the EFI Fundamentals courses I'm bought into working in Lambda instead of AFR. Working through the parameters, I see that the car was tuned in AFR. When I switched the Parameter from AFR to Lambda (Basic) I noticed it had no impact on runnability, as the data display was showing the engine running and idling about where I wanted it to. But going off the Tune Display it showed the Have/Want Lambda data wildly off. ( Target Lambda of 1.40 for example) Clicking the help menu I got a better explanation and see if I want to use Target Lambda data I need to be using Lambda ( Advanced)
It finally didn't threaten to hail on us today so I brought the Supra into work and capture a log file along the way. Aside from the oddball Acc Enrichment spikes, there were a few areas in cruising that were super rich, so I went through and recorded all the areas where it occurred to investigate further.
That's when I noticed that the Target Lambda values on the graph don't seem to match target Lambda data on the Lambda #1 Table, or #2. For example at one point it shows the target lambda of 0.97 SOLIDLY in the middle of a field of 1.0Lambda with no possible interpolation.
Where is this graph value coming from?
Our apologies for the delay in response. I've been working Pikes Peak Hill Climb and Andre is on vacation.
It looks like you have a lot of fuel correction tables active so I'd look through those and see what corrections to fuel target may be active at that time. For example, coolant temperature is a common source of enrichment of fuel target at light load during engine warmup.
Thanks for the response, I've been working through several different aspects of the car over the past month. Firstly, I don't know what I was doing then, but my lambda tables are all in line now. I did discover the previous tuner didn't have EGO correction enabled until 1500 rpm which is a huge part of my issues.