Exactly like CarMan, except I have mine in a raw "dump data from powerup" mode - mine is from obdpros.com and you might have to ask for this version, and get a serial to BT adapter.

(I just checked the http://www.obdpros.com page and the integrated bluetooth version is out. I just sent an email with the inquiry to see about getting one with the right stuff)

One caution - if you save the data from google earth, it compresses things so the logging data will be gone (but the file will be much smaller). And perl should do a good job with extraction. There is a newfix1.c or something in the source tree which is my C post-processor.

My post processor takes the slightly cooked data (look in fixsub.c) and can produce rpm, gear, fuel info etc. from the j1850 stream from my harley, and I already have a preliminary python instrument cluster.



RPM gear - RETMA colors like resistors, brown=1st, red=2nd, etc.
Black means the clutch is in, gray means the ECM hasn't figured out the gear.



CarMan apparently uses standard OBD-II interrogations (it asks, the ECM responds).

I'd have to stretch it a bit to do the OBD-II send/receive, but it wouldn't be too hard.

And I have thought about Kismet - I could just go into monitor mode and look for (and record) beacons, but iwlist is probably as good or better if you don't need the actual packet contents and it doesn't require a special mode.