Archive:Quantify My Ride: Difference between revisions
(project info box) |
No edit summary |
||
| Line 17: | Line 17: | ||
OBD stands for On-Board diagnostics [http://en.wikipedia.org/wiki/On-board_diagnostics]. It should allow us to gather a lot of information via a standarized format, called OBD-2, or EOBD (the European equivalent). There are OBD-2 connectors in most modern cars, and adapters for bluetooth or USB readily available. | OBD stands for On-Board diagnostics [http://en.wikipedia.org/wiki/On-board_diagnostics]. It should allow us to gather a lot of information via a standarized format, called OBD-2, or EOBD (the European equivalent). There are OBD-2 connectors in most modern cars, and adapters for bluetooth or USB readily available. | ||
I have | I have a OBD-2 bluetooth adapter, and a OBD-2 USB cable now. Both work, but I use the USB cable because it's easier to connect. | ||
=== GPS === | === GPS === | ||
| Line 26: | Line 26: | ||
== Hardware == | == Hardware == | ||
=== Planning === | |||
* Raspberry Pi | * Raspberry Pi | ||
* OBD-2 adapter (bluetooth? USB?) | * OBD-2 adapter (bluetooth? USB?) | ||
| Line 34: | Line 35: | ||
* WebCam as Dashcam ? | * WebCam as Dashcam ? | ||
* Powersupply ??? | * Powersupply ??? | ||
=== Rev. 1 === | |||
* Old netbook | |||
* Car power supply | |||
* OBD-2 USB cable | |||
== Software == | |||
I forked [https://github.com/markembling/pyobdlib pyobdlib by markembling], fixed some stuff, and then wrote a logger around it (not yet on github) that spits out a CSV file with some of the more interesting values (for my car). | |||
== Logbook == | |||
;02.09.2013 | |||
:First real test when driving from Munich to Stuttgart. Gathered some data[http://data.tiefpunkt.com]. Used Rev.1 Hardware and simple csv logger. Logger broke down during a short stop when the motor was turned of. Was an issue with pyobdlib. Should be fixable. GPS should be one of the next priorities. | |||
== Links == | == Links == | ||
Revision as of 22:03, 2 September 2013
| Quantified Car Release status: experimental [box doku] | |
|---|---|
| Description | Data dathering (not-so) black box for you car. |
| Author(s) | tiefpunkt |
Quanitfy your car. There's a lot of data being collected automatically in modern cars already, and the plan is to gather that data, and make it useful (maybe).
Data Sources
OBD
OBD stands for On-Board diagnostics [1]. It should allow us to gather a lot of information via a standarized format, called OBD-2, or EOBD (the European equivalent). There are OBD-2 connectors in most modern cars, and adapters for bluetooth or USB readily available.
I have a OBD-2 bluetooth adapter, and a OBD-2 USB cable now. Both work, but I use the USB cable because it's easier to connect.
GPS
With a GPS receiver, we can link the data we gather to a specific location.
Camera
Add a camera?
Hardware
Planning
- Raspberry Pi
- OBD-2 adapter (bluetooth? USB?)
- Wifi -> upload data, via tethering or when at home near to a known access point
- GPS adapter
- Cheap GPS from miniPCI cards [2]
- blink(1) or RZLblink as status LED
- WebCam as Dashcam ?
- Powersupply ???
Rev. 1
- Old netbook
- Car power supply
- OBD-2 USB cable
Software
I forked pyobdlib by markembling, fixed some stuff, and then wrote a logger around it (not yet on github) that spits out a CSV file with some of the more interesting values (for my car).
Logbook
- 02.09.2013
- First real test when driving from Munich to Stuttgart. Gathered some data[3]. Used Rev.1 Hardware and simple csv logger. Logger broke down during a short stop when the motor was turned of. Was an issue with pyobdlib. Should be fixable. GPS should be one of the next priorities.
Links
- How to interface with your car’s ECU through OBD2 and Python
- OBD2-Scantool (Python project for OBD on GitHub)
- Raspberry Pi Car PC Project Part 1Part 2
- Raspberry Pi Car Computer
- Power Supply
- Raspberry PI Power Shield
- Sleepy Pi
- MausBerry Car Power Supply Website Kickstarter
