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.

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.

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.