Announcing the PriusChat OBDII Phone App Project

The "cable" is already on the market.... PLX Kiwi - Kiwi Wifi, Kiwi Bluetooth, Kiwi MPG, Kiwi Drive Green OBD 2 Devices  - your choice of using WiFi or Bluetooth...

 

could we get a group price break on the modules? I saw the apps out there already on itunes.

 

Exciting

I'd like to help out with software development if we agree to release it under one of the Open Source licenses.

 

The gopointtech mod makes me want an Ipod touch now. Darn you Tony.

 

It looks like that and the Kiwi Bluetooth are both about $99, and both come with apps for the phone. The big question is, how extensible are those apps? If they have a way to import our PID tables (and maybe DTC definitions too, would be nice) that's a 95% solution right there. Has anybody checked the docs for either piece of software yet to see how it stacks up on that front?

The other 5% of a perfect solution would be defining new vehicle specific displays (pretty gauges or animations for HSD behavior or battery temps or what not). It's probably less likely (but still possible) that the existing software apps make it easy to create new graphical displays. As with most projects, it'd be easy to spend a whole lot of the effort on the last 5%.

I would bet there are way more than two smartphone obdii apps already devloped or in development, probably some that are open source. I would guess a good place to start would be to compile a table of those, comparing them on the ability to define new PIDs and DTCs and to create new displays. If that table's on a wiki, several people can investigate different apps and contribute findings.

Have you already chosen a place to host (sourceforge or the like) this project? I have an old sourceforge account (they're free) and can set up a new project there if nobody has another preference. I can check in the NHW11 PID tables we've already got, and also put a wiki there, which would be a good way to handle design discussions and the review of existing apps and their capabilities. I can't commit to be project lead though; I can be the guy who sets up the project hosting and the initial list of participants, and then I'll be one of those.

I've just looked over the sourceforge terms of use, and they force a decision on which open source license we want to use; it's supposed to be designated before any code is uploaded.

-Chap

 

Since my check engine light went on a few weeks ago for my '02 Prius, I bought a Bluetooth ODBII scanner from Ebay for about $35. It shipped from China, sure, but it works well so far and was dirt cheap compared to most of what you find here. I use is in conjunction with an Android-powered HTC EVO phone. I've tried several ODBII programs so far, but Torque is the easiest to use and seems to be the most powerful (as in, full of options I'd be too afraid to play with). It's both free and premium. I'm using the free version, but I think I'll be a big spender and pay the $8 for the full version. Suffice to say, Torque and the others I've downloaded (all free, btw) seem to offer all the options that those expensive programs I looked at over the web do.

That said, none of these programs offer car-specific settings that I've noticed. Especially not a Prius specific interface, which would be ideal. I oddly got a trouble code reading of P2000, which is not in any list of trouble codes anywhere... Best I can tell, it might mean something is problematic in the O2 sensor of the catalytic convertor...

 

FWIW - I have the Kiwi ($150) and the Rev App ($40), both of which work well, though the Rev app obvioulsly doesn't have some of the hybrid specific parameters the hypermilers want to see. The Rev app seems well put together and has a nice design quality. The gopointtech is definitely cheaper, at $100, and unlike the kiwi, it has auto shutoff, so it can't put a vampire drain on your battery if you don't turn it off.

Here a Rev app link: DevToaster - Rev - iPhone app development, Great iPhone apps, and more

 

I like that attitude. Let's maybe throw a dart and pick one of the open source licenses already written that will satisfy sourceforge (I should ask Graham Davies if he has a preference since some of his stuff's in the NHW11 PID tables) and I'll set up a sourceforge project for it.

Whoever wants in, get a free sourceforge account if you don't have one already, let me know the name and I'll add it to the project.

-Chap

 

... I'm partial to the most unrestrictive ones, like MIT, myself ....

-Chap

 

Please make it for Droid too!

 

To get a little techie here, I'd recommend not using a GPL. I've read so far about two apps being forced off of the iTunes store by GPL advocates because even though they're free, even though anyone could download them, and even though their source code can be obtained freely as well, it's not "free enough" for GPL because you can't download it on your phone and then transfer it to someone else's phone.

 

I'm not an authority but my understanding is that the answer's no, that the iPhone uses technical measures to prevent installing an app that didn't come from their store. (Some people do jailbreak their iPhones and get around those measures, so in that sense the answer is yes, but not on an un-jailbroken iPhone if I understand it right.)

I hadn't been following that story, so in case I wasn't the only one wishing the earlier poster had supplied a link, here it is (from the FSF's side):

FSF on App Store usage terms

As a practical matter, the choice of license may have a lot to do with what existing code is out there and how it is licensed. If a nice open source obdii app exists that does nearly everything we want, can be extended with Prius PIDs, and is under the GPL, we would have to have way too much time on our hands if we wanted to duplicate all that effort from scratch just to use a different license.

My feeling, I'm happy to, say, MIT-license my own stuff, which doesn't really create any license conflicts for anybody else. Assuming we don't develop a whole obdii app from the bare metal up, we'll be finding useful pieces by others to include. If we can find all of those in MIT or BSD licenses, great. If some of them are GPL then the overall combination is GPL, which might complicate distributing an iPhone version, but the alternative would be to pass up free code that's already there to use and redevelop it from scratch.

My own leaning would be to try to find the best existing pieces to put together and if some of them are GPL then concentrate on an Android distribution first and see how Apple resolves the issue (which might even happen by the time we actually care).

-Chap

 

For those not bored by such things, here's another discussion with a few interesting comments strewn about:

Can GPL iPhone apps exist?

-Chap

 

hi Chap.

my username on sourceforge is 'reeed'