-
Notifications
You must be signed in to change notification settings - Fork 1
Architecture
EricFitchett edited this page Aug 15, 2011
·
1 revision
car-data-logger is made up of a suite of applications that accomplish smaller tasks.
These applications include:
- capture Collects data from multiple sources and multiplexes it into a single file
- analyze Reads the data collected and helps you make sense of it, visually
- arduino Code that runs on the Arduino microcontroller, reading from the 3-axis accelerometer (and possibly other sensors) and sending the data to the computer
- reverse-engineer Helps you figure out what each (undocumented) message coming from your car's ECU means
- elm A library to communicate with the Elm 327 chip in the ElmScan 5 Compact (and compatible)
- vin-decode Attempts to decode your car's unique identifier, to determine if it's the same or close to a car we already have reverse engineered ECU messages for
My personal priority on these applications is as follows:
- capture (you need data before you can do anything)
- arduino (part of capture, and very simple)
- elm (needed for capture)
- analyze
- reverse-engineer (I've already found all the data I care about on my car)
- vin-decode (I think this is one of the least necessary parts of this project)
If you want to contribute in any area, let me know. I can help get you started, or give you a better idea what I was hoping for.