Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 36

Thread: Voyager: Bluetooth OBDii for the Droid

  1. #21
    Raw Wave
    Auto Apps:loading...
    justchat_1's Avatar
    Join Date
    Jul 2008
    Location
    Boston, Ma or NY,NY
    Posts
    2,359
    Quote Originally Posted by regulatre View Post
    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.

  2. #22
    Low Bitrate
    Join Date
    Dec 2009
    Posts
    77
    I did some research last night and it shouldn't be too tough to write a data provider that lets any Droid app access Voyager data. It's all done through cursors/recordsets.

    Next steps
    * DONE! Write a thread that provides "awareness" of overall system state up to the second
    * Finish making Voyager a fully autonomous background service
    * Expose a data provider to Voyager for controlling it.
    * Write a simple control interface that uses that provider
    * Expose other data providers for access to the data.
    * Finish making powerpoint presentation that explains everything about Voyager

    This morning I remote started my car while I was getting ready. I started up Voyager and turned on the autoscan. Even though I was walking around the house, it never lost the connection! It continuously scanned 45 active PIDs (It disables unsupported pids if they fail) and never had to reconnect. At some points there were 3-5 second delays between responses but it always picked back up.

    Average scan rate is 5 pids per second, and I haven't done any work on optimization yet!

    I was up late writing a new thread function that monitors the overall system status and runs various hooks based on what state the OBD system was in, and is currently in. This will let me do things like keep track of trips (trip starts on engine start, trip ends on engine stop)... This plays into making Voyager a fully autonomous background service. It can be commanded by UI but I want it to be fully self-supporting if the user doesn't want to interact.

  3. #23
    Low Bitrate
    Join Date
    Dec 2009
    Posts
    77
    Moving along faster than expected. The Content Provider is already starting to work as I add features. Background service is complete. Working out kinks, finishing loose ends.

    I'm in contact with the author of aCar.

    Some sample data I sent to Armond/aCar:

    time source requestID raw data description
    2010-01-03 00:25:44 7E8 48 96 58.8236 Fuel Level Input
    2010-01-03 00:26:21 7E8 48 92 57.2550 Fuel Level Input
    2010-01-03 00:26:47 7E8 48 9D 61.5687 Fuel Level Input
    2010-01-03 00:27:13 7E8 48 90 56.4706 Fuel Level Input
    2010-01-03 00:27:33 7E8 48 8E 55.6863 Fuel Level Input
    2010-01-03 00:28:15 7E8 48 8B 54.5099 Fuel Level Input
    2010-01-03 00:28:27 7E8 48 80 50.1961 Fuel Level Input
    2010-01-03 00:28:38 7E8 48 9A 60.3922 Fuel Level Input
    2010-01-03 00:28:53 7E8 48 93 57.6471 Fuel Level Input
    2010-01-03 00:29:15 7E8 48 90 56.4706 Fuel Level Input
    2010-01-03 00:29:25 7E8 48 93 57.6471 Fuel Level Input
    2010-01-03 00:29:35 7E8 48 95 58.4314 Fuel Level Input
    2010-01-03 00:29:44 7E8 48 96 58.8236 Fuel Level Input
    2010-01-03 00:29:53 7E8 48 9B 60.7844 Fuel Level Input
    2010-01-03 00:30:03 7E8 48 8E 55.6863 Fuel Level Input
    2010-01-03 00:30:13 7E8 48 93 57.6471 Fuel Level Input
    2010-01-03 00:30:23 7E8 48 9D 61.5687 Fuel Level Input
    2010-01-03 00:30:32 7E8 48 85 52.1569 Fuel Level Input
    2010-01-03 00:30:41 7E8 48 84 51.7648 Fuel Level Input
    2010-01-03 00:30:51 7E8 48 6B 41.9608 Fuel Level Input
    2010-01-03 00:31:00 7E8 48 8A 54.1177 Fuel Level Input
    2010-01-03 00:31:09 7E8 48 89 53.7255 Fuel Level Input
    2010-01-03 00:31:19 7E8 48 80 50.1961 Fuel Level Input

  4. #24
    Newbie
    Join Date
    Dec 2007
    Posts
    19
    Just wanted to let you know a lot of us are anxiously looking forward to this app and wishing you the best in putting it together.

    Good luck, can't wait to see it in action.

  5. #25
    Low Bitrate
    Join Date
    Dec 2009
    Posts
    77
    Thanks for the support. I'm trying to grind some last changes before I release it for testing. With the holidays over, work is busy as ever so I'm moving a little slower again.

    Also I'm grappling between releasing it open source or putting it on the app market for $1-$20. just not sure yet.

    How should I release it?

  6. #26
    Newbie
    Join Date
    Dec 2007
    Posts
    19
    I am a fan of open source and I run Ubuntu on my machines at home. Having said that, I have no problem paying for software that does what I need it to do. There's no reason why you couldn't do both. Make the software open source, let the community improve on it but sell the original (or most stable) version through the app market.

    You could also release it as a free app and then charge for custom skins (sort of like some of the Droid home screen changers do). So someone that wants to run the vanilla app can do so for free but if I want something customized for my car (with my car's logo for example), I would pay a little extra.

    Or give away a version with some of the features turned off (for example, you could sell a version that doesn't remember any stats from the previous time it was on) and then charge for the full, unlocked version with all the bells and whistles.

    If you do sell it, remember that most people will need to buy an additional piece of hardware (the OBD2 dongle) in order to make use of the app. So price accordingly. Hell, you might even consider partnering with a hardware maker and let them bundle it with their device. I would definitley buy the dongle from the company that already had software that worked on my Droid.

    I think you should be compensated for your work. Having said that, the reason I like open source is because sometimes you get improvements when the community is working on it that you wouldn't get otherwise.

    It's a tough call and I wish you luck. I will track the progress and definitely look forward to reviews when it is ready.

    Good luck!

  7. #27
    Low Bitrate
    Join Date
    Dec 2009
    Posts
    77
    Created new thread for testing:
    http://www.mp3car.com/vbulletin/soft...yager-obd.html

    Ready to start letting people test!

    If you have an OBDii bluetooth adapter, an Android phone, and a car, you're ready to test!

  8. #28
    Low Bitrate
    Join Date
    Dec 2009
    Posts
    77
    Voyager has been relased on the Android market. find it as VoyagerConnect.

    Look in the coming weeks for Voyager Dash - which will be an open source dash board for real time OBD monitoring. VoyagerDash will use VoyagerConnect, and intended as an open-source project to jumpstart the use of Voyager Connect by other apps wishing to add OBD support to their app.

  9. #29
    Newbie redleader36's Avatar
    Join Date
    Dec 2007
    Posts
    16
    i don't know how many people would be on board with me, but how hard would it be to make this a whole track package for data acquisition? There is another app out there called Voyager which captures video, images, and datalogs/geotags gps location. could these 2 be combined to make a whole track package that 1) datalogs simple obd2 data such as speed, rpms, and maybe ABS data (i know you are working on ABS) 2) logs gps, 3) captures video.

    I do not even have an android phone yet, but am really looking forward to trying out your program! moto droid should be here on the 27th! i would be really excited to have a whole data acquisition device that i just suction cup to my window during autocross!

  10. #30
    Low Bitrate
    Join Date
    Dec 2009
    Posts
    77
    RL,
    Thanks for your interest! VoyagerConnect logs all of its data to a database which can be accessed by any app through a simple content provider interface. In other words, Voyager already is "ready" for that type of use. Other apps just have to access the data using a content provider and they can add it to their app.

    Say for example the app you mention that captures video and images and GPS location. If Voyager is running in the background, that app can contact Voyager and download live vehicle data at any time or continuously.

    I pulled VoyagerConnect from the market temporarily while we work on a big upgrade. The new release will come out soon, and will have some fun new features.

    Quote Originally Posted by redleader36 View Post
    i don't know how many people would be on board with me, but how hard would it be to make this a whole track package for data acquisition? There is another app out there called Voyager which captures video, images, and datalogs/geotags gps location. could these 2 be combined to make a whole track package that 1) datalogs simple obd2 data such as speed, rpms, and maybe ABS data (i know you are working on ABS) 2) logs gps, 3) captures video.

    I do not even have an android phone yet, but am really looking forward to trying out your program! moto droid should be here on the 27th! i would be really excited to have a whole data acquisition device that i just suction cup to my window during autocross!

Page 3 of 4 FirstFirst 1234 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •