GM 86-95 OBD1 Guide (READ ME)

(eventually this page will have more information)

Basics

When we talk about “OBD1″ GM vehicles, we mean vehicles made from (approximately) 1986 to 1995.  These cars used several different types of engine controller – some have one injector for each cylinder (Tuned Port Injection, or TPI along with the LTx motors) while some have fewer injectors that are placed near the throttle body (Throttle Body Injection, or TBI) instead.  All the vehicles of this generation speak the ALDL protocol for logging/vehicle communication.

For purposes of this guide, “ECM” means Engine Control Module, Powertrain Control Module (PCM), Engine Computer Module (ECM) – terms will be used interchangeably to mean the same thing.

Hardware for OBD1 GM

Overview

94-95 model years are oddballs.  Many of these ECMs support being reflashed over the ALDL interface (e.g. LT1) using TunerCATS.  Some (like the 94-95 TBIs) use a G1 adapter.  Many Grand Prix from these years use the G4 adapter.  Diesels generally use the G5 adapter.

The process for tuning OBD1 GM products is pretty much the same for all 86-93 model years.  First, a “chip adapter” is used to convert whatever the ECM in question needs into a form that accepts a 28 pin EPROM.  Some chip adapters require soldering for installation (G2, G2X) but most do not (G1, G3, G4, G5).  The same EPROMs can be used for all of our OBD1 GM products (except the switching adapters…) which is usually the 27SF512 – C2.

After a chip adapter has been installed in an ECM, tuning can begin.  You can burn chips using a ROM burner such as the BURN1/2.  Alternatively, you can either use the Ostrich 2.0 emulator or the emulation facilities of the APU1 to make changes while the vehicle is running.

Logging from the computer is accomplished using either an ALDU1 or the logging facilities of an APU1.  For 86-94 vehicles, CABL1 is required to connect the logger and the vehicle.  For the 1995 model year, CABL2 is required due to the physically different connector.

Instead of buying the BURN2, Ostrich2 and ALDU1 separately, you can buy the APU1 unit that does the functions of all three pieces in one unit.

Hardware

G1 – “Memcal” style chip adapter (TPI, Syclone/Typhoon, 94-95 TBI, 92-93 LT1, etc.)

G2 – “TBI” 24 pin style chip adapter

G2 GN Style – Grand National Only.

G2X – Multiple program switching version of G2

G3 – Multiple program switching version of G1

G4 – Blue Memcal style chip adapter for some 94-95 vehicles

G5 – Diesel memcal style chip adapter

HDR1 – Header that allows reading memcals in a BURN1/2.  Used to read stock program on memcal ECMs.

BURN2 – Programs chips

Ostrich – USB Chip emulator, allows realtime changes while engine running

Socket Booster – required for use of Ostrich 2.0 in TBI applications.  Can be used instead of G2 adapter.

ALDU1- USB ALDL interface

CABL1- Used to connect an ALDU1 or APU1 and a pre-1995

CABL2 – Used to connect an ALDU1 or APU1 and a 1995 car

APU1 – Combines the functions of the BURN2 (programming chips), Ostrich 2.0 (real time chip emulation) and the ALDU1 in one unit

Applications

This table is abbreviated. If you don’t see your application here, please email us.

Vehicle Identification
Chip Burning
Adapters
Emulation
All-in-One
Datalogging
Year & Model
ECM/PCM Part #
BURN1
27SF512
G1, G3
G2 .6″
G2 .45″
Ostrich 2
ALDU1
CABL1
CABL2
86-89 Firebird, Trans Am, Camaro, Corvette TPI
1227165
X
X
X
X
-
-
X
X
X
X
-
90-92 Firebird, Trans Am, Camaro, Corvette TPI
1227730
X
X
X
X
-
-
X
X
X
X
-
86-93 TBI
1227747 | 1228747
X
X
-
-
X
-
X*
X
X
X
-
94-95 Corvette, Impala LT1
16181333 | 16188051
-
-
-
-
-
-
-
X
X
X ’94
X ’95
92-93 Corvette LT1
16159278
X
X
X
X
-
-
X
X
X
X
-
86-87 Buick Turbo, 89 Turbo Trans Am
1227148
X
X
-
-
-
X
X
X
X
X
-
91-93 Syclone/Typhoon
1227749
X
X
X
X
-
-
X
X
X
X
-

* Socket Booster (S_BOOSTER) required for Ostrich 2 emulation and TBI ECMs

If you have excel, you can also take a look at this spreadsheet for a list of what hardware you’ll need with various combinations.

Software

TunerPro RT ( link ) and TunerCATS ( link ) are the two most commonly used software packages for OBD1 GM.

There is an excellent cross-reference I found with google that lists common ECMs, which mask (software revision) they use and various other useful information.  ( link )

Holden Vehicles

TunerCat OBD1 tuner seems to have the best support for Holden vehicles at this time ( link ) although TunerPro has support for some ( link )

Hardware-wise, the majority of these vehicles use the G1 chip adapter.  Some of the newer vehicles use our newest G6 chip adapter.  We don’t know the Australian vehicles as well as those stateside so we recommend you check out http://www.delcohacking.net for more info on these vehicles.

GM 98+ OBD2 Guide (READ ME)

(eventually this page will have more information)

The main product that we make for 98+ GM vehicles is the RoadRunner emulator that allows realtime changes to be made to a LS1 ECM.

The RoadRunner is designed to be used with either EFI Live or TunerCATS software.

EFI Live is a comprehensive tuning software package that includes both an editor and logging application.  The software has the most comprehensive vehicle support out of any package we sell for OBD2 GM, working with both Gen3 and Gen4 ECMs and TCMs.  It is licensed on a per-vehicle or per ECM type basis.

