beaglebone and OBD model B (ic2)
Posted: Wed May 13, 2015 1:31 am
Hi,
I have a OBD-II model B ic2 adaptor, connected to my car. I have a beaglebone black connected to ic2 ports (and GND, needed that to get it to work!) ... from the beaglebone I can do:-
# ic2detect -y -r 1 (when connect to that ic2 bus!)
which sees 2 x ic2 devices at address 0x60 and 0x68. I could then "ic2dump" the contents, etc
The documentation for the OBD adaptor says:-
"Model B connects with Arduino through I2C interface (SDA/SCL). OBD-II data and MEMS sensor data are both accessed via I2C. The OBD library has encapsulated all the necessary I2C operations for OBD-II access."
so, my questions
1. do the 2 x detected device addresses correspond to the OBD-II and MEMS sensor?
2. in a non-Arduino world (in this case, beaglebone), is it possible to get at the encapsulated OBD data on the ic2 bus?
any help / pointers would be appreciated
e
I have a OBD-II model B ic2 adaptor, connected to my car. I have a beaglebone black connected to ic2 ports (and GND, needed that to get it to work!) ... from the beaglebone I can do:-
# ic2detect -y -r 1 (when connect to that ic2 bus!)
which sees 2 x ic2 devices at address 0x60 and 0x68. I could then "ic2dump" the contents, etc
The documentation for the OBD adaptor says:-
"Model B connects with Arduino through I2C interface (SDA/SCL). OBD-II data and MEMS sensor data are both accessed via I2C. The OBD library has encapsulated all the necessary I2C operations for OBD-II access."
so, my questions
1. do the 2 x detected device addresses correspond to the OBD-II and MEMS sensor?
2. in a non-Arduino world (in this case, beaglebone), is it possible to get at the encapsulated OBD data on the ic2 bus?
any help / pointers would be appreciated
e