EFI Live Commercial Scan and Tune comes with two VIN licenses. To tune more vehicles, you must provide us some information when you purchase VIN or stream licenses.

Requesting a New License

1. Plug in your EFI Live FlashScan handheld to your laptop.  Its display should be lit up.
2. Double click on the “EFILive V7.5 Tune Tool” icon to start the software.  If you do not have this on your desktop, go to the “Start” menu and find it under the EFI Live program group.
   
3. Go to the “Help” menu and select “FlashScan V2 / AutoCal V2 VIN Licensing…”  
4. We need two pieces of information from here.  #1 – WE NEED YOUR SERIAL NUMBER.  You can click the “Copy” button to copy it to the clipboard.
   
5. Once it has been copied, open up an email to us (or the Comments section of your order) and press Control-V (or right click + select paste).  Doing things this way ensure you don’t make a typo.
   
6. Next, click the “Authenticate” table towards the bottom of this window.
   
7. On the “Authenticate” tab is another important piece of information we need, the Auth Code.  Click “Copy” to copy the Auth Code to the clipboard.
   
8. Go back to your email to us / comments for your order.  Hit Control-V again to paste your Auth Code
   
9. That’s it!  Go ahead and submit your Serial + Auth with your order.  If you forget to do so, you can email it to [email protected]

Installing a License Key

After you’ve paid for your licenses, you need to use the information we give you to add them to your EFI Live handheld.

1. Plug in your EFI Live FlashScan handheld to your laptop.  Its display should be lit up.
2. Double click on the “EFILive V7.5 Tune Tool” icon to start the software.  If you do not have this on your desktop, go to the “Start” menu and find it under the EFI Live program group.
   
3. Go to the “Help” menu and select “FlashScan V2 / AutoCal V2 VIN Licensing…”
   
4. Decision time: What did you purchase?
   • If you purchased an Upgrade to Dodge (from Chevy only) select “Upgrade” (blue)
   • If you purchased a Stream license for unlimited VINs of a certain type of vehicle, select “Add Stream” (yellow)
   • If you purchased a VIN License(s) select “Add VIN” (green)
     
5. Look at the email you will have received from us and find the important information.  Activation Code (Red) Number of licenses purchased (yellow)  Total license ount (green)

   

6. Enter the Activation code you should have received in the box and click “Add”.   If you’re entering VIN Licenses, you need to adjust the license number before clicking “Add”.  To do this:
   • Look at the license screen to the right and count the number of licenses in use currently. (4 in the pictured example)
   • Add the number of licenses purchased to the number of licenses in use
   • Set the ‘License number’ to this value.

     

7. You should see a message informing you that the change was successful.
   
8. You should see the new licenses available for use.
   

WinALDL is software to datalog on GM vehicles that use the old 160 baud rate.  This includes but is not limited to vehicles using a 1227747 and 1227165 ECM.  Most older TBI GM computers will speak this protocol.  WinALDL does NOT speak to newer GM OBD1 vehicles that use 8192 baud communication.

WinALDL is available from http://winaldl.joby.se/

WinALDL was written several years ago.  It will work best on Windows XP or older operating systems, if available.  You may need to use a VM or Windows XP compatibility mode on newer Windows7 systems in order for it to run 100% properly.

WinALDL will work with both our ALDU1 and AutoProm.

Setup

There are a few setup tasks that need to be performed.

• Ensure that your ALDU1 or AutoProm is assigned a COM port between 1 and 4.  Make sure you choose a port that does not conflict with system resources.  (see USB guide)
• If you are using the AutoProm, ensure that it is set to pass-through *NOT* AutoProm mode. (see AutoProm troubleshooting guide)
• On most 160 baud applications, you will need to set the switch to 10k mode on your AutoProm or ALDU1
• Set the COM port selection in WinALDL to match what it set up to on the USB driver under the control panel.
• Set the baud rate to 4800 within the WinALDL program.
• Select the ECM type in WinALDL which matches your ECM.
• Make sure the ALDU1 is connected to the laptop prior to starting the software.
• Turn your key off, connect the ALDU1 to the car, and start the software.
• Turn the car on, it should connect.

TunerCat OBD2 Tuner is a software package that allows tuning of 96-current GM vehicles.  For some early 96-97 vehicles, it is often the only solution. TunerCat OBD2 Tuner must be purchased with our RoadRunner hardware (either with a complete RoadRunner ECM or just a RoadRunner Guts kit)  due to licensing restrictions.  TunerCat OBD2 Tuner also has an optional reflash cable accessory and software (“WinFLASH”) that allows vehicles to be flash programmed over the OBD2 port.  Existing users of TunerCat OBD2 software can use a RoadRunner ECM with the RTOBD2 upgrade.  This upgrade is only available to existing users of the TunerCat software.

The software supports real time tuning with the RoadRunner on supported vehicles, reading and flashing over the OBD2 port. THERE IS NO BUILT-IN DATALOGGING APPLICATION. You must have a third party logger or scan-tool in order to have an effective tuning combination.  MX Scan used to work with older versions of the TunerCat reflash cable but it is NOT reported to work with current cables.

