Ford: Strategies supported

Introduction

Although you can use our Ford hardware ( F3 Jaybird QuarterHorse ) on just about any 86-2004 Ford, software is much more lacking.  Currently (Feb 15 2011) there are three software packages that support our Ford hardware – Binary Editor, EEC Editor, TunerPro RT.  Each software package has a different set of computers that it works with although there is quite a bit of overlap on more popular strategies.  For the most part, US and Australian ECMs are best supported – European models are quite lacking in comparison.

Note that most of the information about software support will deal with STRATEGIES not processor codes.  We have a box code-strategy cross reference.  If you don’t see your box code listed there, we will generally be able to help you figure out which strategy your ECM uses most of the time from its box code – send an email to support@moates.net.  Worst case, you will have to read the stock computer (with QuarterHorse or F2E ) and email us the binary.

The following information is REASONABLY up to date as of Feb 15, 2011.  (I will try to update it periodically)

EEC Editor – Supported Strategies

The best way to find out what strategies are supported by EEC Editor is to download and install it!  After you have updated the software, you can see all supported strategies by looking in the directory “C:\Program Files\EEC Editor\definitions”  which contains a file for each strategy EEC Editor can open and edit.  You can see which strategies support datalogging with the QuarterHorse by looking at the directory “C:\Program Files\EEC Editor\dlms”  Please download the software and play with your computer’s definition / DLM prior to purchase as not all strategies are equally complete.

There is also an excel spreadsheet which may be very helpful for determining if there is support for your vehicle. This spreadsheet has more accurate information than this web page.

Supported Editing strategies:

1990F250.DEF
1DDB.DEF
1deb.def
1dec.DEF
1dga.def
2dbd.def
2dca.DEF
2dda.DEF
3dea.def
a9u2.def
AGANF.def
AKAM9.def
akama.def
AKAMH.def
akc0.DEF
AOAG3.def
ATAN0.def
bnaf9.DEF
boae4.def
c3p2.def
C3W1.DEF
cbaz0.def
cbaza.def
CCAQA.def
CCAQE.def
CDAN4.def
CDAN6.def
CDAP3.def
cdba4.def
cfak7.DEF
cmai3.def
cmai7.def
cmai9.def
cmba0.def
CNAB0.def
CNAB1.def
cqab1.def
crai8.def
CRAIA.def
CRAIB.def
CRAIC.def
craj0.DEF
ctbae.def
cvae6.DEF
cvae7.DEF
CVAF1.def
cvba0.DEF
cvba2.DEF
d9s.DEF
DA1.def
GVAKA.def
gvakb.def
gufa.def
gufb.def
gufc.DEF
gure.def
hug02.DEF
HWAD3.DEF
icy1.def
kmak6.def
kqad2.DEF
kraf5.def
LA3.def
LB3.DEF
m2y.def
maag4.DEF
MMAH0.def
MPAM1.def
mrad2.DEF
mrad3.DEF
odal1.DEF
ODAL1.def
OMAD3.def
OMAD4.def
OMAE1.def
OMAE2.def
p2y0.def
PCAG2.def
PCAG6.def
pf3.def
pybd3.DEF
pycl5.def
PYCL7.def
QAAC5.def
qbaa0.DEF
rbadb.def
rbaed.DEF
REAC3.def
reac4.DEF
RGAF2.def
rhagb.def
RQAD6.def
rtai0.DEF
rtai1.def
rtaj0.DEF
RVAF1.def
RVAF3.DEF
rvafa.DEF
rvafb.DEF
rvai1.DEF
RWAI2.def
ryae0.def
RYAF0.def
RYAF1.def
ryak1.DEF
RYBE2.def
RZAN0.def
RZAO1.def
rzao2.def
RZASA.def
rzaso.def
tauf0.DEF
VET1.DEF
way1.def
X2S2.def

Supported Datalogging Strategies:

1DEB_datalog.dlm
cbaza_datalog.dlm
da1_datalog.dlm
fun1_datalog.dlm
gufa_datalog.dlm
gufb_datalog.dlm
gufb_datalog_injector_track.dlm
gufb_dave.dlm
gufb_dave1.dlm
gufb_dave2.dlm
gufc_datalog.dlm
gure.dlm
krdc3_datalog.dlm
p2y0_datalog.dlm
ryaf1_datalog.dlm
(note: this list of DLMs has not been updated as recently as defs)