Tuner CATS OBD2 tuner is used primarily with the RoadRunner hardware.  It only supports Gen3 LS1 ECMs/TCMs.  Tuner CATS OBD2 tuner can ONLY BE SOLD WITH ROADRUNNER HARDWARE.  WE CANNOT SELL IT TO YOU UNDER ANY CIRCUMSTANCES UNLESS YOU BUY ROADRUNNER HARDWARE.  It is licensed on a per ECM type basis.

Ford Overview (READ ME)

“I have a Ford.  What do I need to tune my car?” is an email we frequently receive.  Hopefully this page will provide some answers.

We also often get asked, “Can I use your product to let me put _______ on my engine?” The answer to this is very simple: our products let you tune factory Ford computers.  If the factory Ford computer can do it, our products can help you tune it.  If there is another factory Ford computer that you can swap to run your engine that does what you want, great.  Some examples of what I’m talking about here include putting a MAF sensor on a car, running a car without a MAF speed-density, switching to coilpacks, etc.  If you can’t do it with a factory Ford ECM, our products aren’t going to help you achieve your goals.

We offer products that work with almost all ~1986-2004 Ford ECUs that have a J3 port (i.e. EECIV and EECV).  International users report success using our products with non-US computers that have a J3 port.  A J3 port looks like an edge of a circuit board that kind of sticks out.  J3 ports must be cleaned with a wire brush and solvents in order to remove the protective coating on the circuit board before they can be used.  They are almost always behind a rubber protective panel.  We do not offer any products for Ford computers that lack a J3 port, such as pre-1986 and 2005+ computers.  Also, cars branded by Ford but manufactured by others (i.e. Ford Probe, made by Mazda) often use computers that lack J3 ports.

It is critical that the vehicle is fully off before installing or removing anything on the J3 port.  Failure to power-off the ECM correctly can result in frying our hardware, your ECM or both!!!  If you have any doubts at all, remove the keys from the ignition 100% or disconnect the battery.  WARNING WARNING WARNING!

On this page “application” simply means the car/ECU/engine you are working with.

“ECU” means ECM, PCM – the computer running your car’s engine.

“Strategy” is Ford lingo for a set of procedures (i.e. code) that an ECU runs.  (Closest GM term: Operating system)  Most of the time, a strategy is particular to an ECU, i.e. the GUFB strategy runs onA9L ECUs.  Sometimes more than one strategy can run on the same ECU (i.e. GUFB/A9L + GUFC/A9P) .  Most of the time the “tuner” cars (i.e. Roush, Saleen) use unusual strategies that are often simply renamed factory strategies.

“Definition” means a file that describes the location of parameters that can be changed in a strategy.  All of the Ford tuning software uses definition files to process raw files.

“Patch code” refers to special routines that change the way a strategy operates in order to allow Quarterhorse to log all vehicle parameters.

Hardware used with Ford:

F3 Chip adapter – This stores a new program for a Ford ECU and clips on the J3 port.  This is a simple Ford “chip” that can optionally store two programs.  It works with both EECIV and EECV.

Jaybird – This is a Ford-specific device that writes F3 chip adapters ONLY.  It uses the same Flash n Burn software as a BURN1/BURN2

F2A – The F2A is a Ford interface for the BURN1/BURN2 programmers.  It lets you write a F3 chip adapter using a BURN1/2 programmer and the Flash n Burn software.

F2E – the F2E is used with a F2A and a BURN1/2 to read the stock program from a ECU.

BURN1/BURN2 – These general purpose ROM burners can be used with a F2A to program F3 chips

FORDEMU – This adapter allows the use of a Ostrich emulator to make real-time changes with a Ford ECU.  This product has been replaced with the Quarterhorse.  It does not work very well with EECV ECUs.

Quarterhorse – The Quarterhorse (or “QH” for short) is our flagship Ford tuning product.  It allows changes to be made while the vehicle is running.  It also allows datalogging by spying directly on RAM locations.  In order to log all vehicle parameters, patch code that is specific to each strategy is required.  Many of the features of QH require special definition files and/or software support that may not be available for all applications.

Software for Tuning Fords:

You can read the binary from any J3 Ford computer with our gear (BURN2+F2A+F2E), but that does NOT mean that any J3 ford computer is fair game.  In order to be able to display a raw binary from a Ford ECM in a real-world units that might make sense to you, a definition is required.  The def is kind of like a roadmap that allows software (Binary Editor or EEC Editor) to translate what runs the car’s computer into something meaningful to you.  Defs have to be developed by a human being for each application.  PLEASE ASK US FOR HELP IF YOU ARE NOT SURE YOUR APPLICATION IS SUPPORTED!!!

TunerPro / TunerPro RT (www.tunerpro.net) : Great for basic editing.  Free.  Somewhat limited definitions compared with other software.  At time of writing (11/28/09) lacks full support for QH, but beta versions have support.

EEC Editor (http://www.moates.net/product_info.php?cPath=33&products_id=75) : Cheap ( <$50 ) software with fairly extensive editing support for editing Ford tunes.  EEC Editor requires you to purchase definitions on a per-strategy basis.  One strategy will cover more than one box code.  Definitions for datalogging can be purchased separately.  As of time of writing (11/28/09) has QH support for MANY applications including Fox body mustang (GUFB/GUFC/etc. A9L/A9P/C3W/etc.) 94-95 Mustang (T4M0, CBAZA) along with many 96-03 applications.  Custom definitions available for a fee.

Binary Editor (http://www.eecanalyzer.net) : Relatively cheap ( $80 BE / $130 BE + EEC Analyzer) software with comprehensive editing support and comprehensive support for QH.  See here for a list of strategies supported.  Binary Editor comes with a bunch of definitions that are free and there are others you need to pay for.  You can see most of them at http://www.eecanalyzer.net in the downloads section.