All GM Cars (Ford, Holden) (16 Pin - ALDL Cable) Camaro (16 Pin - ALDL Cable) Firebird (16 Pin - ALDL Cable) Corvette (16 Pin - ALDL Cable) Lotus (12 Pin - ALDL Cable) Nissan (14 Pin - Extension cable, buy on eBay) Honda (3 Pin - Extension cable, buy on eBay) Subaru (9 Pin - Extension cable, buy on eBay). Well, your car has what is called an ALDL plug in located under the drivers side of the dash. You will need to have a scan tool plugged into this to scan the cars computer. This will tell you what has registered the fault to turn on your light. Most parts stores will scan your computer, but they are not repair.
ALDL 12 pins connector - front view
Assembly Line Diagnostic Link or ALDL is a proprietary on-board diagnostics system developed by General Motors before the standardization of OBD-2. It was previously called Assembly Line Communications Link or ALCL. The two terms are used interchangeably.
This system was only vaguely standardized and suffered from the fact that specifications for the communications link varied from one model to the next. ALDL was largely used by manufacturers for diagnostics at their dealerships and official maintenance facilities. The connector is usually located under the dash on the driver's side of left-hand drive (LHD) vehicles, though this location was not standardized.
For the assembly plant test system computer that was connected to this vehicle connector and known by the same name, see the article IBM Series/1. In the late 1980s the system was migrated to the ADTS system (ALDL Development and Test System) which utilized an industrialized IBM PC with custom interface hardware.
There were at least four different connectors used with ALDL. General Motors implemented both a 5-pin connector and a 12-pin connector, with the 12 pin connector (Packard/Delco/Delphi part number 12020043) being used in the vast majority of GM cars. Lotus implemented a 10-pin connector. The pins are given letter designations in the following layouts (as seen from the front of the vehicle connector):
Note the difference in pin ordering between the connectors and the fact that the letter I is not used. Unfortunately, the definition of which signals were present on each pin varied between vehicle models. There were generally only three pins used for basic ALDL âground, battery voltage, and a single line for dataâ, although other pins were often used for additional vehicle-specific diagnostic information and control interfaces. No battery voltage is present in the 12 pin ALDL connector.
The earliest implementations of ALDL were unidirectional and transmitted serial data at 160 baud using PWM. Some 160 baud models constantly transmitted sensor data on startup, while others started transmitting data when placed in diagnostic mode with a resistor connected to the ALDL port.
Later versions were bidirectional and operated at a much faster (but incredibly slow compared to today's standards) rate of 8192 baud. Implementations using the 8192 baud rate were primarily request-driven, meaning that the main diagnostic data was not transmitted until a request was made. Some idle data transmission of trivial parameters, however, existed in many vehicles. Bidirectional communication also allowed many other functions to be performed via ALDL, such as actuator tests, parameter overrides, and in some cases even reprogramming of the ECU itself. Multiple devices could be placed on the ALDL data line for primitive networking and communication. Many later 8192 baud vehicles, for example, had airbag control, ABS, and even climate control units sending data on the same serial bus.
In both versions, ALDL data is sent in a format unique to the model of ECU in the vehicle with little standardization between models, so a proper definition of the data is required to interpret it. Most professional scan tools require a large database of vehicle definitions.
The signaling of ALDL is similar to the RS-232serial data standard; differing in the voltages used to denote logical one (usually 0 V DC) and logical zero (either +5 V DC or +12 V DC), and that unlike RS-232, both transmit and receive functions are on the same conductor. Schematics are available on the internet for devices that can be used to convert the ALDL voltages to those of the RS-232 standard, allowing the raw data to be read with a computer having a serial port and the proper software.
Multiple scanner software programs are available. TunerPro RT is one of the most flexible and most popular. It covers most US applications. 94-95 6.5 Turbo Diesel scanner software is also available  Direct USB to ALDL cables and even Bluetooth modules are available from suppliers like Red Devil River.
Retrieved from 'https://en.wikipedia.org/w/index.php?title=ALDL&oldid=900883356'
ALDLdroid is an application for OBD1 GM (ALDL) ECMs. It is currently compatible with both 160 baud and 8192 baud protocols.
ALDLdroid is compatible with TunerPro files (ADX) for data logging, just make sure you have the ADX file for your ECM before purchasing the app. If the app doesn't come pre-packaged with the ADX file you need, you will need to add your file to the ADX directory of the ALDLdroid folder on your Android device once you've started the app for the first time and the folders structure has been created.
The application has also been used beyonds GM ECMs. With the proper XDF file (make sure your file is not encrypted), it can do tuning file editing on other car/motorcycle brands such as BMW N54, Buell, DSM, Ducati, Ford, Holden, Nissan, Porsche, Volvo, Fiat, Renault, etc. Just make sure your can source the XDF file for your application before purchasing the app.
The tuning section uses TunerPro files as well (XDF) to allow editing BIN files. Real-time tuning is currently supported with the Moates Ostrich and the Moates AutoProm hardware. Real-time tuning for NVRAM based ECUs has also been added (only tested with Australian ECUs such as the Delco '808). Chip programming is also possible using the Moates BURN1/BURN2 hardware.
Currently, connection to the ECM can be made using Bluetooth or USB (FTDI). Make sure that your Android device support one of these two connection methods. USB host mode is supported on most devices these days but note that having a USB port on your Android device doesn't automatically means it support USB host mode.
For GM OBD-I, ALDL adapters to connect the application to your GM ECM for data logging can be purchased here if you don't already own one:
- Bluetooth version: http://www.1320electronics.com/products.html
- USB version: http://www.moates.net/aldu1-and-cabl1-p-127.html
By double tapping on any page of the dashboard, you enter the dashboard edit mode. That mode allow full customization (add/edit/delete) of the dashboard indicators. You can easily drag indicators where you want them. You can also add indicators in the format you want: gauge, basic readout, bar graph or histogram. Colors can be customized along with some styling. Alarms can be set and once your alarm value has been entered to trigger an alarm, an indicator can be configured to turn red and/or the Android app can vibrate.
The app includes a couple log viewers. One allow you to see your data logs in a scatter plot format where you can select the X/Y/Z axis from columns of your data log files. The second one allow you to see your GPS data on a map and can be merged with the third viewer that is the regular log viewer that can shows time series of data from any columns of your data log files. See screenshots to see all three of them.
No refund can be made after the 15 minutes allowed by Google Play. It would probably be a good idea to check with online communities that use the same ECM as you if they had success with this app before purchasing.
If you're running into any issue with the app, don't panic, just email me and I will try my best to help. Don't write a bad review until you gave me a chance to help :) Note that I might not have access to your exact setup (Car ECM, Android device, etc) so please provide as much information as possible.
I'm not responsible for any damage that could be caused by this app to your vehicle or anything else (although I really don't see how anything bad could happen). Buy and use at your own risks. Drive safe!
Like us on facebook: https://www.facebook.com/aldldroid