I did a site search and found some info on this subject which was mostly a year old....wondering if anyone has located software and cable which connects the Palm units to our OBD1 systems?
Guess who just inherited an older Palm, it sure would be nice to see the Palm on the dash instead of the laptop and bucket sunshade I'm using rolling around on the back seat.
Craig Moates posted a request for interest...looks like this issue has maybe died?
Has anyone found a package???

 

I found a web link to Miragecorp which I gained by following a thread suggesting Pervinco.com had Palm OBD1 info....well I sent them a email and got this prompt reply from Chris Dooley from http://automotive.miragecorp.com/Contact/Contact.html.

Siggy

Reply as follows:

Unfortunately right now, the products will only work on the select cars listed on the website. OBDI was a "fuzzy" standard, in that it wasn't really a standard at all. Before 1996 manufacturers programmed whatever they wanted into their diagnostic system, and everyone was different. But after 1996 it was regulated so that one code reader could read everyone's car.

This is why there is basically a scan tool for every car before 96, and why autozone can only read codes on cars 96+ for you.

Thanks,

Chris Dooley
Mirage Computers, Inc.
cdooley@miragecorp.com

 

I started doing a bit of research on this last week, as i have an older palm visor not doing a whole lot with.. (already figured out how to make my dock charge my non-chargable palm visor)

What you have said is correct, which is why we need to know what streem (ECM) your looking at when collecting data... we do that part now, so that part is already figured out...

So far what I see as the issues for using a palm are:

1) cable to input data to palm. This part seems to have been solved but im still looking for more info. on a simple kit or somthing.

2) software to collect, store, view data. Stuff avaliable seems very $$$.....

I havent searched much yet so maybe there is some obviouse freeware type source for this stuff...

-mike

 

To any and all following this thread, I received this reply recently from Reid of Pervinco who was trying to develop Palm ALDL...here is the reply.

LeRoy,

Embarassed to say that all development halted some time ago. It's working pretty well for the older series, but I ran into some hardware snags on the more modern ECUs. I didn't really advertise this effort that much, so I wasn't aware there were any folks out there interested.

I may resume work again, given a sufficient level of interest. The Sync software to the PC is all done and works well, as is the PC display software. Where I really need to focus is on the ALDL interface (which I now have a completely new design for).

-Reid-
Pervinco.com

-----Siggy asked----
Sent: Tuesday, July 05, 2005 1:00 AM
To: info@pervinco.com
Subject: Palm OBD1 ALDL


Hi Pervinco



Nice web page, have you made any progress with a Palm OBD1 logging package???

Sure would be keen to learn more and so would a few form members on https://www.thirdgen.org/



Regards

 

So? Any more info? That would be the perfect setup.

 

I think ALLOT more people would prefer a PocketPC solution. There are a few PPC's with a standard 4-pin usb connector for the usb to aldl cables we already use and a PPC version of TunerPro RT to go with it would be the absolute shiz :hail:

 

One of these days I'll "borrow" my wife's PPC and write a logger for it. Maybe when I have more spare time. Maybe when I quit my day job. Maybe...

(Don't hold your breath).

 

Well I'll tell you what, when you think you can set the time aside and do it, drop me an email and I can provide with a PocketPC with a 4-pin usb and Windows Mobile 5 that you can use for testing since all the new ones from now are going to be WM5 and the program has to be written differently than with previous PPC OS's. This makes sense because WM5 uses memory different than the old ones and this will be the trend for atleast 10 years from now. It might make sense to write it for the older OS because thos PDA's are plentiful now but then you would need to re-do it for the newer OS's. I'm babbling, anyway, let me know. Even 2 years from now if thats how long it takes. I wish I had the time to learn what you know to help you out....

 

I wrote a logging program for the PPC, using embedded visual basic, worked with my Zeitronix Zt-2 wideband setup, but just barely.

Embedded visual basic is not supported anymore, and as I do not know 'C', or have the new Visual Basic .Net, I quit working on it.

Some timing issues with EVB, it is too slow. It can capture the data ok, but if you want an updated display, it slows it way down.

I am sure a '.net' or 'C' expert could write one that would be fast enough.

 

There are a ton of threads on this topic, but nothing conclusive. Some of the threads discuss Craig Moates' project of porting WinALDL to Palm OS. Anyone know of any progress or products?


Thanks!

 

Just update anyone who reads this threads on the tech of the last YEAR, lol...

Palm is no longer made. It's Windows Mobile ONLY and nothing else. Whatever is going to be ported or written must be written for either WM2003SE, WM 5, or WM 6 which is going to be released in a few months.

Personally, I want a version of TunerPro ported to WM2003SE. Then I can use all the xdf, ads, and bin files that I already have. Heck I would even pay another $30 in a heartbeat. Someone would have to write a USB driver that we can run in the mobile devices ROM, and then made an adapter to go from the USB ALDL cables we use now to plug into a mini USB like on a PDA. I would be able to cook the driver into the deviced extended ROM cabs and help with beta testing....