G4 – Moates Support https://support.moates.net Where all your DIY EFI questions are answered! Mon, 21 Nov 2022 13:10:17 +0000 en-US hourly 1 https://wordpress.org/?v=4.5.3 Programming Chips Using Offsets https://support.moates.net/programming-chips-using-offsets/ https://support.moates.net/programming-chips-using-offsets/#respond Tue, 06 Apr 2010 03:04:49 +0000 http://support.moates.net/?p=775 Introduction

If you’re completely new to burning chips, you may want to take a look at the Beginners’ Guide before reading the rest of this article.  You will probably still need to read this guide in order to choose the correct programming parameters unless you’re in the situation where you’re programming a chip that is the exact same size as the chip you are replacing.  Programming chips with offsets comes into play in two situations:

  1. If the chip you are programming is of a larger capacity than the binary file you are putting on it, you need to use an offset to ensure the tune ends up in the right spot on the chip.
  2. Switching adapters which hold multiple programs require the use of offsets to fit multiple programs on a single chip for a switching adapter.

Both of these cases will be covered in this article.

Chip Offsets With a Single Tune:

We’re going to assume you have either TunerPro or Flash n Burn open at this point and the chip physically oriented correctly.  If you need help with this, look at the Beginners’ Guide before continuing.  We will be selecting the correct buffer and chip addressing to ensure the chip is burned properly and can be used.

When in the software:

  1. Select the type of chip you’ll be programming from the drop-down menu. This will likely be either the AT29C256, 27SF512, AT90F040 or Moates J3 adapter (F3/F3v2).
  2. Pick the ‘Load file to buffer’ option, and navigate to the file you want programmed on the chip. Select it, and it will be loaded to memory on the PC. Take note of the file size indicated in the message window. (You can typically “hover” over the filename before opening it and Windows will pop up an information box iwth the file size)  It will likely be one of five sizes: 4k, 16k, 32k, 56k or 64k bytes.
    • The file you have loaded will determine your buffer addressing (start/end)
    • 4k byte = 0000/0FFF
    • 16k byte = 0000/3FFF
    • 32k byte = 0000/7FFF
    • 56k byte = 0000/DFFF
    • 64k byte = 0000/FFFF
  3. In the top right part of the window you will see the Chip Addressing offset values that need to be changed. The buffer addressing along with the chip size will determine what offsets you need to use. (Flash n Burn usually automatically selects sane offsets based on your chip type and file size in order to place your buffer at the end of the chip, where it usually belongs.)
    The following table summarizes what offsets you need to use depending on chip used and file size:

    File Size
    Chip
    Buffer Start -> End
    Chip Start -> End
    4k (4096)
    AT29C256
    000000 -> 000FFF
    007000 -> 007FFF
    16k (16384)
    AT29C256
    000000 -> 003FFF
    004000 -> 007FFF
    32k (32768)
    AT29C256
    000000 -> 007FFF
    000000 -> 007FFF
    4k (4096)
    27SF512
    000000 -> 000FFF
    00F000 -> 00FFFF
    16k (16384)
    27SF512
    000000 -> 003FFF
    00C000 -> 00FFFF
    32k (32768)
    27SF512
    000000 -> 007FFF
    008000 -> 00FFFF
    56k (57344)
    27SF512
    000000 -> 00DFFF
    002000 -> 00FFFF
    64k (65536)
    27SF512
    000000 -> 00FFFF
    000000 -> 00FFFF
    32k (32768 EECIV)
    F3/F3v2
    000000 -> 007FFF
    032000 -> 039FFF
    56k (57344 EECIV)
    F3/F3v2
    000000 -> 00DFFF
    032000 -> 03FFFF
    64k (65536 EECIV)
    F3/F3v2
    000000 -> 00FFFF
    032000 -> 03FFFF
    216k or 224k (EECV)
    F3/F3v2
    “bank” format: non-linear!
    convert to 256k!
    256k (EECV)
    F3/F3v2
    000000 -> 03FFFF
    000000 -> 03FFFF

    While the correct values are often selected, you can manually enter them.  For a single-tune single-chip scenario, you generally want the buffer (or file content) to be placed at the ‘end’ of the chip. The notable exceptions to this rule are 32k EECIV Ford tunes (which need to start at 0x32000 and end before the end of the chip) and 216k/224k Ford EECV bins (which are not in linear memory format and need converted to 256k before programming).

    check_settings
    To do this manually:

    • Ensure Buffer Addresses are correct for the file size you have loaded.
    • Adjust the Chip Addressing start value and end value until the end value is the maximum value for the chip AND buffer address values are correct.
    • A short list of common chip addressing settings:
      • 64k bin: 000000 start 00FFFF end ( SST27SF512 chip )
      • 32k bin: 008000 start 00FFFF end ( SST27SF512 chip )
      • 16k bin: 00C000 start 00FFFF end ( SST27SF512 chip )
      • 4k bin: 00F000 start 00FFFF end ( SST27SF512 chip )
      • 56k Ford EECIV bin: 032000 start 03FFFF end ( Ford F3 chip )
      • 256k Ford EECV bin: 000000 start 03FFFF end ( Ford F3 chip )
      • 112k Ford EECV bin: SPECIAL need other software ( Ford F3 chip )
      • 216k Ford EECV bin: SPECIAL need other software ( Ford F3 chip )
      • BEB files CANNOT be programmed with FnB / TP.  Must program using Binary Editor
      • eBIN file CANNOT be programmed
  4. Once you are satisfied with the offsets, perform a normal Erase/Blank/Program/Verify cycle!  Consult the Beginners’ Guide for more information.

