Ok .... CTRL+C warmed up? ... check .... cracked knuckles twice? .... check check ..... deep breath ..... aaaaaaand go ....
Before I post ANYTHING ... please let me be clear on one point ... I'm not sure how much of the operation of these ECM's you already understand so please don't take anything I explain that you already know as an offense to your intelligence ... I'm just starting from the beginning ...
A quick explanation on the O2 sensor, the AFV and the EGO correction's influence on the fuel maps before we continue ...
The O2 sensors first ... When most people think of O2 sensors they think of the wideband O2 sensors in a vehicle which put out a (more or less) steady voltage compared to our narrowband (otherwise known as lambda sensors) in our bikes ... which function basically as an on/off switch to the ECM providing a 1 or a 0 input for it to record and observe ... basically what the ECM looks for from it's O2 sensor when it's in closed loop and actually taking it into account is how many times it crosses the midpoint value it has stored over a given period of runtime ... in a perfect world it should be seeing 1, 0, 1, 0, 1, 0, 1, 0 or something of that effect ... we will see this as the EGO voltage fluctuating rapidly from a "high" voltage to a "low voltage (we're only dealing with 1 volt here) ... the more times it crosses over in a given time, the better ... now if you start running really rich or really lean the O2 sensor will start running at a consistent high or low voltage and putting out more 0's or 1's in a given time ... instead of 1, 0, 1, 0, 1, 0, 1, 0 it'll see 1, 1, 1, 1, 1, 0, 1, 0, 1, 1 ... this will mean you're running very rich and the computer will start taking fuel out to try and get back to a steady 1, 0, 1, 0, 1, 0 flow ... But remember, narrowband sensors are nowhere near as accurate as widebands are ... basically the ECM is putting for a "slightly more than educated guess" at what it needs to do to correct the fueling ... a lot of people make the mistake of changing parts or throwing in maps and thinking the O2 will make up the difference ... well only to a certain extent ... In a perfect world, the ECM's entire fuel map should be tuned for roughly stoichiometric running ... the O2 sensor is built in to compensate for day to day changes ... not correct wild fueling errors ...
Which brings you to the EGO correction ... this is a percentage that your ECM gets from observing the O2 sensor's output when you're operating in a closed loop area of the fuel map and seeing if your engine is running consistently lean or rich... this percentage is applied directly to the fuel cell your bike is currently running in ... if it's a high percentage it's adding fuel, if it's low vice/versa ...
Now ... The AFV .... Just like I explained above what EGO correction does to a certain fuel cell, the AFV does it to the entire map ... if your AFV is 110, it's applying 110% of the fuel to any given fuel cell in the fuel map no matter where your bike is operating at in the fuel map ... your bike gets the AFV by taking an average of how lean or rich the bike is running in closed loop from the EGO correction ... if you go out and run a log with your bike, you'll consistently see the AFV mimic the EGO correction percentage ... As explained before this is to try and get the fuel maps to run as perfect as possible so there's as little correction being applied from the O2 sensor as possible ...
Now ... if you slap a map in your bike that's not tuned correctly for your modifications you'll have lean conditions and rich conditions in different portions of the map .... say your idle is good, but your cruising RPM's in the closed loop area are really lean ... when you first start up the bike after you put the maps in, it'll run great for a bit until you take it out on the road and cruise around in an area of the fuel map that's lean ... when your bike sees it's starting to run lean from the O2 sensor, it'll up the AFV to match what the O2 sensor is seeing (which applies it to the entire map as a whole) ... this will make that one particular area run great, but the rest of the map will run like shit ... when you stop at a red light and let the bike drop to idle the AFV will still be in effect to the fuel cell values in the idle portion of the map, but since it's adding fuel from seeing the previously lean readings from the O2 sensor your idle will be running crazy rich ... the O2 sensor will be trying to compensate and apply the EGO correction to the fueling, but it's also applying this to the AFV that the ECM has in place for the whole map ... so your fueling will just get worse ... narrowband O2 sensors aren't terribly accurate, they just kinda shoot for an average ... so the further the error it's reading the worse of a "guess" from the ECM it will be ...
For the first picture ...
Your engine is idling and at operating temperature so the EGO correction should be reading 100% in a perfect world during this sort of operation (or as close to it as possible in real world operation because of outside factors ... temp, humidity, altitude, etc.) ... in that picture I see it at 134% ... this is telling me your idle cell fuel values are reading terribly lean on the O2 sensor and it's taking the cell value you're idling in and adding 34% on top of what's already there ... also your AFV is showing 128 which tells me the cruising RPM's (about 2.5k-4kish) are also lean ... the AFV is a percentage that the ECM applies to the entire map as a whole ... so it's taking your entire map and adding an additional 28% on top of everything that's already there ...
----------------------------------------- To be continued when I get home from work .. ------------------------------------
