You certainly would not have believe it had you not done it on your own thats for sure as you all have been fighting it for years.
I'm assuming that this is directed at me, since Joe is a relative new comer to this conversation, so let me respond by asking in what way have I been fighting this?
You seem to have a rather short memory. When I made the jump into flash tuning a few years ago, did I not go through the process as outlined by TTS and its representatives, all the while documenting publically what I was doing, with a final outcome that validated that vtuning per the outlined process worked? In the validation, did I not also publically document that when the Vtune program on an afr bike indicates that enough data has been collected on an extendable cell that the results are fairly linear to what was recorded on an external afr meter? The lambda cals are the only one's that I do not have confidence in the extension method, and I have not seen any circumstance to get me to change my opinion on that.
I am not opposed to using broad bands, but I am not opposed to using narrow bands either. In the several attempts that Bob had made previous to get this thread going, I never publically stated that it wouldn't work. I honestly didn’t know, in truth I was actually biased towards the notion that it would work since Bob and Jason both had stated that WOT tuning using narrow bands was not a new concept. If I mind correctly, it was you telling Andy Whittle that narrow bands can't be used in this fashion several years ago, not me.
The only issue that I have on using the narrow bands to tune with is an operator at this time is not dealing with known values. If you go tell someone to target 1720 mV on a lambda bike, they will look at you like you have two heads. There is nothing to tell them how many ve values that you must increase the cell to if the current reading is 1610 mV. The operator can use afr since the calibration has a table with desired afr, and then the math between desired.