| Author | Message | ||
     Uly_man |
I think I have now got to grips with the basic workings of Tunepro and a VERY basic understanding of how the FI system works in relation to the bike. That is logging runs, what the files do and the ADX definition file. I managed to edit (even though there is no help in the "help" file) the ADX definition file to set up the "dash and monitor" views and they run fine. The "history tables" are what I am not sure about? Ok so I have edited the ADX definition file "history tables" to give me a Front and Rear 3D fuel map that match the (first/main) ECM 3D Fuel map tables. RPM (X-Axis) on the lower left, LOAD (Y-Axis) on the lower right and VeCurr (Output-Z) vertical of the 3D graph/table "history" map. I can now run a log and the "logging point" jumps around (cell/box in yellow) on the history table recording the data to the table. This data/numbers closely match those in the ECMs base fuel map. They are 5 to 10 points out and are worse as the LOAD and RPM go up. This is only one log though and it does not cover the whole range of the map. My question is this. Have I "set it up" right and is the data I am getting what it should be? In other words is the data that is being logged in the cells of the "history" file those that the ECM has calculated to try and match those in the base fuel map. | ||
| Spacecapsule1 |
if you changed your adx file (load and rpm) to match the map on your ecm, then yes you've set it up right. the data you see logged are the ecm calculated values with various other corrections applied... you need to tune each rpm range in your map to have the same afv. THEN you can work on adjusting the entire map to target approx. 100 afv. | ||
| Uly_man |
"if you changed your adx file (load and rpm) to match the map on your ecm, then yes you've set it up right." Yes cool. "the data you see logged are the ecm calculated values with various other corrections applied." Yes thats ok. "you need to tune each rpm range in your map to have the same afv. THEN you can work on adjusting the entire map to target approx. 100 afv." I am only doing this as an experiment but my understanding is that the numbers in the log are the EGO corrections over the base map and the base map is likely to be 14.7:1 over the whole map for emissions control. From my understanding the EGO correction is the key to tuning as it is trying to adjust the fuel to match the fixed base fuel map. The AFV is there to compensate for other things and will NEVER be 100% all the time due to varied things like temp etc. Something like a running range of 90 to 110 seems about right over a run. So, it seems, what you do is build a new fuel map for the mid/upper power band because the OEM on does not have that and then tune from that one using the EGO correction from the logged run to suit your setup. I did not get your logged run Spacecap1. I would like to see it. Take care Sir. | ||
| Spacecapsule1 |
true, you wont get 100. but you'll get close. also, the idea behind tuning each rpm range first is to limit the amount of correcting the ecm has to do between the rpm ranges in the fuel map. this should help smooth things out a bit. I believe the ego correction is trying to achieve 14.7, not trying to match the fuel map? my bike is busted and down for good until I can come up with the cash to fix the engine. some type of mechanical failure. I'll see if i have an old logged run for ya.... | ||
| Uly_man |
Sorry to hear about the bike. A run would be handy to look over. Thanks. |
