The Burn1 is a revolutionary device that was designed with the automotive enthusiast in mind. it supports chips used in our products aimed at ECUs/ECMs from the late 80s and early 90s.

The BURN1 can:

• WRITE SST 27SF512, ATMEL AT29C256 and 29F040 chips.
• READ but NOT WRITE 2732A, 27C128, 27C256 chips (and most other 24/28 pin EPROMs/EEPROMs that can replace one of these chips).
• With a F2A adapter, it can WRITE our F3 EECIV/EECV chip modules.
• With a F2E adapter, READ factory Ford ECMs.
• with a HDR1 adapter, READ factory GM TPI ECMs that would use a G1 chip adapter .

As you can see, it is designed to comprehensively work with our products but it is NOT a general purpose EPROM programmer.  If you require programming chips outside these specifications, you probably should look at another product.

Before the Burn1 was developed, there were only a handful of chip burners known to be compatible with these chips. These burners were usually not cost-effective, used outdated PC interfaces like a parallel Printer port. They also required external power supplies, so forget burning on the fly. Examples include the $160 Pocket Programmer II.

The Burn1 was revolutionary with its simple USB interface that provided all power to the unit. An internal DC voltage step-up circuit is used to provide the high erase voltage required on certain chips.

The latest generation of the Burn1 is the Burn2. It has the same same command set and features as the Burn1 but has a smaller size.

How to Buy

This product has been replace with the Burn2. Please visit the Burn2′s page on our webstore here

The Burn2

The Burn2 has the same features as the Burn1, only smaller and more compact.

The Burn2 is a revolutionary device that was designed with the automotive enthusiast in mind. it supports chips used in our products aimed at ECUs/ECMs from the late 80s and early 90s.

The BURN2 can:

• WRITE SST 27SF512, ATMEL AT29C256 and 29F040 chips.
• READ but NOT WRITE 2732A, 27C128, 27C256 chips (and most other 24/28 pin EPROMs/EEPROMs that can replace one of these chips).
• With a F2A adapter, it can WRITE our F3 EECIV/EECV chip modules.
• With a F2E adapter, READ factory Ford ECMs.
• with a HDR1 adapter, READ factory GM TPI ECMs that would use a G1 chip adapter .

As you can see, it is designed to comprehensively work with our products but it is NOT a general purpose EPROM programmer.  If you require programming chips outside these specifications, you probably should look at another product.

How to Buy

Visit this item’s page in our online store here

Software

This device can be used directly from TunerPro RT, EEC Editor, Binary Editor software packages as well as the Flash-n-Burn dedicated programmer software.

About the QuarterHorse

Firmware Updates

• The new version of Binary Editor 2010 requires QH firmware 1.6 or higher.Most firmware upgrades are bugfixes of one variety or another.  If you aren’t having trouble, chances are the bugs do not affect you.
• Most bugs affected the QH when operating in modes 3 and 4 (EECV)
• The latest firmware revision as of 2/11/10 (version 1.6) allows you to read the stock program from an ECM using the QuarterHorse.

Program Switching with QuarterHorse

Here are pictures which detail how the rotary switch is installed on the QuarterHorse. The kit comes with a length of no-clean solder, and it is very easy. Follow the pictures for guidance, and remember, this is ONLY for EEC-IV and not post-1995 EEC-V.

First, look at the connector part you received. It may or may not have had one of the 4 pins removed. If not, pull it out so that it is as shown.

Go ahead and use the no-clean solder that was supplied. Get one spot on the QH connector tinned up like it shows in the picture.
Now, hold the modified 4 (now 3) pin connector in place as shown, re-heating the solder so that the two pieces can be bonded together in the correct position.

Now, come in with the solder on the other 2 joints. Use a little extra for strength, but don’t go overboard. Re-heat and add solder to the first joint you started with here to ensure good connection.

Soldering work is now complete, so check fitment of the cable and look for straightness and orientation. Use the photo below for reference.

Here’s another angle showing solder joint details.

These are most of the parts (pin header shown unmodified) that come with the switch kit. Knob is also included (shown in 2nd picture below).

Here is what the completed switch / QH / knob assembly should look like:

This is a pretty simple installation. It basically overrides the BS0/BS3 lines (if you’re familiar with this terminology) at the EEC connector. Therefore, to repeat, this is NOT to be used on EEC-V applications.

