1986 Transam EFILiveV4 connection

[gm-services]

Hey guys

I am using EFILIVE V4 professional, and Moates APU-1 to try and scan 1986 Pontiac Transam TPI 5L. It has AUM3236 PROM. I can only get it to connect by selecting VN commodore as the vehicle type. It will connect and display data, most of which is incorrect.

Is this vehicle supported, if so what vehicle type am I supposed to choose?

I have an AKM cable interface also but no serial port to try it on

What else can I try

Brad Roberts
GM Services

[Blacky]

Go to this ftp site:ftp://ftp.diy-efi.org/pub/gmecm/
Download the ALDLstuff.zip file, extract the file and open the Index.doc file. Look for a matching entry for the Transam. The VIN letter that is listed in that document is the 8th letter of the VIN.

That will tell you which *.ds file contains the data stream for that vehicle.

Create a copy of the VN *.xml file and then edit the copy with the details from the Transam's *.ds file.

Regards
Paul

[dw_bobby]

Hi all,

I have a 3.1L SFI (L82) (VIN=M) 94 Grand prix, ECM 16186387.

I found 2 entries in the index file:

DATA STREAM A256
ENGINE USAGE:
3.1L SFI (L82) (VIN=M) 94 SFI-66U 1L

DATA STREAM A259
ENGINE USAGE:
3.1L SFI (L82) (VIN=M) 94 SFI-66U 2,3,4N
3.1L SFI (L82) (VIN=M) 95 SFI-66U 2,3,4N

Which one should i use?

And how can i edit the xml file?? Looks like i need a bunch of doctorates before i can do that..)

And another thing: EFI Live connects ok but then gives me a "Com timeout: Expecting frame header byte". What is that?

Thanks a lot

[Blacky]

Those two data streams are identical except for the PRNDL decode table at byte #43. You'll just have to try both settings to see which one matches your vehicle.

You can add the data from the *.ds files using the built in EFILive V4 data stream editor.

Here's a "quick start" guide...

Select menu option: Edit->Vehicle
Then click on [Delete Item] to clear the existing vehicle.
Then create your new vehicle definition like this:

Enter a new code, for example: A256 (this is what the final *.xml file will be saved as).
Fill in the other fields with the relevant info. Only the ALDL Baud setting is relevant (use 8192), all other fields are just for your own future reference.

On the chatter tab page, check the chatter check box.
From the *ds file you can see the suspend command and resume modes are mode $08 and $09 respectively, enter the actual commands by clicking on the [...] button and adding $E4 for the ID and $08 (suspend) or $09 (resume) for the mode. EFILive will automatically calculate and add the correct checksum byte at the end of the message when you click OK.

Leave the timings and macros for now, and ad din your details in the author page if you want.

Click on the "new vehicle" icon in the left column.
Then click [add sub item] to set up the ECM module.
Add a code for the ECM Module, i.e. "ECM".
The ID comes from the *.ds file and is $E4
The mode we want is "$01 Request ALDL data frame"
Description: Engine control module.

Click on the "ECM: ($01) Request ALDL Data Frame" item in the left column.
Then click [add sub item] to set up the Request.
Add a code for the request, i.e. "Table 00".
Description: Request data from ECM's table 00
Check reply and process check boxes.
Parameter: $00 (which means get data from table 00)
You should see the frame EFILive generated will match the first "Mode 1" entry in the *.ds file. EFILive has automatically calculated and add the correct checksum byte at the end of the frame.

Click on the "Table 00: Request data from ECM's table 00" entry in the left column.
Then click [add sub item] to set up an attribute. You need to add one attribute for each of the entries under table 00 in the *ds file.

The EFILive help files go into more detail about how to do that.

Regards
Paul

[dw_bobby]

Thanks Paul, that will sure get me started on the right track.

Do you mind pointing me to the location in the help files that has more about this? I searched for info on editing the defintions but couldn't find any.

Many thanks!!

[Blacky]

Start the EFILive V4 software, select Help->Help (or press F1)
Select Reference, then Vehicle Definitions.
Also:
Select Reference, then Modules.
and
Select Reference, then Requests.
And finally
Select Reference, then Requests, then Attributes.


Regards
Paul

[dw_bobby]

ok, it's starting to make a little sense.

Couldn't find the stuff you mentioned in the ds file. Is this the "table 00"?

..PAGE
..HEAD03L NUMBER OF DATA WORDS - 67
..HEAD04L ALDL MODE 1 MESSAGE 0 RESPONSE
WORD# DATA NAME DESCRIPTION

1 TIME ENGINE RUN TIME IN SECOND MSB
2 TIME+1 ENGINE RUN TIME IN SECOND LSB
SEC = N
3 COOLDEGA COOLANT TEMPERATURE (NON DEFAULTED)
DEGREES C = N*.75 - 40
DEGREES F = 1.35*N - 40


I couldn't find basic things such as engine or vehicle speed so i'm really confused.

Would it be a good idea to take an already existing file (i.e. 1994-95 W Body LQ1.xml which shouldn't be so far from my car) and just change data according to the ds file?

Many thanks.

[Blacky]

Vehicle speed is byte 11.
Engine speed can be obtained from either 13+14 or 40.

The engine speed is an inverse operation. I.e. the "N" in the equation is the denominator on the bottom of the fraction. You need to check the "Invert" checkbox.

Regards
Paul

[Blacky]

Also when setting up parameters that use two bytes, ie.. engine speed uses bytes 13 and 14, you need to specify the starting byte as 14 and the length as 16 bits.

Regards
Paul

[Blacky]

One other very important thing. Don't add any comments to the comments fields while setting up the file. Adding comments can cause the file contents to be erased and you'll lose all data you've entered since starting the file. Its a bug deep down in the xml routines that we can't fix.

I highly recommend saving the *.xml file after adding every 3-4 parameters and copying the saved file to a new backup file each time. Sure you'll end up with a lot of files but if the bug does strike at least you have a working backup to recover.

Regards
Paul