TunerCat OBD2 Tuner is licensed on a per-VDF (Vehicle Definition File) basis.  You can purchase each VDF individually or as a package including a group (LS1, All) of definitions and hardware together at a discount.  Each VDF generally covers multiple vehicles that use similar engine controllers.  Once you have purchased a VDF, you may tune as many vehicles of that type as you like – there is no per-VIN licensing.

Installation Tips and Troubleshooting

TunerCat OBD2 tuner relies on the same FTDI drivers that we use for the rest of our products.  If you suspect you have driver issues, please consult the USB Driver Troubleshooting Guide.

TunerCat OBD2 Tuner is not the most modern piece of software.  In fact, if you want the software to run properly we highly recommend that you use Windows XP as this is the only operating system that has consistent behavior without a fuss.  TunerCat OBD2 Tuner has been tested to run successfully inside a VMWare Virtual Machine running XP and can be made to run stable in this configuration.

If you cannot figure out a way to use Windows XP and are going to try to use TunerCat OBD2 tuner under Windows Vista, Win7 and Win8/8.1, follow these steps:

1. If you’ve already run the installers, first uninstall the program.
2. In order for the programs to install correctly the installation program must be run in Compatibility mode. Before running the setup program right click on it. Select Properties from the list and then click the Compatibility tab. From there, pick the default (Windows XP SP2), click on the ‘Apply’ button and then click on the ‘OK’ button.
3. Now double click on the setup program to install the program and follow the on-screen instruction to complete the installation.
4. After completing the installation you’ll also need to set the OBDII RT Tuner program itself to run in compatibility mode. To do so, right click on the OBDII RT Tuner icon on the Desktop, Select ‘Properties’ from the pop-up menu and then click the ‘Compatibility’ tab. On the Compatibility screen click on the ‘Run the program in compatibility mode, select the default Windows XP SP2, check the ‘Run as administrator’ box, click on the ‘Apply’ button and then click on the ‘OK’ button. Then repeat this process for the WinFlash OBDII program.

Vehicle Support

The latest list of supported vehicles can always be found here: TunerCat ODB2 VDF files

As of the time of writing (3-26-2012), the following vehicles are supported:

Among other things, TunerPro RT brings a new definition format, the ADX.  This is an extended version of the previous file format, ADS.  The file formats are NOT compatible, but you can convert between them fairly simply.  Unfortunately, the automatic conversion utility in TunerPro isn’t perfect so this guide exists to help you achieve success.

Failure to set the body length correctly (which this guide will explain) can result in periodic timeouts or errors while logging.  Generally, you will be able to initially connect but there will be seemingly random errors in the data captured.  This seems to be much worse on faster PCs.

Procedure

1. Open TunerPro v5.x
2. Go to Acquisition … Import Definition … From ADS
3. Point TunerPro at the ADS file you wish to convert.
4. When prompted, choose a filename for the new ADX definition (this filename doesn’t really matter, just remember it)
5. Go to Acquisition … Load Definition and point it at the file you just saved.
6. Go to Acquisition … Edit Definition
7. In the editor window, click on the plus next to Commands and then click on Transmit Data Reply
8. Make sure the “Body Size (Dec)” item is 67.  In many cases, it will incorrectly get set to 66 by the automatic conversion tool.
9. Click ‘Save’ and you’re done!  If you ever load this definition in the future, it will be ready to go.

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!

You can also click this for a direct link to the files section: link

In order to issue you a license for Binary Editor, you must first download and install the software. ( http://www.eecanalyzer.net )  Once you have downloaded and installed the software, go to the “Register” menu at the top of the screen and select “Register Binary Editor”

Next, you will be presented with a screen where you need to provide some information.  First, check the boxes to indicate which hardware you will be using.  Under “Tuners,” check “Moates” for the QuarterHorse.  If you have an Innovate or PLX wideband, make sure you check the appropriate box under “Loggers.”  You will also need to do this for the DataQ standalone datalogger, if you own one.  Finally, put your name in the “Licensed To:” box.  Finally, copy and paste the Machine Code displayed and email it to [email protected] so he can issue you your license.

Note: you will see the machine code  change as you check and uncheck boxes along with changing the name in the “Licensed To:” box.  You must have the same boxes checked and your name typed identically as when you requested your license before you type in the registration key or your “Machine Code” will be different and the registration process will fail!

After you have received an email with your registration key, you will need to open the software registration box again, make sure the same boxes are checked, re-input your name in the “Licensed To:” box so everything matches.  Enter the registration key in the boxes below and then click “Register” – and you’re done!

EEC Analyzer

Download and install the software from http://www.eecanalyzer.net

Go to the “About” tab and click “Register”

Copy and paste the “Machine Code” into an email to [email protected]

When you receive your registration code, navigate back to this screen and enter it in the bottom box then click “Ok.”  Your software will now be registered.

Hardware Supported

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

Discontinued Hardware

If you have discontinued hardware, you can get current production hardware (Demon2) for half off with our trade-in program.  More details here.

The Demon (or “Demon 1”) is no longer in production and has been replaced by the Demon2.

Demon1 hardware

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

Original Neptune RTP Hardware

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.

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.

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.

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]