hey i was just thinkin bout datalogging, and then i was like hmmmm instead of reading a vac/boost gauge and assuming it is dead on with the map sensor y not use a volt meter on the map sensor. so then in ur car you have 2 backlit lcd displays. one for o2 sensor, the other for map sensor. then i could datalog with a video camera. would i be wasting my time or would this work pretty nicely. i am planning to run a vac/boost and a/f gauge for looks to just to be a lil ricey. =)

 

In all honesty I give you credit for thinking this out and at least asking other peoples opinions about it But, I think it wouldn't be worth your time and effort. Dattaloging is something way more complex that just a vid. camera monitoring the Boost guage etc. Dattalogging will give you extremely accurate monitoring capability's of Lambata readings, your fuel maps and curves etc. Ignition I beleive, and I'm sure theres quite a bit more in depth information that I cannot describe.
But anyway, dataloging is the way to go to actually fine tune your engine. You'll be able to collect all the information of what your engine is doing, and correct from there.

 

I'll have to agree with TM on this one..

Great thinking, though. It's nice to see some innovation on this board!

I'll sort of elaborate on the fundamental flaws in the idea though. First off, single wire O2 voltage is not linear, and the voltage is only "effective" between ~14.2:1 (.92v) to ~15.2:1 (.05v). Not enough range (hence then "narrow band") to effectively tune a vehicle.

Second, there is a bit of "controversy" behind datalogging in general, on which method is actually "better" to tune by. The two opposing sides are, "external" (datalogign device tapped directly into a car's sensors) and internal (getting datalogged information directly from the ECU).

The main reason for this is, accuracy, or lack there of. Now, tapping directly into your vehicles sensors (or gather from external sensors) could be very accurate, but does the ECU lose something during calculation of the values? Yes, sometimes. Personally, I support the gathering of post processed data from the ECU. This way, I know exactly what the ECU is reading. Now, this sounds perfect? Why doesn't everyone use this? Because ever so slightly behind. Because it's already been processed, it's just a microsecond behind the actual values.

Oh well.. my point is, with the video, you're A) gathering external information, and B) relying on instruments that may lag behind also (voltmeter, tach..). Just too many variables for it to be a viable source of tuning.

 

what are other options if i cant afford a "real" datalogging method? how does the te2 datalogger work?

 

Hehe, that would be EF9's department. Us OBD1 guy's are still trying to incorperate datalogging into out programing :P

 

 

ahahaha Nice one bamboo, how much do you charge to rent?

 

"we're counting cards"
-my datalogger