I like it, I've never used any of the really expensive stuff but it seems ok. With Honda module I can talk to honda sensors etc way better than your generic code reader. Like ABS sensors etc. Hard part is knowing what I'm looking at and what it means. Like accelerator position sensor A volts, wtf is that? Would be nice if I had a honda manual describing what all this means, and what are normal values. Would also be nice if a range was provided with the reading like some of the better tools provide. But better than generic data like I said. And yes I'm using a laptop with a usb cable/dongle that connects to odbd2 port.
I don't think AF sensors are more difficult, just different. A standard 02 sensor has voltage between 0 and 1, call .5 normal. If voltage approaches zero you have a lean condition. Approaching 1 is a rich condition.
AF sensor (wideband) can measure a bigger variance of lean and rich vs standard narrow band o2 sensor. I forget what the voltage means but there are values. But you also measure current in mA, and negative means rich, positive means lean. Fuel trim is what the computer is doing, and is measured kind of like current, but with a base value of 1 = stroichiometric. Anything above 1 is a positive fuel trim, which means the AF sensor is reading too much oxygen (a lean condition), so the computer is adding fuel. If the fuel trim is below 1, that means the AF sensor is reading a rich condition, too much fuel, so you have a negative fuel trim which means the computer is removing fuel. Then there's the lambda value, 1 being stoichiometric, above 1 lean, below 1 rich. Still learning about lambda but I think it's important.
Truth be told I'm still learning. Next tool is going to be a picoscope so I can start getting data that way. But whatever you use, if you can graph your o2 or af sensors and see how they respond to testing I think helps tremendously.
www.piloteers.org