Binary Editor Supported Strategies

The best way to find out if your strategy is supported in Binary Editor is to download the software and install it!  Let it update itself.  It should download the latest and greatest strategies available.   You can also take a look at the strategies download page at EECAnalyzer.net for more information. Strategies are stored in “C:\Program Files\Binary Editor\DEF” in a unique folder for each definition.

Please note: datalogging and editing are controlled by the same definition file in BE.  You will have to load the definition along with a tune file to get an accurate idea of what exactly is supported.

Please also note: some definitions (that end in “.xls”) can be used by anyone with the software.  Other strategy files (those with the “.cry” extension) require additional registration with their author to use them. Derek Fenwick is a particularly excellent strategy author to look for.

Supported Strategies:

(This list last updated 2/15/11 – check http://www.eecaalyzer.net for an updated list)
AHACA (free)
AHACB (pay)
ANY1 (pay)
C1A1 (pay)
CAW0 (pay)
CBAZ0 (pay)
CBAZA (free AND pay)
CCAQA (pay)
CCAQE (pay)
CDAN4 (pay)
CDAN6 (pay)
CZAJL (pay)
CZAW0 (pay)
D1L1 (pay)
D4U1 (pay)
GSALC (pay)
GSALI (pay)
GUF1 (free)
GUFA (free)
GUFB (free)
GURE (free)
LA (free)
LA3 (free)
LB2 (free)
LHBL0 (pay)
LHBL1 (pay)
LHBL2 (pay)
LUX0 (free)
NVMG85 (pay)
PCAF5 (free)
PE (free)

Pops Racing Strategies:

Pops racing and Adam Marrer have started offering definitions for some of the popular EECIV and EECV strategies which are not publicly available otherwise. You can purchase them through Moates.net. Almost all of the 1996-2004 Mustang GT, Cobra, and Lightning strategies are covered here. As of the time of writing (2/15/11) these strategies are offered:
AGANN
AGANF
AHACA
C3P3/C3P2/ICY1
CBAZA
CDAN3
CDAN4
CRAI8
CRAJ0
CVAE6
CVAE7
CVAF1
CVBA0
CZAJL
FBFG2
FBGI0
MRAD2
MRAD3
OMAD3
OMAD4
OMAE1
RTAJ0
RVAF1
RVAFA
RVAFB
RYAF0
RYAF1
RYAK1
RYBE2
TAUF0

TunerPro / TunerPro RT Supported Strategies

One way to find out if your strategy is supported by TunerPro / TunerPro RT is to look at the list of supported definitions.  TunerPro supports the QuarterHorse as of version 5.0 which has been released as of the time of writing (February 2011) but QH and strategy support lags considerably behind EEC Editor and Binary Editor.  There is extremely solid support for GUFB (A9L / Fox body) and CBAZA (T4M0 / J4J1 / 94-95 Mustang). You can download the TPRT5 specific files here.

Australian EEC Support list

Tuner Pro seems to be the weapon of choice for most Australian EECs.  You can get more info and an updated list of supported cars, box codes and strategies here:

Australian EECs : http://www.tiperformance.com.au/technical.html

Ford: Box code – strategy – vehicle cross reference

This page is intended to help people who have looked here to figure out if there is support for their vehicle.

Each ECM has a 3 or 4 digit processor code that uniquely identifies it.  You can tell what strategy a ECM uses from its box code or from looking at a dump of a stock program from that ECM.  “Strategy” is Ford’s lingo for a program to run a vehicle. (or operating system)  Each strategy can have multiple calibrations for different engines.  Sometimes even V6 and V8 engines will use the same strategy!

If you are wondering if your strategy is supported, take a look at the Supported Strategies guide.

This list will grow over time.  If you don’t see your vehicle listed here, email support@moates.net

A9L = GUFB (88-93 “Fox body” V8 mustang 5-speed)

A9P = GUF1 (88-93 “Fox body” V8 mustang auto)

T4M0 = CBAZA (94-95 SN95mustang  5.0 V8)

LLX4 = CDAN4 (96-97 Cobra 4.6L 32v)

PTP2 = FBFG2 (04 Mustang GT)

RCX5 = CDAN4 (97 Tbird 3.8L v6)

SLL4 = CTBAE (96 5.0 explorer ??? )

LKT3 = ODAJ0 (02 F150 4×4 auto)

SCI1 = ODAG0 (02 F150 4×4 manual)

NMI1= ODAG0 (02 F150 4×4 manual)

MIJ1 = ODAG0 (02 F150 4×4 manual)

KVF1 = ODAL1 (02 F150 4×4 manual)

CXN1 = MNAE1 (01 Lightning)

CUX1 = MRAD2 (01/02 Lightning)

CUX2 = MRAD3 (01/02 Lightning)

URB1 = TAUF0 (02/03 Lightning)

There is a handy Excel spreadsheet you may want to look at ( link ) that has a decent cross-reference.

Who uses our gear?

This page is being created so we have a place to keep track of all the people who are using our gear for various applications.  If you would like to be added or removed from here, please email support@moates.net or leave a comment.  Hit control-F to find keywords on this page as eventually we hope this grows to a very large list!

ECU Connections forum – mostly Bosch Motronic stuff.

DS-MAP – MAP sensor conversion for DSM ECUs, supports Ostrich

TunerPro RT – general purpose ROM editor that supports APU1, Ostrich, ALDU1 and most of our gear.  Useful for Nissan, Ford, GM, DSM, some Bosch Motronic (BMW, Porsche, VW, etc.) among others. (we sell this)

ThirdGen.org – forum dedicated to the 3rd gen camaro/firebird with a great Tuning section!

EFI Live – Supports our RoadRunner Emulator for OBD2 GM vehicles (we sell this)

Binary Editor – Supports our QuarterHorse emulator for 86-04 Ford vehicles (we sell this)

EEC Editor – Supports our QuarterHorse emulator for 86-04 Ford vehicles (we sell this)

TunerCat – supports APU1, ALDU1, Ostrich, etc. for OBD1 GM vehicles

Neptune – supports Demon, Ostrich, BURN2,  etc.  The premiere solution for tuning 92-01 distributor Hondas (we sell this)

eCtune – supports Demon, Ostrich, BURN2, Hondalog, etc.  Another great 92-01 distributor Honda solution

Crome – supports Demon, Ostrich, BURN2, Hondalog, etc.  an older and poorly maintained 92-01 distributor Honda solution

TurboEdit – supports Ostrich, Hondalog.  an old and finicky software package for 88-91 distributed Hondas

BRE – supports Ostrich, Hondalog.  an old and finicky software package primarily aimed at 89-91 Vtec hondas

Pgmfi.ORG – Home of the DIY Honda community.  Birthplace of CROME, TurboEdit, BRE and loosely affiliated with other softwares.  Still a great resource for Honda ECU tuning.

Nistune – supports Ostrich, dual Ostrich.  Nissan ROM tuning software, dealer version works with our hardware.  Programs made with Nistune work with our Nissan 2Chip adapter.

Tuning Porsche 944 turbo vehicles using TunerPro, Ostrich, SocketBooster (thanks Joshua)

Turbo Mopars using Ostrich2

RhinoTuning using Ostrich2 / BURN2/ etc. for tuning Suzuki Swift pre-OBD2 vehicles

Nissan Data Voice uses the Ostrich2 for realtime tuning for OBD1 Nissan vehicles

EmUtility: standalone emulator control

Introduction

Ever wish your favorite Moates emulator would work with your favorite ROM editor software that doesn’t have native support for our products?  EmUtility (from the author of TunerPro) allows you to use Moates emulators with any software that can spit out a binary (bin) or hexadecimal (hex) format file.  It supports the Ostrich1, Ostrich2, APU1 *and* RoadRunner!  It can even support more than one emulator connected to the same computer simultaneously. (this requires more than one instance of the program, one for each emu)

Installation

You can get EmUtility from the Utilities section of TunerPro.net

EmUtility may require additional files to be installed for it to work, specifically the Microsoft Visual C redistributable libraries, which  are also linked off the Utilities section of TunerPro.net

EmUtility does not come with an installer – it is shipped as a zip file with a single program file inside.  Unzip it to place where you will be able to easily find it, such as your desktop.  You can run it directly from the desktop and it will not make a “mess” because it is only one file.

Usage

EmUtility is pretty straightforward to use.

First, start the program.  You should see “Detecting Hardware… Ostrich 2.0 blah blah blah” for instance.  If you see “No Hardware Detected” check your cables and connections.  If you cannot get your hardware to detect, try looking at our USB Troubleshooting Guide.

After you have verified that your hardware has been detected properly, click the “…” next to “Input / Output File” to select a file to use.  (If you are going to read the contents of the emulator to a file, this can be a new file)

Next select an operation from the drop down box next to “Operation”  Valid operations include:

  • Read from emulator to file = creates a new file on your computer with the contents of emulator RAM.  Must specify a filename, how much memory you want read (size), if you want to use a non-standard start address (File Start Address)  and if you want to use large RAM support (required for files > 512kbit / 64k byte)
  • Write from file to emulator = updates the RAM on your emulator with the contents of a file on your computer.  Must specify a filename  and if you want to use large RAM support (required for files > 512kbit / 64k byte).  File size and start address will be automatically selected for you and will be correct in most cases where your file is the same size as the chip you are trying to emulate.  (i.e. 32k byte file for 27C256 chip)
  • Verify emulator RAM with file = compares the contents of the Emulator’s RAM with a file on your computer to see if they match.  Must specify a filename  and if you want to use large RAM support (required for files > 512kbit / 64k byte).  File size and start address will be automatically selected for you and will be correct in most cases where your file is the same size as the chip you are trying to emulate.  (i.e. 32k byte file for 27C256 chip)
  • Monitor File for changes and upload = this operation monitors a file for changes and uploads the changes to your emulator as they happen. ust specify a filename  and if you want to use large RAM support (required for files > 512kbit / 64k byte).  File size and start address will be automatically selected for you and will be correct in most cases where your file is the same size as the chip you are trying to emulate.  (i.e. 32k byte file for 27C256 chip)

After you have selected and configued the operation you desire, click “Execute” to perform it.  To cancel a monitoring+upload session or other op, click “Cancel Op”

That’s it!

Suggested Uses

If you have a program that can spit out bin files but it does not support Moates hardware:

  1. Start EmUtility
  2. Pick “Write from file to Emulator”
  3. Point EmUtility at the file you are working with
  4. Click “Execute” to load the initial file
  5. Change the operation to “Monitor file for changes and upload”
  6. Click “Execute” to begin monitoring the file for changes
  7. Leave EmUtility running in the background.  Go back to your editing application.  Make changes and save the file (with the same filename).  As you save changes to the file, EmUtility will copy them to your emulator almost instantly!

Nissan 16 bit applications with TunerPro 4.x: (using a daughterboard like our Nissan 20×2 that takes two identical chips and two Ostrich 2.0 emulators)

  1. Plug in ONE Ostrich and follow the directions immediately above to set up monitoring for an application that does not support Moates hardware.
  2. Leave EmUtility running and connect the second Ostrich.
  3. Start TunerPro.  It should detect your second Ostrich.
  4. Start your emulation session in TunerPro.
  5. Tune away.  TunerPro will update one Ostrich, EmUtility will update the other

(Note: TunerPro 5.x supports dual Ostrich mode which is easier to set up than this)

16 bit Nissan applications such as 925style.com’s ROM  EDITOR (using a daughterboard like our Nissan 20×2 that takes two identical chips and two Ostrich 2.0 emulators)

  1. Plug in ONE Ostrich and follow the first set of directions above to set up monitoring for an application that does not support Moates hardware.
  2. Leave EmUtility running and connect the second Ostrich.
  3. Start a SECOND COPY of EmUtility.  It should detect your second Ostrich.
  4. Repeat the instructions for loading a binary and starting monitoring in the second EmUtility session
  5. Tune away!  As you save changes to the file, each instance of EmUtility will update one emulator.

Using the RoadRunner as a general purpose 16 bit emulator with software that does not have native support (i.e. Bosch Motronic 28Fxxx):

  1. Start EmUtility
  2. Pick “Write from file to Emulator”
  3. Point EmUtility at the file you are working with
  4. Click “Execute” to load the initial file
  5. Change the operation to “Monitor file for changes and upload”
  6. Click “Execute” to begin monitoring the file for changes
  7. Leave EmUtility running in the background.  Go back to your editing application.  Make changes and save the file (with the same filename).  As you save changes to the file, EmUtility will copy them to your emulator almost instantly!