Anyone fooled with the hondata autotune functionality?
Dustin...I know that G3-TEG used it recently and loved the feature...it's something that I look forward to using once I have a stage 4 system and a WBO2....1/2 of the way there.
Austin
Austin
Trending Topics
Good question!. I have Romeditor 2.5 and I don't see it anywhere and it's not in the manual...
Dustin plz share...
Dustin plz share...
Ahh, my fears confirmed 
You can do it manually with the lambda thing, but that's not fun at all
Doug, you around?

You can do it manually with the lambda thing, but that's not fun at all

Doug, you around?
The Autotune function is not implemented. There are too many variables like acceleration enrichment, and injector overrun cutoff which change the required air fuel ratio for your given load and rpm value. We have found that rather than tuning on a cell by cell basis it is best to build up a map ( a number of rpm and load points) before making changes to the fuel values. I will post an article on this next week in this forum.
Doug
Doug
There isn't an "autotune" per se... however the Hondata coupled with a wideband O2 and the Datalogging capability of the Hondata system is a powerful tuning tool.
You can set your desired TARGET LAMBDA either in Lambda or A/F values in the TARGET LAMBDA pull down menu. Once that is done, make a power run and log the wideband O2 readings either in the RomEditor or the Hondalogger.
Open up the saved datalog in the RomEditor via the pull down menu. Then scroll forward in time to the portion of the power run in which you are concerned about. (most likely the point where you started the WOT run to redline)
You will see in the PERCENTAGE LAMBDA table how far off your actual A/F readings are as compared to your target Lambda values that you had set before hand. This difference in A/F is on a CELL-BY-CELL basis thus making the tuning and changes extremely easy.
Simply highlight the cell(s) that you wish to modify. For example, at 6500rpms I set my target Lambda at 13.2, however when i made my power run, my actual A/F was 12.5. So you will see a difference number displayed in that cell corrosponding to this difference - 0.7.
Highlight the the cell at 6500 row and corrosponding column and goto the FUEL table. Hit the "U" button seven times and you are done. Continue doing this until all cells have been updated.
Make another power run. You should see that your A/F is now 99% nailed to your target Lambda.
PS: sometimes it is more convenient to highlight a portion of the table that requires changing since changing a single cell affects its' neighboring cells as well because under load the ECU is using a group of 4 cells and averaging their values rather than using the value of a single cell at each load point.
HTH
You can set your desired TARGET LAMBDA either in Lambda or A/F values in the TARGET LAMBDA pull down menu. Once that is done, make a power run and log the wideband O2 readings either in the RomEditor or the Hondalogger.
Open up the saved datalog in the RomEditor via the pull down menu. Then scroll forward in time to the portion of the power run in which you are concerned about. (most likely the point where you started the WOT run to redline)
You will see in the PERCENTAGE LAMBDA table how far off your actual A/F readings are as compared to your target Lambda values that you had set before hand. This difference in A/F is on a CELL-BY-CELL basis thus making the tuning and changes extremely easy.
Simply highlight the cell(s) that you wish to modify. For example, at 6500rpms I set my target Lambda at 13.2, however when i made my power run, my actual A/F was 12.5. So you will see a difference number displayed in that cell corrosponding to this difference - 0.7.
Highlight the the cell at 6500 row and corrosponding column and goto the FUEL table. Hit the "U" button seven times and you are done. Continue doing this until all cells have been updated.
Make another power run. You should see that your A/F is now 99% nailed to your target Lambda.
PS: sometimes it is more convenient to highlight a portion of the table that requires changing since changing a single cell affects its' neighboring cells as well because under load the ECU is using a group of 4 cells and averaging their values rather than using the value of a single cell at each load point.
HTH
Thread
Thread Starter
Forum
Replies
Last Post
turbotime
Forced Induction
2
Oct 10, 2005 11:56 AM
CovertFI
Forced Induction
10
Jul 10, 2002 02:29 PM





