Open loop tune coming to a close!
Nearing completion of my open loop street tune. Still logging and adjusting, but I'm about done now! My goal is to get all my cells to +/- 9% or less. I'm finally close! There's still some WTF areas that seem to be a right pain to get rid of, like the 70% rich cell.. sigh.. Anywho.. I'd say about 2 more log/adjust sessions should put me where I'm attempting. Then it's closed loop time.
Last edited by Txdragon; Apr 12, 2017 at 03:49 PM. Reason: fixed picture
Honda-Tech Member
Joined: Feb 2017
Posts: 66
Likes: 0
From: Democratic People's Republic of Khalifornia
If you know the likelihood of you being in those areas of the map on street are going to be slim to none, you might be better off just shaving the number to what you suppose the value should be and letting the closed loop handle it from there. Hitting those areas of the map on street isn't exactly the most feasible thing to do.
If you know the likelihood of you being in those areas of the map on street are going to be slim to none, you might be better off just shaving the number to what you suppose the value should be and letting the closed loop handle it from there. Hitting those areas of the map on street isn't exactly the most feasible thing to do.
+/-9% is a lot of error! The terribly simple lambda control is going to have a tough time with that and you're going to to be running around with a ton of fuel trim. Try to get it more like <3% total error with nothing negative (so, 0 to 3% rich). Don't worry about cells you can't hit or cells that have huge outlier numbers. Use your best judgement to extrapolate those cells.
I rarely touch the first column from base (you should be in fuel cut there) and I make my last column the same as my last achievable column. These two end columns are there to keep you "on the curve" and keep the ecu from extrapolating. Look at the 2d view of the map and note any points that increase/decrease a lot between rpm breakpoints. Add a column between those two breakpoints for more resolution interpolate the new column and rerun as needed.
Make sure you don't have any rows crossing and smooth as needed. Check the 3D view and smooth some more. Rinse and repeat and THEN turn on the lambda control (closed loop)
I rarely touch the first column from base (you should be in fuel cut there) and I make my last column the same as my last achievable column. These two end columns are there to keep you "on the curve" and keep the ecu from extrapolating. Look at the 2d view of the map and note any points that increase/decrease a lot between rpm breakpoints. Add a column between those two breakpoints for more resolution interpolate the new column and rerun as needed.
Make sure you don't have any rows crossing and smooth as needed. Check the 3D view and smooth some more. Rinse and repeat and THEN turn on the lambda control (closed loop)
Trending Topics
+/-9% is a lot of error! The terribly simple lambda control is going to have a tough time with that and you're going to to be running around with a ton of fuel trim. Try to get it more like <3% total error with nothing negative (so, 0 to 3% rich). Don't worry about cells you can't hit or cells that have huge outlier numbers. Use your best judgement to extrapolate those cells.
I rarely touch the first column from base (you should be in fuel cut there) and I make my last column the same as my last achievable column. These two end columns are there to keep you "on the curve" and keep the ecu from extrapolating. Look at the 2d view of the map and note any points that increase/decrease a lot between rpm breakpoints. Add a column between those two breakpoints for more resolution interpolate the new column and rerun as needed.
Make sure you don't have any rows crossing and smooth as needed. Check the 3D view and smooth some more. Rinse and repeat and THEN turn on the lambda control (closed loop)
I rarely touch the first column from base (you should be in fuel cut there) and I make my last column the same as my last achievable column. These two end columns are there to keep you "on the curve" and keep the ecu from extrapolating. Look at the 2d view of the map and note any points that increase/decrease a lot between rpm breakpoints. Add a column between those two breakpoints for more resolution interpolate the new column and rerun as needed.
Make sure you don't have any rows crossing and smooth as needed. Check the 3D view and smooth some more. Rinse and repeat and THEN turn on the lambda control (closed loop)
Honda-Tech Member
Joined: Feb 2017
Posts: 66
Likes: 0
From: Democratic People's Republic of Khalifornia
I'm not familiar with neptune, but I'm going to go on a limb and presume that there's some way to datalog the car in closed loop and view the percentage corrections the ECU is making at those areas in the table. Just reapply that percentage to the raw values in the table, and you should be able to dial in without forcing yourself in open loop. This should be done on a dyno because if you're zipping through the cells and just trying to tap them as you pass them (on street), tip in fuel compensation may be present in the readings and throw off your entire calibration.
Neptune shows you the percentage you are off. That is what his pic is showing. Doing it the closed loop way would be significantly more painful.
I agree, doing it on a load bearing dyno would be far and away the most efficient way to do it, and is also the only real way to tune part throttle ignition. I can almost guarantee that those 29 & 70% rich cells are tip-in related errors based on their locations.
Also, start tuning in lambda instead of AFR and your life will be easier. Your error from target is always in %!
I agree, doing it on a load bearing dyno would be far and away the most efficient way to do it, and is also the only real way to tune part throttle ignition. I can almost guarantee that those 29 & 70% rich cells are tip-in related errors based on their locations.
Also, start tuning in lambda instead of AFR and your life will be easier. Your error from target is always in %!
I'm not familiar with neptune, but I'm going to go on a limb and presume that there's some way to datalog the car in closed loop and view the percentage corrections the ECU is making at those areas in the table. Just reapply that percentage to the raw values in the table, and you should be able to dial in without forcing yourself in open loop. This should be done on a dyno because if you're zipping through the cells and just trying to tap them as you pass them (on street), tip in fuel compensation may be present in the readings and throw off your entire calibration.
Neptune shows you the percentage you are off. That is what his pic is showing. Doing it the closed loop way would be significantly more painful.
I agree, doing it on a load bearing dyno would be far and away the most efficient way to do it, and is also the only real way to tune part throttle ignition. I can almost guarantee that those 29 & 70% rich cells are tip-in related errors based on their locations.
Also, start tuning in lambda instead of AFR and your life will be easier. Your error from target is always in %!
I agree, doing it on a load bearing dyno would be far and away the most efficient way to do it, and is also the only real way to tune part throttle ignition. I can almost guarantee that those 29 & 70% rich cells are tip-in related errors based on their locations.
Also, start tuning in lambda instead of AFR and your life will be easier. Your error from target is always in %!
A couple runs after installing the new clutch has me near dialed in this time. I am now with a small number of lean cells and rich cells are average 4%. Tons between 1 and 3, several 4 and 5.
I have been playing around with timing as well. From my understanding, I should be shooting for 29 deg at WOT with 13:1 a/f and I am close at 28.5 lol. Feels great and new clutch is certainly putting it all to the wheels now, no more slipping!
I have been playing around with timing as well. From my understanding, I should be shooting for 29 deg at WOT with 13:1 a/f and I am close at 28.5 lol. Feels great and new clutch is certainly putting it all to the wheels now, no more slipping!
Thread
Thread Starter
Forum
Replies
Last Post
CplNet
Engine Management and Tuning
6
Jul 3, 2013 06:29 PM
aasarsak
Engine Management and Tuning
4
Mar 22, 2009 10:17 PM







