I'm a geek... we established that. I want to build a carputer for one of my Jeeps. Everytime I mention it to Cappa, he calls me a geek and laughs at me.

 So, when we got the press release for the DashDAQ by Drew Technologies I was shocked that Cappa agreed it would be cool to get one and do some testing. I mean, this thing is almost a carputer.

Let me back up. A carputer is what you get when you install a computer in your car (Jeep). Mounting a laptop to an arm doesn't count. You mount a hard drive somewhere, sink an LCD screen into the dash, and integrate the system into your rig. In theory, you could control the radio, nav, lights, engine diagnostics, link it to some satellite internet for working literally anywhere, and even more from it. Check out the pictures and you get the idea - not mine, I found em online somewhere.

So this DashDAQ is the size of a widescreen Garmin or Tom Tom, but plugs into the vehicle's OBD2 port and allows real-time monitoring of engine sensors, any codes that might pop up, and more. I got it with the optional navigation package so I can now do both from one unit (rather than having many units suction-cupped to the windshield). It also has the ability to accept inputs from many 3rd party devices. I'm working with AEM to hook the company's UEGO to it, and that should open up another slew of options.

I look at it like this, this one thing can get rid of a GPS, a scantool, a G-tech meter (yep can do acceleration/braking/HP too), and with the UEGO an add-on gauge in the form of an O2 sensor (but this should display more than just A/F ratios). I'm sure there is more I'm missing... but I just got the thing, cut me some slack.

Anyway, considering how I get laughed at, I'm psyched to get one step closer to a carputer, and having a blast learning a new tool, and seeing engine parameters as I drive (I've got intake air temp, engine coolant temp, map, spark advance, and more (there are 28 available to me right now, and there are many choices for how many of those 28 are displayed). Watch for the full run-down in an upcoming issue (after I've had more seat time with it of course)