Using Switching Adapters:

Using our switching adapters (G2X, G3, GX, TwoTimer, F3, F3v2,F8) requires programming chips using offsets of making “stacked” bin files.  Switching adapters use chips that are larger than an ECU requires, allowing the extra space to be used for multiple programs.  The “extra” space gets divided up into chunks, each of which can store an individual tune.  There are two approaches to creating proper chips for use with switching adapters, both equally valid:

  1. Lump all tune files together on your PC into one bin file “stacked” which is the same size as the chip, program chip at once.
    • The “Bin Stacker/splitter” function in TunerPro can be used to prepare a single file from a group of tunes.  (You can also use a hex editor or other tool)
    • This “stacked” file contains all the tunes and can then be programmed like a “normal” file using TunerPro, Flash n Burn, etc.
    • “Normal” programming cycle: Erase, Blank check, Load tune/buffer, Program chip, Verify.
    • Entire chip gets programmed at once, all tunes for the ECU get programmed on the chip in one operation as part of the “stacked” file.
    • Requires preparation of new “stacked” file and reprogramming of entire chip if any individual tune changes.
  2. Program the chip multiple times, once for each tune, different small selected area of chip Program/Verify cycle instead of whole chip.
    • Instead of relying on a program to create a “stacked” file, knowledge of chip addressing is used to place tunes at correct places within a chip.
    • Programming cycle changes slightly: Erase, Blank check happens at very beginning of cycle ONLY ONCE.  Does NOT happen before every Program/Verify operation, like normal.
    • Erase/Blank is followed by multiple Program, Verify operations.  Each operation is for one tune.  Each operation will have different start/end addresses which are a portion of the chip.
    • Does NOT require preparing any special files in advance – uses the same bin files which would be used for single-tune programming.
    • If you want to chance a tune which is already programmed, the entire chip must be erased and all tunes individually reprogrammed.

As a rule of thumb, tunes start at the end of the chip and count down.  i.e. “Tune 0” is in the highest addresses on the chip, or the top slot in a stacked bin.  “Tune 1” will be the next lower slot.  Some adapters have chips which can hold more tunes than there are address lines for switching.

