OBD GM ALDL software

**malcom2073** · 04-25-2009, 11:09 AM

One of the big problems with OBD1 gauges via ALDL, is that each ECU outputs the data differently. You need an ECU definition file to know what your ECU is going to output. I can probably adapt my gauges that I pasted as a screenshot on the second page into a workable program, but it would require people entering in their own ecu data format. I have a list of the ECU formats for a good number of 80's GM vehicles, I'll see what I can dig up if there really is interest.

**talons24** · 04-25-2009, 01:22 PM

The ECU I am using, (and which is the most popular for engine swaps into older cars) is the 1994-1995 LT1 computer. Part number 16188051 I would bet that if you set up software for this ecm you would have a hit on your hands. If you are interested I have 2 of these ECMs that have not been modified or changed in any way that I can supply you one to do any testing you want on it in exchange for the setup when you get it done.

Thanks again

**ElCap** · 04-26-2009, 03:56 AM

Originally Posted by malcom2073

One of the big problems with OBD1 gauges via ALDL, is that each ECU outputs the data differently. You need an ECU definition file to know what your ECU is going to output. I can probably adapt my gauges that I pasted as a screenshot on the second page into a workable program, but it would require people entering in their own ecu data format. I have a list of the ECU formats for a good number of 80's GM vehicles, I'll see what I can dig up if there really is interest.

im definately interested!!! i have the 1227808 ecm.

**malcom2073** · 04-26-2009, 08:33 AM

Originally Posted by ElCap

im definately interested!!! i have the 1227808 ecm.

That's the aussie version of mine, which is the 1227165, cept you don't have 8192 baud you're limited to 160 baud. In theory it has the same datastream output as mine in 160 baud mode (mine does both baud rates), but you're gonna be limited in update rate.

As for the 16188051, I found the datastream information, the only thing is... is that ECU from an atx or mtx? Apparently it makes a difference.

**talons24** · 04-26-2009, 10:50 AM

I didnt know they used that ecm on standards and autos. Mine is an Automatic (a 4L60E transmission), And that is the most popular, but Standards do get used on conversions from time to time as well. Thanks again

**ElCap** · 04-27-2009, 03:37 AM

Originally Posted by malcom2073

That's the aussie version of mine, which is the 1227165, cept you don't have 8192 baud you're limited to 160 baud. In theory it has the same datastream output as mine in 160 baud mode (mine does both baud rates), but you're gonna be limited in update rate.

Yeh stupid 160 baud rate! ive heard that i can replace my 1227808 with the 1227165 and get the 8192 baud rate. but i cant seem to find any for a good price. ive also got a kalmaker tune so i'd prob need to check with my tuner that it would be a straight swap (cant see why not..).

160 baud rate just aint enough for any proper digital dash thou.. i mean it can display a fair few things like battery voltage, water temp etc (stuff that doesn't change too often) but for anything that update regularly (like speed, tacho, tps etc) its not too practical.

but hey ill still give a go lol.

**talons24** · 04-27-2009, 09:34 AM

There is a website out there that might help you find the other ECM for a more reasonable cost it is CAR-PARTS........ You can search by price or how close they are to you. Thats where I got my ECMs.

**davesaudio2** · 04-28-2009, 08:46 PM

Each ECM using a different protocol, ya gotta wonder just what they were thinking. Different teams I suppose...

**84RegalRider** · 05-10-2009, 03:57 PM

"160 baud rate just aint enough for any proper digital dash thou"

agreed, even though it was only less then a second lag i got it down too it still kinda sucked, but thats only when i floored it. Under normal driving everything was updated regularly and on time.

**antus** · 07-02-2009, 10:07 AM

Ive just signed up here to post some info for ELcap. Kalmaker runs 8192baud ALDL, not 160. To get this data you'll need to add a max232 serial interface to your ECU. This serial link will differ from the 'real' 8192 baud ALDL in that it wont be on the ALDL pin on the OBD connector, instead after modding your ECU you'll have a full duplex serial port. Assuming you have a street pro 3 tune, not workshop, and if it is the normally aspirated program (N03) you can get a definition for scannerpro or tunerproRT 5 (when its released) here:

http://www.delcohacking.net/forums/v....php?f=10&t=29

Ive also developed some ALDL software that emulates a moates autoprom to talk to tunerproRT and converts the write requests to Kalmaker or OSE ALDL write requests (when running on NVSRAM). This software is called antusprom. Im having some trouble getting it to talk reliably to newer PCMs though, and it has no gui, so I hope to try and improve some of the software in this thread instead.

Does anyone know if the source for the QT toolkit ALDL reader here is available?