i was getting some logs working on this tune and after i stopped, reflashed and started back up it was really lean. i thought maybe my fuel pressure was jacked so drove to shop and checked it but it was actually high at almost 70. so i adjusted that and drove it again and the error was better but then after stopping and looking at log started it up and lean again.
thinking might be heat soak on the air temp sensor. at one point it was reading IAT around 160 i noticed sitting there so i got on highway and the average error did come down and IAT dropped to around 80s. it was like 70 ambient
here are some logs showing the swings. is this a heatsoak issue or...?
one from monday night everything seemed normal. then first today seemed normal. second showing lean and last was trip i got on highway to get some air flowing
Haha ok... so higher rpm and throttle open loop for higher areas on the table and then closed loop and fuel trims enabled for part throttle cruise and idle areas?
No, have closed loop enabled like factory. Let the software decide when to command OL by going into PE in high load areas.
As far as types of CL there's STFT and LTFT. Some people disable LTFT. The only rationale I've heard is that LTFT's carry over into PE. To me LTFT's correcting PE enrichment, and all the rest, is a good thing.
Last edited by SiriusC1024; 05-19-2023 at 02:28 PM.
You tune with feedback from the O2 sensors which means Closed Loop. PE is open loop in the way it functions, and it depends on the accuracy of the VE table.
Use a filter in your LTFT+STFT graph to exclude anything where EQ isn't = 1.
Similarly, you can also make a filter in your wideband graph to only include data when EQ is greater than 1. Filters are awesome, but clunky to describe because of the way the PIDs change from controller to controller. My E40 filters wouldn't work on your Gen 3. You just have to build them yourself using the 'New Variable' button, then adding <, >, =, avg,...
You can also filter to exclude idle (either by when idle routines are active if there's a flag for that, or by only including stuff over a certain minimum throttle pedal or TPS), and also transients by not including stuff a certain time before and after a throttle change greater than a certain amount... and removing anything when EVAP purge is active, and and and...
If it's a channel that can be logged, you can make a filter against it.
Make a copy of your current graph(s), then put your experimental filters into the new copy. That way you can switch easily between the graph with no filters and the ones with them.. See which filters do what.
That tune file is the opposite of 'MAF only'. If that's the one used during MAF tuning you'd be taking VE error and applying to the MAF table, and that wouldn't turn out so great.
Reply With Quote