Each switching adapter we sell has different numbers of available slots, slot sizes and corresponding chip addresses start/end:

  • G2X: 27SF512 chip (00000/0FFFF), 16x 32kbit/4kbyte slots on chip:
    1. F000/FFFF
    2. E000/EFFF
    3. D000/DFFF
    4. C000/CFFF
    5. B000/BFFF
    6. A000/AFFF
    7. 9000/9FFF
    8. 8000/8FFF
  • G3: 29F040 chip (000000 / 07FFFFF), 16x variable size slots, Ex remote required, addressing varies according to settings on adapter
  • GX: 29F040 chip (000000 / 07FFFFF), 16x 64k slots, Ex remote required, addressing varies according to size of base file.
    • There are 16 slots on the chip.  Each slot is 64k ( 0x0FFFF) in size.
    • Tunes smaller than 64k typically need to be top-justified so that they END at the end of each window
    • When using the Ex remote (or no switcher – floating switch inputs) slot “0” will be at the end of the chip and bigger numbers on the Ex remote will mean slots closer to the beginning (0x000000) of the chip.
  • TwoTimer: 27SF512 (00000/0FFFF), 2x 256kbit/32kbyte slots, idles in “high position”
    1. 8000/FFFF
    2. 0000/7FFF
  • F3 (version one – switch pin and 2 tunes): special case.  Cannot program entire device at once, stacking NOT possible.  Program chip twice, manually change state of switching pin during programming. Note: “Erase chip” function does NOT erase whole chip, only erases the “bank” selected by the jumper
  • F3v2 (version two – 4 pin connector and dial switch, 8 tunes): special case.  Cannot program entire device at once, stacking NOT possible.  Program chip multiple times, manually change state of switch during programming to select different slots. Note: “Erase chip” function does NOT erase whole chip, only erases the “bank” selected by the switch
  • F8: special case.  Use F8 device utility to prepare and program tunes.
]]>
https://support.moates.net/programming-chips-using-offsets/feed/ 0
Discounts for Shops, Resellers, and Group Buys https://support.moates.net/discounts-for-shops-resellers-and-group-buys/ https://support.moates.net/discounts-for-shops-resellers-and-group-buys/#respond Sun, 04 Apr 2010 20:20:15 +0000 http://support.moates.net/?p=757 Shops and Resellers:

If you are interested in purchasing Moates.Net products in bulk, or would like to be a reseller of our products, the following discount structure is available to you:

10% off for 10 – 19 pieces more of a given item
15% off for 20 – 49
20% off for 50 – 99 and
25% off for 100+ units

NOTE!
This discount can be applied retroactively as well for a 12 month rolling total. For instance, if you buy 5 units at regular price of $20 each and then later on purchase 6 more units in a 12 month period at $20 each, then a discount will be applied to the total so you’ll get a partial refund of 10% on all 11 units, or $22.

Furthermore, if you subsequently purchase 12 more units, you will be eligible for the 15% price break on all 23 units, giving you an additional $47 off. The total net discount on ALL same items purchased in a 12 month rolling period would effectively be 15%. We chose a 12 month rolling time period instead of a calendar year so you won’t lose your discount if you buy in December and then more in January.

This may seem confusing, and it does add to order processing complexity on our side. However, it is designed to lower the risk level for entry-level shops and resellers. You don’t need a big buy-in, since the retroactive discount structure takes care of you!

This discount structure is not valid for small incremental orders (one part here, one part there), and does not apply to individual drop shipments. Instead, it is limited to quantity orders of 3 or more pieces at a time going to the same destination. So if you buy 3 units and 8 units, then you get the 10% discount on all 11. If you then buy 1 separate unit separately, the 1 separate unit doesn’t get the discount and doesn’t count toward the total accumulation for bulk retroactive discount.The reason for this is that the 1 piece at a time approach still requires all of the administrative order processing burden on our side, and part of the reason for bulk discounts is that it is easier for us to ship quantities of units than shipping them individually.

Group buys:

Pre-arranged group buys are available. The same normal discount structure as described for bulk discounts applies based on the number of participants, but the minimum individual order quantity of 3 isn’t required.

