| Author | Message | ||
     Xoptimizedrsx |
Ecmspy now has a version of the ADX file to link the bikes as well. He didnt put in the history tables du to they are not exactly a Auto tune. the history tables are for analysis of the data run. not to be confused from True Auto tune. its reading the data based from the VEcurr1 and veCurr2 (actual injected fuel per injector) compared to the actual fuel table you will see a slight difference. the data logs can be saved as a cvs file and ran in the mlv program. I will post the little program made to convert the saved txt file from tunerpro to a msq file for MLV to get your ecm's data. It's always something when it comes to the ecms but as soon as one thing is resolved another will surface... As I get data and learn data I will always post the findings be it I did the findings or the group did them working on it. Its all in one pot to share for the good of it. | ||
| Xoptimizedrsx |
Vehicles that run in closed loop usually output a correction value (as I know Buells do). That correction value tells you what correction the ECU is making to get the mixture to stoich. For closed loop tuning, you typically want to get that correction as close to "no correction" as possible, so you can use the correction value to determine what changes to make to the fuel table. This is your goal. For vehicles that have wide-band O2s, the vehicle usually outputs the AFR in the stream. You can also chart this to use this for tuning. If a cell in the history table has 15.7 AFR and you want to be in at 14.7 (stoich for gasoline), then you know what correction to apply (roughly 14.7/15.7, or 0.936). So, for such a history table, you'd use RPM on one axis, load on another, and Actual AFR / Target AFR on the Z (cell) axis. This is how fuel tuning is typically done. |
