when tuning do I adjust a whole RPM row at a time trying to achieve 14.7 afr or 1.0 lambda?
you have to do a bunch of datalogging, filter out data that is in power enrichment, open loop, cold engine, decel, stuff like that... then average your fueling error (whether it be wideband or narrowband trims) into a region of your ve table based on the current map and rpm.
you generally don't want to tune a whole RPM row
eehack automates this procedure in its analyzer, giving you a rough idea of what changes need to be made, then you make the changes manually by percentage.. look at the 'cruising afr' tab. if you need 5% more fuel, then select cells in that region and *1.05
this is a bit painstaking, though, and the analysis isn't very smart about dealing with data in surrounding cells, so i wrote trimalyzer
dump the logs from tunerpro or eehack as CSV and load them into trimalyzer tool and it'll automate the whole thing (kinda)
it filters your data (to discard events outside closed loop, in PE, when the engine is coled, etc) and then analyzes the fueling errors, making educated guesses where data is weak, etc, plots them in a ve correction table, you can even copy the table(s) from tunerpro or tunercat, click a button in trimalyzer, and it'll make the changes for you, you can just paste them back in.
Trimalyzer How-To ? fbodytech