NOTE: The QuarterHorse must be configured to use MODE 1 or the switch will NOT WORK.  As of the time of writing (Apr 2011) Binary Editor is the only software that supports Mode switching which means it is also the ONLY software that will currently work with the switcher module.

EECEditor is a ROM Editor for many Ford vehicles.

John Cui

CROME is a ROM-Editor written primarily for OBD I Honda ECUs. A Pro version is available for $149 which unlocks a hidden data-logging feature.

CROME works natively with the following Moates hardware:

• Ostrich (both 1.0 and 2.0)
• Burn1
• Burn2
• HuLog (both Xtreme HuLog and Original HuLog)
• HondaLog

[youtube]http://www.youtube.com/watch?v=BKpLKHEwWXY[/youtube]

The RoadRunner works exclusively with EFILive, which is compatible with all LS1 PCMs.

The 2Timer is a great tool used by anyone who needs multiple fuel maps one one chip. Good examples are those who run Nitrous, or typically run two different types of fuel. (I.E. Race Gas map vs. Pump Gas map)

Creating a BIN for the 2Timer

We get this question a lot, so we have decided to do a write-up to help people out. Let’s assume you have an easy situation and you are simply trying to create a Race Gas tune for your vehicle. We are also going to assume that you have both of your original BIN files in an easily accessible folder on your computer. For the sake of simplicity, lets say that both of these tunes were produced with CROME. So you should have 2 files, each of size 32,768 bytes, or 32KB for short. You need to combine these files into one 64KB file.

Unfortunately, CROME does not have this capability. However TunerPro does.

Download it here.

There is a standalone module within TunerPro called the Bin Stacker.

Tools->Bin Stacker/Splitter

Within the Bin Stacker there are some rather Cryptic options:

Bin Size: This is the size of the tune. Typically 32KB (for Hondas)

Chip Size: This is the capacity of the chip. 64KB (assuming your using a SST 27SF512)

Block Size: This is useful if you are putting two 16KB tunes on a 64K chip, but you need the second 16KB tune to start at the halfway point of the chip. Set the block size to 32KB and it will start writing the second tune at the 32KB mark. If you’re doing this on a Honda, select 32KB.

For the 2Timer, Pos 1 is the default, and Pos 0 is the map that gets selected when you ground the wire coming out of the 2Timer unit.

Using the Browse button you will be able to put your two tunes in their appropriate positions, and by clicking Stack you will be able to create 1 file that you can burn to a chip.

Using the Flash N Burn software you will be able to burn this file to your SST 27SF512 chip.

Alternate Procedure

When using the 2Timer to switch between two 32k programs, you will want to program the chip directly (not through the 2Timer). Assuming you are using the 27SF512 chip, you can program two positions.

1. First, insert the 27SF512 chip into the BURN1 programmer and erase it followed by a blank check.
2. Load the first program from file to the buffer of the FlashBurn program.
3. For the first program (switch open to select), program the chip using chip addressing of 8000-FFFF, buffer addressing of 0000-7FFF. After the programming cycle, perform a verify step.
4. Load the second program from file to the buffer.
5. For the second program (switch wire grounded), use chip addressing 0000-7FFF and the same buffer addressing as before. Again, verify after this step.  DO NOT ERASE THE CHIP BEFORE PROGRAMMING A SECOND TIME
6. That’s it! You can switch the wire to ground to select the ‘lower’ chip addressing location.

You may also want to consult the article on programming chips with offsets found here.

How to Buy

To purchase the 2Timer, please visit this item in our Online Store here

Flash & Burn Screen Shot

Download Flash & Burn here.

Flash & Burn is a software package used with the Burn1 and Burn2 EEPROM burners, as well as the Autoprom (APU1).

Note, many tuning software packages (like CROME and Hondata) can interface with these burners directly making this software not necessary.

The meanest emulator known to man.

The release of the Ostrich 2.0 was the marking point for the next generation of Moates products. Along with a 75% size reduction, the Ostrich 2.0 also boasts many firmware advances. The Ostrich 2.0 connects to the host computer with a baud rate of 921,600bps, which is the fastest bit rate supported by standard RS-232.

In English, this means uploads, download and verifies happen in less than 2 seconds for most ROMs.

