When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I am thinking I'd get the OBD Car Doctor Pro version of the app, since that is also on both Android & iOS. This way I've got 4 people in the house that can all check their own car without me needing to be present - just the wifi dongle.
Is this plan going to work for the F350? Going proprietary OBD to OBDII thru the cable seems a bit ghetto, but if it will work I'm on it. Anyone here have experience with converting cables etc with these?
I would also like some opinions on this. I'd like to get a code reader but don't know much about them. I think for OBD I all a code reader does is count flashes for you. I feel like I'd probably get more use out of an OBD II code reader but at the same time, I hate to buy one that doesn't work on my own vehicle. heh
I would be pretty skeptical about those converter cables. OBD1 and OBDII are two completely different protocols and there is no reader that will do both satisfactorily and economically. There have been products that will do this, but they are not any sort of app you can run on your cellphone. They are dedicated pieces of equipment, outdated and likely difficult to obtain.
The ELM327 OBDII device is pretty good. I use one with the Torque app and it works well with any OBDII vehicle I have tried it on. Running it on Android phones and tablet. Free version works well.
Back on your earlier vehicles, anything OBD1 can be considered proprietary. That's the main reason OBDII spec'd a common code set for the basic engine functions. There still is a bunch of proprietary codes for transmissions and body control modules and I hope you realize your basic OBDII readers will not handle any manufacturer specific codes. I don't know anything about the Toyota OBD system, but the reader for the Ford codes is pretty common. Or simply, count the flashes.
I figured it was going to be thin pickings for the old Ford and the old Toyota on that front. Sounds like I should pick up the dedicated device for the Ford at least. Cost would be about the same as the converter route, or a little more.
I've got to get a post on a Toyota forum about what I should do for the 93 Camry.
Those adapter cables are for specialized scan tools designed to handle a large variety of different protocols. The ELM327 adapters is not such a device, and no software out for them would know what to do with it.
There is really no such thing as an OBD-1 "standard" - both the Toyota and Ford systems are completely proprietary, and will need their own adapters. However, you can check the codes on the Toyota and the Ford with just a paper clip.
The Equus/Innova 3145 is a cost effect code reader for the older Fords, there really isn't much else to see. I have another generic OBD2 code reader but it doesn't show any of the brand specific info that I can get with a ELM327 interface and the Forscan software combo for example. This is the way to go for any newer vehicle IMO, the interface will work on anything you just need a brand specific software or app for each different vehicle to get at all the available modules and data.
For the older Fords, I have an OTC Monitor 2000 with Pathfinder 1993 cartridge which covers up to 1993 definitions but really scans anything Ford OBD-1 since it will report any code that it 'clicks' ( counts sweeps like you can with a paper clip or volt meter ). It might not show what the code is if it is older... The Pathfinder 1993 Cart also has the OEM Ford scan stuff, whatever it was called then I can't remember. I was able to get into the menu for it on my old 1992 Ranger but without the manual for it, I didn't know how to use it