Any purchase made on the website or over the phone under a group buy situation should be CLEARY INDICATED, preferably in the comments section of the order. That way we know what to do with it.

For example, one group buy coordinator will contact us ahead of time and initiate the group buy period (up to two weeks in duration). We will agree on the close-out date for the group purchase.

If the coordinator wants to have all of the units shipped to them and then distribute them to the individual purchasers, then it will be handled no differently than a standard bulk discount situation.

If the buyers decide to pay for the units individually at our webstore and have them shipped separately to each buyer, then that is also fine. In this case, full price will be charged initially. At the close of the group buy, a discount will be applied as a partial refund to each participant separately.

The total discount will depend on the total number of participants. So for 10-19 it’d be 10% and for 20-49 it’ll be 15%. We usually don’t know how many participants are involved until the close of the group buy period, so that’s why the partial refund / discount is delayed until that time.

Hope this helps!

]]>
https://support.moates.net/discounts-for-shops-resellers-and-group-buys/feed/ 0
Moates.net Philosophy (READ ME) https://support.moates.net/moatesnet-philosophy-read-me/ https://support.moates.net/moatesnet-philosophy-read-me/#respond Wed, 10 Feb 2010 02:51:08 +0000 http://support.moates.net/?p=650 Our Philosophy:

We are a small technically-oriented outfit that focuses on product development not fancy packaging, phone support, and marketing.  We bring you high-quality, value-priced products aimed at self-starters willing to read documentation, learn independently and most importantly try things on their own without someone providing guidance every step of the way.

About Moates.Net and our products:

It is important for you, our users, to understand what we expect of you and what we aim for in our products.  Our philosophy at Moates.Net is simple: we want to bring enthusiasts the highest quality products for tuning their cars at a reasonable price.  What we mean by “enthusiasts” is simple: people who are motivated to learn about tuning their car.  It doesn’t matter whether you’re working on your own car or work for a shop – if you’re willing to learn about tuning a car, you are part of our target audience.

Our objective isn’t to make a fortune – there are plenty of companies out there that sell comparable products for a whole lot more.  With that said, there are trade offs in our approach.  Our products frequently do not even have boxes, let alone fancy packaging like other vendors.  Our products do not ship with much printed instructions – instead our documentation can be found online.  (Like this support site!)  We devote most of our resources to product development, leaving limited resources for intensive support.  We have chosen instead to provide inexpensive products with fewer frills aimed at a more educated user.

What We Expect of You

Here at Moates.Net, education and teaching are things we value highly.   We don’t expect everyone to be born knowing how to tune a car or use our products.  We expect anyone who purchases our products to be willing to READ and learn independently. We will help you if you run into trouble, but we expect you to READ documentation and try to do it on your own first.  We base a lot of the technical documentation and guides we develop on the questions that you ask.  (If you have any suggestions for additional guide topics, we are always willing to listen.)  Many of our activities, such as this support site and our YouTube channel with its video tutorials, are aimed at providing resources to further educate our users.

If it doesn’t work out…

Worst case, we have a no questions asked money back guarantee for any parts returned in the condition they were received.  (We can’t issue a full refund for items damaged through neglect, negligence or abuse.)  We hope this isn’t how things end, but you’re only out the cost of shipping and the time you spent trying to figure it out.

]]>
https://support.moates.net/moatesnet-philosophy-read-me/feed/ 0
GM 86-95 OBD1 Guide (READ ME) https://support.moates.net/gm-86-95-obd1-guide-read-me/ https://support.moates.net/gm-86-95-obd1-guide-read-me/#comments Thu, 07 May 2009 17:20:10 +0000 http://support.moates.net/?p=552 (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 #
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.

FreeScan is a free datalogger that works with some GM vehicles. ( link )

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.

]]>
https://support.moates.net/gm-86-95-obd1-guide-read-me/feed/ 1
TunerPro RT https://support.moates.net/tunerpro-rt/ https://support.moates.net/tunerpro-rt/#respond Thu, 18 Sep 2008 03:41:35 +0000 http://support.moates.net/?p=144 Tuner Pro is a piece of software written by Mark Mansur that is compatible with a great number of vehicles and ECUs.

