Free Palm OBD-II code reader software from me
 

After playing with another free package, I've found it locks up more than mine does -- don't know why. So I'm making mine available in it's current form.

http://home.earthlink.net/~johngrigg...s/obdpalm3.jpg

I'm also not totally happy with the data collection module of the other package as far as speed -- I think I can do better maybe. We'll see. I'll let you know and perhaps post some beta's.

This softwaer I'm giving away comes in two parts: a Palm-OS executable called OBDPALM.PRC and a database called Generic-3ELZ.PDB. I have registered the app with Palm and my developer ID for this project is 3ELZ. You may not sell this product (I don't know who'd buy it so far anyway, lol) but you can use it for yourself as you see fit.

It looks like this when it comes up. Tapping the "Check" button starts the code retrieval sequence. The codes show up in the list box on the right, which scrolls if there's a bunch of them. Tapping on the codes displays a pop up with the decoded text.
http://home.earthlink.net/~johngrigg...s/obdpalm1.jpg

I compiled the database from a number of public domain sources and it's the most complete set of codes I've found for Fords. You can use the database for your own purposes if you like.

The software can be used even without a scantool to look up codes. There's a menu selection for that ("Search Codes") as shown here, and the second screen shot shows the screen with a code entered and decoded.

http://home.earthlink.net/~johngrigg...s/obdpalm2.jpg
http://home.earthlink.net/~johngrigg...s/obdpalm4.jpg


You need the type of interface based on the chip made by Elm Electronics of Canada ( http://www.elmelectronics.com ). Scantool ( http://www.scantool.net ) sells the interfaces and cables and gives away software for the PC.

Here's my software and database (click and save, or right click and save, then sync to your Palm):

http://home.earthlink.net/~johngriggs/bin/OBDPALM.PRC

http://home.earthlink.net/~johngrigg...neric-3ELZ.PDB

It should run on all palms from an early Palm Professional to just about any newer Palm PROVIDED that the unit has a serial port. Keep in mind that you need a null-modem adaptor to use it with the Scantool interfaces, or you need a suitably fabricated serial cable.

Right now, the software only gets stored and not pending codes, and allows you to see the text message for that code when you click on the retrieved codes from a list. If you have a 2001 or later vehicle it will also tell you the VIN number of your vehicle.

You can turn off the MIL/CEL with it as well.

Have fun and post questions that come up in using it here.

I'm putting in the "pending" code list in the next two weeks or so when I get a chance to work on it.

are you kiddin me???



******* you are smart man

I picked up John's sofware a few weeks ago, and I gotta say the man is pretty dang smart. Everyone should take advantage of his generousity and get a copy. Mine is running on an old Palm Pro, and it works great. You can pick up one of these old PDA workhorses for around $20 on ebay. Add a $100 OBDII reader and cable, and you have a very nice diagnostic tool. I'm about to order the reader, but can't decide which company to go with.

Either way, John's software is AWESOME. Thanks again John, you da man!

way cool man! so this is only a diagnostic device? u cant tune anything with it, correct?

True, since the OBDII interface that you need to get will only read the codes, and cannot program the ECU like a Bama Programmer would.
You can however reset the CEL light, which helps tremendously when looking for trouble.

Sorry, there is a lot of info I don't have. The frames to modify memory are very specific and formatted or encrypted in ways I have no knowledge of.

What I've done is pretty easy for the average professional programmer. Thanks for the compliments though! :smile: The hardest part was assembling the database from public domain sources, and putting it in .pdb format -- and even that wasn't so much hard as time consuming.

Like I say, it doesn't show you "pending" codes, or drive cycle results, but I'll be adding those later. Pending codes are faults which have been detected, but haven't been around long enough to excite the PCM to the point where it's going to flag it with a CEL. Drive cycle results are part of what emission tests look at and they verify that the "dynamics" of PCM operation result in proper control throughout a variety of conditions.

very cool... i just need to find my palm and i can use that

Try the inside of your hand... Sorry, had to do it!