| Author | Message | ||
     Hunger |
Now I've finally tuned my maps after muffler swap. I did it properly, with data logging, using MegalogViewer to get stochiometric. And I'm telling you it works, the bike runs great. Yet, ECM still wants it leaner. The AFV keeps dropping to ~85%. Somebody tell me why is that because with such AFV it shows all the symptoms of lean running while on 100% the feeling is perfect. No hestitation, no choking, and power is there when you need it. You just ride and know that's the correct tune. No such problems when on stock muffler. An advice would be appreciated  | ||
| Steveford |
I do not know but I do know that the 100% is simply a starting point and then it will change depending upon the altitude. | ||
| Readyxb |
Can you upload a datalog that demonstrates the AFV changing from 100% to ~85%? I'd like to review it. | ||
| Teeps |
Stock or Race Only ECM? | ||
| Hunger |
Stock ECM. I've re-tuned today and now it drops as far as ~90% so it's kind of better. I've also logged a steady run on a highway, will try to use that to 'polish' the map. Readyxb, I will get that log soon. Probably tomorrow - it's 11pm here atm. BTW. What should be used as EGO correction column in Megalog? 'Gego' or 'EGO Corr.'? I'm logging with ECMDroid. | ||
| Phelan |
The ECM is targeting 14.5-1 AFR during cruising RPM, and thus changing the AFV accordingly to accommodate. When the bike is in open loop, it will take a sample over a period of time and adjust the AFV to compensate. The factors that change this are elevation, humidity, and temperature. All three of these will change daily, so it makes sense that your AFV will change daily. Almost never will it stay and run at 100% all the time, nor would you want it to, as the weather changes by the hour, sometimes even quicker. (Message edited by phelan on May 07, 2016) | ||
| Sagehawk |
What age and mileage are on the 02 sensor? I'm starting to suspect my o2 sensor is changing with 26000 miles on it. My afv has drifted to 94. or so after being an average of 101 to 103 forever. if you are changing maps and datalogging with a weak sensor you wont get good results. Phelan: what are you doing for your front cylinder? are you datalogging it as well with its own sensor? or are you doing a percentage points richer that rear cylinder is shown to be at caompared to 14.7%? Have got a few other questions of the group as this thread progresses. | ||
| Readyxb |
Open Loop: - Gego=AFV - EGO Corr.=Last Value in Closed Loop Closed Loop: - Gego=EGO Corr. - AFV=Calculated in CLL Knowing the above, which would you use for MLV? Tuning is opening a can of worms! | ||
| Hunger |
Readyxb, here's the log: https://drive.google.com/open?id=0B1WuX8MwMI1ceXJa cXg5cnI0ajg If you can have a look I will be really grateful. Knowing the above, which would you use for MLV? Tuning is opening a can of worms! Argh. Honestly, I'm still mixing those (EGO/Gego close/open loop). But what you're trying to say is there's no simple answer? What age and mileage are on the 02 sensor? I'm starting to suspect my o2 sensor is changing with 26000 miles on it. My afv has drifted to 94. or so after being an average of 101 to 103 forever. if you are changing maps and datalogging with a weak sensor you wont get good results. Maybe, but it's the very same sensor based on which tuning was done that on the same day made AFV drifting. If the sensor is a little off it should be off the same way in both situations... Unless it's broken in a different way, I don't know how the O2 sensors work. As for age, I also don't know. Probably as old as the bike. Phelan: what are you doing for your front cylinder? are you datalogging it as well with its own sensor? or are you doing a percentage points richer that rear cylinder is shown to be at caompared to 14.7%? Have got a few other questions of the group as this thread progresses. I'm interested in that too. For now just made the front the same as rear plus 3. (Message edited by Hunger on May 08, 2016) | ||
| Sagehawk |
Hunger: what was the ambient temperature the day you took this log? It doesn't look like you got hot enough to come off of cold start enrichment. original settings are 180c I believe for everything to go closed loop. after bike sits all day and is ambient, I'll take my cheap laser thermometer and shoot the gas tank. Your iat and clt ought to be within a few degrees of each other and that ambient fuel tank. That's how I check my bike every so often. not really scientific but youll have an idea of those two temps as compared to the real world. IAT and clt are within 6 degrees of each other usually. comparison over time is my thoughts on it, just like shooting the oiling system for temp disparities. Let us know how you are doing. | ||
| Firemanjim |
You must have mucked about in the Learned Fuel area and added too much fuel there. It then adjusts entire map to see the 14.5 it wants in the Learn area. | ||
| Hunger |
Sagehawk - Nice catch. Indeed it was cold outside. About 10C (50F). It was late in the evening and I was riding fast on a highway that's why engine coundn't reach 180C. But that's OK. 160C is within normal operating temp. which AFAIK is 150-180C. I believe learning triggers at 150C but I might be wrong. In any case I will compare the sensor readings with pyrometer but I remember doing that not long ago an it was OK. Also I don't think IAT should be similar to CLT. The intake air comes from the outside so it should read more than ambient but not even close to CLT. | ||
| Readyxb |
Just that tuning requires education, planning, and equipment (ie, front/rear O2 sensors)! Thanks for the data. Sensors look healthy. Idle base fuel map is spot on. Cruising at 65-75 mph, however, the base map is too rich, so AFV gets adjusted down. For example, at a load of 40-50 @ 2800-3200 RPM, base map is ~10% too rich. I have to trust the data, so I am wondering if the problem might lie with the .msq/tune file used for VE analyze. Did you start with a stock fuel map and use an msq file that matched? How was the tune file created? |
