Thread: Voyager: Bluetooth OBDii for the Droid

Originally Posted by justchat_1

No need to re-invent the wheel: OpenOBD (yup another subproject)

And like bugbyte said these features will be available from the OSDash project.

Thanks JC! Although I hadn't proposed a diagnostic codes DB like what they are working on in that project I think its database could be nicely leveraged. For example if Voyager detects trouble codes present in the ECU, it could interrogate a web server and obtain detailed information, including web URLs for the user to learn more about each code.

Thats actually one of my projects....but we took it a step further -> translated each manufacturer specific DTC to a universal DTC and then use the combinations of universal DTCs to determine likely causes. So instead of just EVAP system leak detected we provide trouble shooting steps like 1) Ensure the gas cap is securely tightened....etc.

Edit:
nice impala btw

Bravo! I like it!
I saw some chatter on the thread about storing manufacturer specific codes in the database. It seemed to die down quickly but my interest is piqued.

I'm also sold on the OSDash ideas. To add an internet-aware adapter to the Voyager code base wouldn't take much work, in theory.

My droid is drooling. Good job, I was actually thinking about this last week.

Originally Posted by Bugbyte

If someone writes a car maintenance and tracking service, again, you could use your app to supply OBD information to that service or use that service to supply your app with info, if it applies.

should get a hold of this guy. the ability to get odb2 stuff into this app would be awesome.

No doubt. Nice app.
I just sent him an email.

We'd just have to hash out a way for his app (or any app for that matter) to talk to Voyager.

aCar is a great app!! if it could integrate with voyager for fuel fillup detections that could be kinda nice. I would say mileage too but the only way to do that would be via GPS, and you would have to tell it when u were driving (which I would definitely forget to do).

The info display in my dash can be selected to show me odometer (and other stuff). Word on the street is that it uses the class 2 bus (SWC) though (not regular CAN). If we just had a big VIN database with special codes in it.... ;-)

Fuel level is working well in Voyager. Just % fuel present in the tank. no frills.

Like on startup, if current fuel level is higher than last fuel level by X%, then start the aCar app (register a notification that user can click on to start acar app).

Originally Posted by regulatre

Fuel level is working well in Voyager. Just % fuel present in the tank. no frills.
Like on startup, if current fuel level is higher than last fuel level by X%, then start the aCar app (register a notification that user can click on to start acar app).

Exactly...and something like 10% should be more then enough.

The info display in my dash can be selected to show me odometer (and other stuff). Word on the street is that it uses the class 2 bus (SWC) though (not regular CAN). If we just had a big VIN database with special codes in it.... ;-)

Maufacturers make it very difficult to get to mileage data over OBDII to prevent tampering....most manufacturers only store it in the instrument cluster itself (well technically the CAN node representing it)....and it varies from year to year. Do a quick forum search and you should find at least one thread discussing exactly this in depth...the conclusion was that it would have to be figured out one vehicle at a time.