Btw the link for the cable doesn't work?
Otherwise thanks for that.

 

All those cables say 96 and newer so thats mine out.

 

That why he said OBD2 96+, I take it hince your name you have a OBD1 94

Sent from my PG86100 using AutoGuide.com App

 

"but should work on most pre 2008.
My bad.

 

coco, downloaded the exec's (They passed virus and Malware scans) and read through the PDF file. Looks like a decent free solution for OBD2. Problem is I only have 1 OBD2 vehicle a Ford product others are all OBD1. Really interested to see where this goes...AKA: FreeScan . The .pdf 'GD Scan Guide' looks like it's using SAE J/1979 standard PID's so it may work for the standard major parameters on my 2003. Think I may order up a cable and give it a test. Going to search around to see if I can find a manufacture specific PID list for my '03.

 

Just downloaded the files, picked up a trojan off the site itself. Use caution.

 

Bob, I believe what GaryDoug wants, is for people with cars other than f-bodies to try out program and see how it works. Your Ford obd2 car is a perfect candidate.

 

Actually any 96-02 car that works would be helpful, especially the F-series ones. What I am needing is a list of PID's supported for each year car and each version engine. It's not absolutely necessary, but I would like to know if I can just run the scan of them without having to require the user to scan for them all. Email me for the instructions on how to create the PID list and I will be glad to share the identified results with you.
The first version is just the standard mandated PIDs and may work for most cars. I know it works for a 98 Bonneville, 98 Firebird (V6 and V8), 95 Lexus ES350, and a 2006 Hyundai Tiburon. It may have a problem with the 99 and newer cars because of the multiple controllers (It only assumes a PCM on the bus) The second version may work on most cars too, but I will be shifting to the GM cars only to make use of the proprietary enhanced PID sets and bi-directional controls, and will be directly addressing the PCM to avoid conflicts with the multiple controllers on the newer cars. So if you want a non-GM version, stick with the 1st version. For GM cars, stay tuned for more capable versions.

 

I see there have been many downloads of the two versions and I have a question. Has anyone had any problems using the version 2 program (GD-Scan2.exe or GD-Scan2a.exe) on an 96 or 97 V8 (LT1) engine?

A member has reported that some features will not work on his 96 car, however it is "Hypertech-ed"; and I can't tell him if that affects the enhanced data capability. Thanks

Edit 8/22: Another user with a factory (unmodified) 96 PCM reported good results

 

Off topic but the link to the Freescan program is dead?

 

Its definately down atm , here's another link:

FreeScan | Free Communications software downloads at SourceForge.net

 

Yes frescan web page is dead. Don't know if it's for good or just down for a while. It's been dead in the past.

 

My ADL cable finally arrived after customs obviously decided they had kept it long enough.
Just to say that OBD diagnostics supply a driver disc which is also crammed full of scan programs.

 

I am well along in writing an OBD1 scan program for the 94/95 LT1 F-series cars. It will contain more data than the Freescan app and about the same basic material as Datamaster (a few less "cute" features) when done. I will add some bi-directional actuators as well: Fans, A/C, MIL, evap purge, EGR duty cycle, AIR pump, and closed/open loop mode. Most of it is already working but I will take some time to dress it up and add some graphs (maybe) and datalogging before offering it for free. Anyone who wants to try it now (or at any time) can just ask.

 

Yes I want to try it, but I will wait until you complete the program. And as always, members of ls1lt1.com thank you.

I don't suppose there's anyway you could include opti high and low resolution pulse, in your program? That would be a winner to members of both forums.

 

The problem with that is the PCM does not give much information on those signals. The low res signal is reported by the time period period in milliseconds (which is used to calculate the RPM, the inverse value). The high res signal is not reported except as a "present/not present" value and as a failed DTC. These are how the Tech 2 reports them and I will do that as well.

 

I placed the first beta version in the same folder with the GDScan app:
My Files
The filename is Scan9495.zip.Two files, just place them in the same folder. Won't work with XP just yet and no dialoging at this time. Many actuators though, something the others don't have. This version is for the automatic, but I can adapt it to manual. For those with a newer pc and no serial port, you will need a USB-type cable. You can make you own setup for about $20-30. let me know if you want instructions.

 

Are you going to make a version that works with XP. I'll probably be stuck running xp until it's so obsolete it no longer functions.

 

There is no reason this shouldn't work with XP, but it won't on my old XP PC. I don't know why, because versions only 5 days old work fine. I will be trying to figure this out. Perhaps you could run it and tell me the errors produced.

 

I think it's working on XP now, even though it doesn't look it's best aesthetically. I found some bugs and corrected them.

 

I'd like to give the OBD1 a try w/XP Home installed on laptop.. question can the OBD2 ELM 327 cable be used for OBD1 by jumping pins 9 to M (serial data) and 4 & 5 to A (Ground). If so I'll need to order a cable, been using OBD2 ELM 327 Bluetooth adapter w/ Android Torque App to play with so I don't have a cable. Looking at this.. Amazon.com: HDE ELM 327 Diagnostics USB Cable: Electronics. I have a F/B/Y -Body 16188051 OBD1 PCM set up on a bench test setup I can play with..

 

See the new topic "OBD1 scan program for free" for the reply.

 

Thanks for the new program

 

will this not work with windows 8? or am I doing something wrong?

 

Two users have verified proper operation with Windows 8. Can you be more specific about what doesn't work for you?
Also please use the OBD1 topic instead of this one for the OBD2 app. It has much more detail and communications.

 

Will a ELM 327 Interface cable work for this or will I have to buy the cable that is being posted in this post?

 

Go back to post #1, it says you need an elm 327 cable. Any elm 327 will work, if it's been put together correctly. So if you buy a cheap Chinese made cable, take it apart to make sure connector pins are tight and soldering is done well on circuit board.

 

This topic is for the OBD2 systems which are on F-cars from 1996 to 2002. OBD1 is in another topic for F-cars from 1993 to 1995 (94 and 95 supported).
Each type of system needs it's own unique type of cable. 96-02 cars need the ELM327 type or an equivalent. 93-95 cars need a different type, which you can build or buy. They are not interchangeable.