Download TunerPro here

Originally written to modify GM and Ford binaries, the uniqueness of TunerPro is its ability to have Definitions. While this adds a slight layer of complexity to the end user, the definition files (XDF) instruct TunerPro as to where tables and variables reside within the binary it is opening, allowing TunerPro to be compatible with virtually any binary.

Currently definitions are available for the following Vehicles at least as of 9/30/08, more being added regular (see http://www.tunerpro.net website for all the latest)::

General Motors

Mask ID
ECM
Bin Definition
ALDL Definition
Application
$6E
1227165
6E.xdf
1227165_6E.ads
1989 LB9/L98 F & Y Body (Bins)
$8D
1227730
Super_8dm2.ecu
1227730_8D.ads
90-91 LB9/L98 F-Body
$32
1227165
32.ecu
1227165_160.ads
86 5.0/5.7 F & Y Body
$32B
1227165
32Bv001.ecu
1227165_160.ads
87-88 5.0/5.7 F & Y Body
$42
1227747
7747-mine.ecu
1227747_42.ads
1987-1991 5.0 Truck, Etc
$31
16197427/16156930
TBD
95 C/K Truck/Van 5.7/7.4
$5D
1227808
TBD
88 Australian Holden
$12
16183082
TBD
’93+ Australian Holden V8
$DA3
16159278
93 LT1
$0D
16197427
0D_v1_02.xdf
0D.ads
94-95 C/K 4.3L, 5.7L & 7.4L
$83
16176424/16195699
83HoldenVS_V8_v2.xdf
TBD
96 Holden VS V8
$61
1228746
61v2.xdf
TBD
89-92 F & B Body LO3 & LO5 – Maintained by Jon Prevost
$E6
16168625
E6.xdf
93 5.7L L05 K Truck
$8F
1227727/1227730
8F.xdf 8F_v2.xdf
89-90 LG5 3100 Turbo.ads
89-90 3.1L Turbo (TGP)
$31T
1227148
TBD
1227148TBuick.ads
87-90 3.8L Turbo (LC2) Buick
$1FA
16196387
TBD
1FA.ads
94-95 3.1L W-body (Grand Prix, Monte,…)

Ford (requires v4.13 or higher)

ID
Bin Definition
Last Updated
Application
T23B
T23B.xdf
5/29/08

8UA – 88 2.3l Thunderbird auto
LB3 – 87-88 2.3l Thunderbird auto
LA3 – 88 2.3l Thunderbird 5sp

Definition maintained by Dex

GUFA
GUFA.xdf
4/12/08

8LD – ’88 – ’93 5.0l Mustangs
A9S – ’88 – ’93 5.0l Mustangs

Definition maintained by Dex

GUFB (A9L)
GUFB.xdf
4/12/08

A9L – 88-92 Mustang 5.0L
A9M – ’89 – ’93 5.0l Mustang
A3M – 93 5.0 Mustang
A3M1 – 93 5.0 Mustang
A3M2 – 93 5.0 Mustang
D3D1 – 89-93 5.0 Mustang
S0Z – 89-93 5.0 Mustang
X3Z – 93 5.0 Cobra

Definition maintained by Dex

GUF1
GUF1.xdf
4/12/08
A9P – ’89 – ’92 5.0l Mustang auto
A9T – ’89 – ’93 5.0l Mustang auto
C3W – ’93 5.0l Mustang auto
C3W1 – ’93 5.0l Mustang auto
8LF – ’88 – ’93 5.0l CA Mustang auto

Definition maintained by Dex
CDAN4
CDAN4.xdf
1/23/06

96-97 4.6L Mustang, T-Bird, Crown Vic
96-97 3.8L Mustang

NOTE: This XDF is for “full” binaries. Only 256k 0189 EEC-V files should be used.

CRAJ0
CRAJ0.xdf
8/15/06
LAQ2 – 98 3.8l Mustang
AOL2 – 98 4.6l 4V Mustang
AOL3 – 98 4.6l 4V Mustang
CBAZA
CBAZA.xdf
10/1/07

L4C1 – 94-95 5.0l Mustang 5sp export market
J4J1 – 94-95 5.0l Mustang Cobra 5sp
T4M0 – 94-95 5.0l Mustang 5sp
U4P0 – 94-95 5.0l Mustang auto
W4H0 – 94-95 5.0l Mustang auto
ZA0 – 95 5.8 Mustang Cobra R 5sp
FCL0 – 95 5.0l Mustang auto Japan market
S4M1 – 5.0l auto

LUX0
LUX0.xdf
12/12/07
DA1 – ’87 Mustang 5.0L
DB1 – ’88 Mustang 5.0L
L8
IAW048_01.xdf
3/19/08
Sierra Sapphire 4wd Cosworth L8
L1
IAW045_01.xdf
3/19/08
Sierra 3 door Cosworth L1
L6
IAW045_06.xdf
3/19/08
Sierra Sapphire 2wd Cosworth L6
HWAD3
HWAD3.xdf
8/21/08
6DBD – 1998 Futura/GLI, 4.0L, auto
6DNB – 1998 GLI, 4.0L, auto
6TEE – 1998 XR6 Ghia, 4.0L, auto

May also work with:
6DAC – 1998, unknown, 4.0L, manual (HWMD3 strat.)
6DMA – 1997 XR6, 4.0L, auto (HWAC2 strat.)

(Requires 256KB bin with first 8KB to be null-padded)

N4AGB
N4AGB.xdf
8/26/08
4DBG – 1995 Futura/GLI, 4.0L, auto
4TEG – 1995 Futura/GLI, 4.0L, LPG

May also work with:
4TBD – 1994 Fairmont Ghia, 4.0L, auto (N4AG9 strat.)

(Requires 256KB bin with first 8KB to be null-padded)

Subaru (Requires v4.13 or higher)

ID
Bin Definition
Last Updated
Application
N/A
0405WRX.xdf
2/12/06
04-05 USDM WRX

Nissan

ID
Bin Definition
Last Updated
Application
B13/S13
B13RT.xdf
3/23/07
1996-1997 B13 w/ Realtime
Z32
Z32.xdf
8/29/06
90-95 300ZX (8-bit ECU only)

Porsche (Motronic)

ID
Bin Definition
Last Updated
Application
N/A
87Porsche911-4KChip.xdf
6/27/08
’87 911 w/ 4KB chip (Bins)
N/A
6/27/08
’84-’86 911 w/ 2KB or 4KB chip (Bins)

DSM (Eagle/Mitsubishi)

ID
Bin Definition
Last Updated
Application
1G E931
e931stk.xdf
9/10/06
1991 Talon AWD (16KB bin)

Renault

ID
Bin Definition
Last Updated
Application
Fenix 1B
R21T_720D.xdf
8/19/08
Renault 21 2.0L Turbo, 8KB ROM (27C64) (Bins)
Fenix 3A
Clio16S_7494.xdf
8/19/08
Renault Clio 16V w/o O2 Sensor, 32KB ROM (27C256)
Fenix 3B
Clio16S_7852.xdf
9/02/08
Renault Clio 16V with O2 Sensor, 32KB ROM (27C256) (Bins)
Fenix 3
ClioWilliams_7881.xdf
9/02/08
Renault Clio Williams 2.0 16v

Registration

You will be emailed a key file to register to the address provided with your order.  In order to do this, we need your name, address, phone number and CORRECT EMAIL.  Make sure you can check the email address you provide with your order as this is where we will send your key.  Be sure to check any spam filters.  We do not need a key or any other information from you for TunerPro RT – we simply need a valid email address.

]]>
https://support.moates.net/tunerpro-rt/feed/ 0