There are also some new features for developers available on the Ostrich. Features like ROM tracing, and window tracing allow developers to keep track of what addresses are being access within specific regions of the ROM. This is helpful for reverse engineering roms, and can also aid in datalogging ECUs with limited datalogging capability.

The following software packages are known to be compatible with the Ostrich 2.0:

• CROME

• Hondata

• Neptune

• eCtune

• BRE

• TurboEdit

• TunerPro

And many more…

To purchase the Ostrich 2.0, please see this item in our Online Store here

Supported Targets – 24, 28, 32 pin 8 bit ROMs

The Ostrich is a general purpose emulator.  It can be used to emulate up to a 4 megabit ***8 bit*** EPROM.  It cannot be used to emulate 16 bit ROMs like the 28Fxxx.  The Ostrich 2.0  is available with DIP28, DIP32 cables.  The SocketBooster 1.0 is used with 24 pin applications.

• 27C32 (TBI GMs, Old Bosch Motronic) = 28 pin emulation cable, Socket Booster
• 27C64 (misc ECMs) = 28 pin emulation cable, Socket Booster
• 27C128 (misc ECUs) = 28 pin emulation cable
• 27C256 (misc ECUs) = 28 pin emulation cable
• 27C512 (misc ECUs = 28 pin emulation cable
• 27C010 (?) = 32 pin emulation cable
• 29F040 (?) = 32 pin emulation cable

In cases where you have a PLCC package chip, you CAN use the Ostrich 2.0 but you need a DIP->PLCC adapter.  We do NOT sell these.  Logical systems seem to sell suitable adapters.

The SocketBooster and the Ostrich 2.0

The SocketBooster is never required when using the Ostrich 1.0 but it is required for most 27C32-based applications when using an Ostrich 2.0.  You can think of it as a signal amplifier for the Ostrich 2.0.  In most applications, the Ostrich 2.0 can produce a strong enough signal on its own.  If your ECU acts like it has a bad chip or no chip installed when using the Ostrich but the same program works as a chip, this could be a sign that your application needs a SocketBooster.  (It could also mean that your Ostrich is failing…)  You might ask, “well why don’t you use a SocketBooster all the time?”  Unfortunately, the SocketBooster interferes with the operation of the “trace” feature of the Ostrich.

This is a list of applications where we have found a SocketBooster to be ABSOLUTELY necessary:

• 86-93 GM TBI ECMs using a 24 pin 27C32 EPROM

This is a list of application where we have found a SocketBooster to be necessary in SOME cases:

• 90-93 Nissan Z32 8 bit ECUs, 90-93 Nissan R32 Skyline 8 bit ECUs.  (By extension, most 8 bit Nissan computers around this age)
• 90-94 Mitsubishi DSM ECUs

This is a list of applications where the SocketBooster is 100% NOT needed:

• 88-95 Honda ECUs
• 86-95 GM TPI “Memcal” style ECMs
• Nintendo NES and Gameboy
• All 32 pin applications

If you don’t see your ECM listed, email support@moates.net with the particulars of your application.

Ostrich Use with PLCC32 Targets

The Ostrich can be used with PLC32 targets, but we do not sell the necessary adapters.  In most cases, you will need to get the EMU3206 cable we sell so you are starting with a 32 pin DIP.  We have fund these vendors sell adapters that will work for emulation of PLCC32 targets:

• http://www.adapt-plus.com/products/adapters/prod_dipplcc.html
• http://www.logicalsys.com/
• http://www.adapters.com/

Introduction

Although our hardware uses USB connectivity, you don’t have to be a kernel level device driver programmer or any sort of expert in the USB framework to interface our devices.Our devices simply create a virtual COM port that can be written to via all sorts of methods.

Old-school Windows programmers may be familiar with using the Windows API to play with serial ports. While this is fun, the new school .NET programmers can throw together applications in literally minutes using serialPort objects. We would love to see a C# Moates Hardware Class with all of our hardware features implemented. Unfortunately, we haven’t gotten around to doing it.

One of the downfalls of using a virtual serial port is that customers seem to have problems remembering baud rate settings. Luckily there is a (not so simple) solution. FTDI devices can be interfaced through what is known as the D2XX API. Basically, you import functions from their unmanaged DLL and you can connect to their devices without the user ever having to select a COM port. We have begun developing a C# Class based on an example from the FTDI website, but it is far from completion.

If you have written some nice code for interfacing our hardware and feel like sharing, please post it here or email us.

The following guide (MS Excel format) details the commands and expected responses for all of our devices.  If you don’t see something you need or have questions, email us.

Download the Moates Hardware Interfacing Guide here (v19 2/11/10)

Rest in Peace

The Ostrich 1.0, which has now been discontinued, was the first in the Ostrich line. Upon the creation of the first Moates product, the Autoprom (APU1) the team at Moates quickly realized the demand for separation of the Burner/Emulator/Datalogger combo.

As a result, the Ostrich 1.0 was born.

Early versions of the Ostrich 1.0 were very basic featuring only a black case.

Later versions of the Ostrich 1.0 featured a sticker with a very mean looking Ostrich.

Early revisions of the firmware used 115,200 baud rate. Later revisions (leading up to the Ostrich 2.0) were released featuring the 921,600 baud rate.

Summary

Only certain Hondas can be tuned using our hardware. In short, these are any vehicles that run a B, D, H, or F (Accord) series engine with a distributor and can run an OBD I ECU. Whether they accept these ECUs natively or via an OBD II to OBD I or OBD0 to OBD I conversion harness makes no difference.

Some of the OBD0 (pre-92) vehicles can be chipped and tuned natively, but the OBD I software tools are so much more advanced and user friendly that it is worth considering converting these vehicles to OBD1 with a conversion harness when possible.

If you have a 1996-2001 Honda, you will need to remove your stock OBD2 ECU and plug-in a supported OBD I ECU via a conversion harness. Please make sure you order the appropriate harness for your car as different model years used different connectors.

Supported Vehicles

• 1992-2000 Civic (1996-2000 Civics require OBD2-OBD1 conversion harness, use 92-95 OBD1 ECU)
• 1992-2001 Integra (1996-2001 Integras require OBD2-OBD1 conversion harness, use OBD1 ECU)
• 1992-2001 Prelude/Accord (1996-2001 Preludes require OBD2-OBD1 conversion harness, requires Integra or Civic OBD1 ECU swap, )
• 1988-1991 Civic/CRX Si-HF or swapped cars (can use OBD1 ECU and OBD1 tools with OBD1/OBD2 distributor swap and conversion harness)
• 1988-1991 Integra/CR-X/Civic with B16A swap (requires PR3/PW0 ECUs to use as OBD0 Vtec)
• 1990-1991 Civic/CRX Si D16A6 (will have PM6 ECU, ready to use as OBD0 non-vtec)
• 1988-1989 Civic/CRX Si, 1988-1991 CRX HF (requires use of a 90-91 ECU to use as OBD0 non-vtec)

Supported ECUs

• 1992-1995 Civic (P05 | P06 | P08 | P28)
• 1994-1995 Del Sol VTEC (P30)
• 1992-1995 Integra GS-R (P61, P72)
• 1992-1995 Integra RS/LS/GS/SE (PR4 | P74 | P75)
• 1992-1995 JDM Civic, Integra, Del Sol, etc. (P30, P72, P54, P08, etc. small square case. Place note in order!!! JDM ECUs require different parts than USDM)
• Chippable OBD-0 ECUs (PW0 | PR3 | PM6)
• see also pgmfi wiki on the subject

Note: If you do not see your car or ECU specifically listed here, please check to make sure you do not have an unsupported setup before purchasing anything!

Supported Tuning Software

• Neptune (targets primarily 92-95 OBD1 ECU hardware, very actively developed, advanced feature set, per-vehicle licensing)
• eCtune (targets primarily 92-95 OBD1 ECU hardware, starting to be poorly maintained, advanced feature set, per-vehicle licensing)
• CROME Pro (targets OBD1 ECUs, supports datalogging, getting to be poorly maintained, great for “simple” tunes, flexible licensing)  There is a very nice PDF tutorial written up by Darren Kattan. Check it out by clicking HERE.
• CROME (as above, free but without datalogging support)
• BRE (Primarily targets OB0 Vtec computers: PR3, PW0. Also has limited support for PM6. Only recommended for “simple” setups. Not very actively supported)
• TurboEdit (Primarily targets OBD0 non-vtec computers, i.e. PM6. Only recommended for non-vtec engines and very simple setups. Not very actively supported)
• Uberdata (Older application. Targets OBD1 platform. Once thought to be dead but seems to be some recent development activity)
• FreeLog (Free, datalogging package, works with Crome, not heavily supported/updated.)

About Firmware Updates and a Warning

Periodically we release new firmware for our products. We generally recommend against updating firmware unless you have a very specific reason for doing so, as it can often be a risky process.

If you are attempting to update your firmware because you think your current firmware is corrupt, be advised that you will not be able to update your firmware unless the old firmware actually works and is able to accept new firmware. You will have to return your device to us in these cases.

Again, most of the time problems can be resolved without a firmware upgrade. Consult this site and/or contact us at support@moates.net if you think you need a firmware update.

Firmware Update Procedure

The information on this page pertains to the following devices:

• APU1 AutoProm
• Ostrich 1.0
• Ostrich 2.0
• Flash & Burn (BURN1 / BURN2)
• Roadrunner LS1 16-Bit Emulator
• QuarterHorse J3 Ford Emulator

Directions for updating firmware:

1. Download the following utility (new version as of 2008):
   Firmware Update Utility
   and unzip it to the location of your choice.
2. Download the appropriate firmware package for your hardware from the table below and unzip it to the location of your choice (preferably to the same location as the update utility).
3. Connect your hardware to your PC and close all software applications.
4. Start the firmware update utility. Your hardware should be automatically detected. If it isn’t, click the “Detect” button
5. Click the “Browse” button in the update utility and browse to the firmware package you downloaded and unzipped in step 2 above.
6. If the package and hardware match, the “Update” button should be available. Press it now.
7. Once complete, the updater should notify you of success and display the new version information.

Firmware downloads for individual units:

Honda ECUs have a Diagnostic Generation, Model and a Board Revision.

The diagnostic generations are OBD 0, OBD I, and OBD II.

Examples of the model are  P28, P72, etc.

The board revisions are 1980, 11F0, and 1720.

Diagnostic Generation (OBD 0, OBD I, OBD IIa/b)

Every generation

From top to bottom:

Knowing the generation of your ECU is extremely important. For a P28 it is easy because the P28 was only made for OBD I vehicles, however Integra ECUs like the P72 and P75 have both OBD I and OBD II variants. Be weary of this when you are purchasing an ECU online, an OBD II ECU is basically worthless.

Model (P28/P72/etc)

Side view of P28

Just because you have an OBD 0 or OBD I ECU doesn’t necessarily mean that you’ll be able to just up and tune. Take a look at the side of your ECU, you’ll see 37820-PXX-XXX. The numbers following the P, like P28 or P30 are very important. Here are some things to note about the most common variants:

• P05 – Civic CX – Most basic supported ECU. Doesn’t have O2 Heater circuit, disable this to prevent CEL
• P06 – Civic DX – Same as P05 but has heater circuit
• P08 – JDM Civic – Same as P06, but has VTEC
• P28 -  Civic Ex/Si – The standard issue tuning ECU.
• P30 – Del Sol VTEC – Same as P28 but has a Knock Board
• P72 – Same as P30 but with IAB control
• P75 – Same as P72 but with no Knock Board or VTEC control

Board Revision

The only reason that the board revision is typically of interest is when you are attempting to add components like a VTEC conversion kit.

The board revision can be found silkscreened onto your ECU:

This is a 11F0 board

USDM/JDM

The only time you need to worry about whether your ECU is UDSM or JDM is when selecting which chip kit to purchase. JDM ECUs require slightly different chips than their USDM counterparts, so make sure you select the right one when you order.

USDM (Rectangular)

To perform an auto to manual conversion on an OBD I Honda ECU, use the following procedure:

1. Verify that you have an Automatic. You will know if there are resistors in RP17 and RP18 (next to the EEPROM)
2. Remove RP17 and RP18
3. Replace RP18 with a jumper. (The one you removed from J12 usually works well, or just a paperclip)

When you are done, the resistors should look like this:

Manual ECU Resistor Arrangement

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

Ford (requires v4.13 or higher)

Subaru (Requires v4.13 or higher)

Nissan

Porsche (Motronic)

DSM (Eagle/Mitsubishi)

Renault

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.

This page is here to add VTEC capability to your otherwise non-VTEC ECU.

The reason we are able to do this, is because when Honda designed their ECUs, the boards for the P05, P06, P28, etc were basically all identical. For the ECUs like the P05 and P06 that did not require VTEC, the components that are used for VTEC functionality were simply not installed.

Thanks to the guidance of the forums on PGMFI.org, we were able to collect these missing components, organize them into kits and sell them to you.

You can convert the following ECUs to VTEC:

• P05
• P06
• P75

The first step in the process is to identify the board in your ECU. In these ECUs, the only factors that affect board revision is the time that the ECU was produce. Meaning that just because you have a P06 doesn’t mean you’ll necessarily have a particular board.

First, identify your ECU to find out what board you have.

It will be one of the following. Clicking these will bring you to their respective page on our online store.

• 11F0
• 1720
• 1980

Your kit will come with a handful of components as well as a card with pictures that indicates the place to install the components. Sometimes this isn’t enough. Here is a better picture:

1720 Conversion

1720: VTEC Conversion

The Autoprom

The Autoprom was the first Moates device. It is a combination Emulator, Chip Burner and Datalogger.

Today you can buy these devices separately, however this package eliminates the need for 3 separate units.

Compatibility

As of writing this article, the only software known to be fully compatible with the Autoprom is TunerPro RT.  TunerCat OBD1 Tuner and TTS Datamaster support almost all of the AutoProm’s features.

If you plan on tuning Honda vehicles, purchase the Ostrich, Burn1, and HuLog separately or a Demon as there is no software for Hondas that supports the Autoprom and all of its features.

The Autoprom CANNOT be used to program F3 Ford chips using the FA nor can it be used to read Ford ECMs using the FE.  You will need to look at the Jaybird or BURN2/FA/FE combo for Ford vehicles.

The Autoprom does not work smoothly with 29F040 chips.  If you need to work with these chips, it is recommended that you purchase a BURN2.

Usage

Real-Time Tuning / Emulation

1. Make sure car is in key-off position with no power to the ECM. Remove the ‘stock’ chip and install socket adapter (G1 or G2) if not already present. Remove any chip from the AutoProm ZIF socket!
2. Hook the 28-pin ribbon cable header to the ECM chip adapter socket. Make sure the ‘red’ wire points toward where the notch, or Pin1, would be on a chip normally going in the socket. The AutoProm will auto-select its power source from either the USB port or the ECM header.
3. Get your PC powered on with TunerPro or TunerCat loaded up. Hook USB cable up to the AutoProm and PC. Check the AutoProm switch positions along the backpanel. The innermost horizontal switch can be positioned either inboard (10k – used to select data initiation on older-model vehicles.  Try the other ‘open’ setting first!) or outboard (open A-B – almost everything else) depending on ECM requirements. The outer horizontal switch should be in the ‘towards the USB port’ position. (APU1 mode. Other position is passthrough mode, identical to ALDU1).
4. If you haven’t already loaded a file onto the AutoProm, you will get an SES light condition indicating bad PROM content. Now is the time to go ahead and initialize the AutoProm from the PC software (should be under ‘Emulation, Initialize’ option). Once initialized, load the desired binary file into the PC software and upload it to the AutoProm (option should be right next to the ‘Initialize’ button). You may want to select the ‘Verify’ option (in TunerPro) to ensure that the binary upload was successful. If you keyed the vehicle on without a valid binary loaded, you may need to cycle the key off for about 20 seconds to let the ECM reset.
5. At this point, you should have the AutoProm loaded with the desired binary file. The car should now respond as though a chip with the uploaded binary content is installed. If not, then there is an issue. Either the binary is corrupt or some other condition exists.
6. From the PC software, you can make on-the-fly changes in the BIN content and have those changes immediately transferred to the AutoProm and the car should respond accordingly. There are several options within the supporting PC software, such as ‘Checksum Disable’, ‘Upload Entire Tables’, ‘Update Checksum’, and ‘Keep Item Open’, etc., so read through the documentation and practice a little bit so you understand what is going on and what to select. Typically, checksum disable or update checksum should be selected. Use a setting of “AA at 08” for 28 pin applications, and “AA at 04” for 24 pin ECMs.
7. Have fun, and try not to burn anything up other than rubber and fuel!

Stand-Alone Datalogging

1. Hook the APU1 up to the PC USB port and place the outer horizontal switch in the standalone, ‘away from USB port’ position (toward outside). It doesn’t matter whether the AutoProm is connected to the ECM chip socket because it gets power for standalone data logging from the USB port.
2. Connect the ALDL cable to the car’s ALDL connection. Place the inner horizontal switch on the AutoProm backpanel in the proper position for your vehicle and mode desired: inboard=”10k across A-B”, outboard=”open between A-B”.
3. Load up your favorite datalogging program on the PC, such as “TunerPro”, “WinALDL”, or “TTS DataMaster”. You may need to select an ADS file to define your datastream if using TunerPro. Turn on the key and start logging data! To stop, just turn car off and disconnect hardware. Keep in mind that in this mode, the hardware will not be ‘detected’ like the AutoProm mode, and that you’ll need to specify which USB Serial Port number (hopefully COM3 or COM4) has been allocated to the port in the datalogging software preferences.

Simultaneous Emulation and Datalogging

1. Carry out the same steps described above in the sections on Emulation and Datalogging, except keep the outer horizontal switch in the ‘inboard / toward USB port’ position.
2. Use a simultaneous-supporting program such as TunerPro RT to perform simultaneous datalogging and real-time emulation/tuning. You should see results from changes to the binary on-the-fly right when you make them.

Chip Reading and Programming

1. Connect the AutoProm to the USB cable. The USB will supply the power.
2. Make sure the 28 pin ribbon cable used for emulation is UNPLUGGED from the unit. Unpredictable behavior can result from the APU1 being directly connected to a ECM using the emulation cable while burning chips.
3. Place the target or source chip in the ZIF socket. Orientation is critical, and the chip should be placed with its notch or arrow facing toward the ZIF handle and toward the back panel of the AutoProm. The chip should be at the ‘bottom’ of the socket, such that any unused socket pin slots are closest to the handle or backplane.
4. Use a supporting software program, such as TunerPro or FlashBurn to pick read/write operation, file location and name, starting and ending addresses, any hex offsets, bank selection, or other characteristic of the read/write operation. Carry out desired program/read/verify steps as desired, and remove chip from socket.

APU1+Wideband+Datalog

On the back of the APU1 you will find a terminal block with 4x screw terminals. The one closest to the USB port is GND/Common, and the other 3 are for channels 1,2,3 respectively. If you have a wideband O2 with 0-5v outputs, it can be wired up to GND/CH1 and TunerPro can then present the ADC data along with the rest of the datastream.

This is a nice article written by Charles Woock on how to configure TunerPro RT to digest 0-5v inputs such as the LM1 and LC1. The values can be brought in through the APU1 via the APADC interface.  (Note: newer APU1s have the APADC interface built in as standard equipment) The tutorial explains how to set up the ADS file and render values such as AFR Air Fuel Ratio as part of your GM ALDL data stream.

Here’s the PDF file:

http://static.moates.net/zips/wideband_datalog_tunerpro_lm1.pdf

eCtune is a ROM Editor available for Hondas. It is written by Calvin Baank and has an exhaustive list of features.

eCtune has very structured licensing. It is important to note that most eCtune tunes will only work when run off the Ostrich or Demon. This means a separate Ostrich must be present in each car you tune with eCtune. (For all you CROME guys, there is no more burning chips and walking away)

At the end of the day, if you want to drive 5 cars at the same time, you will need 5 Ostrii.

There is also a dealer version available, contact eCtune for more information.

For more information on eCtune, visit the eCtune website here

NOTE: We do NOT sell or directly support eCtune.  You must purchase your software licenses and receive support directly from eCtune!  This page is provided for information only.

Neptune RTP is a tuning hardware/software package for tuning OBD1 Honda and Acura vehicles developed by James Holy.  Quality hardware, quality software and solid support combine to provide what is arguably the most comprehensive package available for tuning these cars.   More information can be found at the official Neptune site here.  The Neptune RTP software can be downloaded here.

Hardware Supported

Currently, the Demon is the only supported hardware for Neptune.  We sell the Demon+Neptune RTP setup.

Discontinued Hardware

The original Neptune RTP board was designed by Moates.  It is no longer in production and has been replaced by the Demon.

Neptune Hardware