Building a LT1 $EE ADS file from ALDL DS file?

[EagleMark]

Just found the first EE LT1 adx file and another modified. In the commands they are nothing like what the aldl ds lists and nothing like the latest EE on TP website. So far I have about 15 hours into trying to learn how to do this from a ds file and just can't find the information.

Going to try them in my LT1 tomorrow and see if any work.

With Robert retired I just don't know if anyone will be able to figure these out.

Mark at TP is going to have to do a tutorial so we can write these. There's got to be a sceince to this. Even if I get data coming in on same it has a glitch where it jumps numbers for a second then back. Looked at the origanal EE first one written for SannerPro before it was incoperated to TunerPro and it has loads of silence commands the new one does not... with hex adress not even mentioned in the ALDL.ds... so how the heck do you figure it out?

[Six_Shooter]

It's probably an offset that is confusing you, remember hex always starts counting at 0 (zero).

[EagleMark]

I thought about that after reading your ADX write ups and the Understanding Hex at TunerPro. But some of the address are spot on, some were not even mentioned?

So it's like they used all ALDL.ds address but added a few.

Then as far as commands, replies and macros they don't add up from ALDL.ds to what's written in TP ADX... that is one thing I have to figure out and there is no documentation on is Commands.
1. Send Command
2. Listen for packet response
OK those 2 I have figured in the ALDL.ds
3. Listen for silence
4. Trigger
5. Macro Command
Those three I don't understand. But with these old/first written EE.adx files they have a bunch where the new one does not. I'll have to see if I can reverse engeener what's there

[EagleMark]

Here's the one I have been trying to get to work... To make things more confusing the listings for LT1 are below. Doesn't matter to much to compare them as they all have the same Mode 1 Message send... well some are 5 and leave out the trans? But most have six.
DATA STREAM A223
ENGINE USAGE:
5.7L MFI (LT1) (VIN = P) 1994 1B,F,Y 2F 4B 6D - CARS
3.4L MFI (L99) (VIN = T) 1994 1B - CARS
* 5.7L SFI (LT1) (VIN = P) 1995 1Y - CAR AUTOMATIC TRANSMISSIONDATA STREAM A273
ENGINE USAGE:
5.7L MFI (LT1) (VIN = P) 1994 1,2F - CARS MANUAL TRANSMISSION
* 5.7L SFI (LT1) (VIN = P) 1995 1,2F - CARS MANUAL TRANSMISSION
DATA STREAM A274
ENGINE USAGE:
5.7L MFI (LT1) (VIN = P) 1994 1,2F - CARS AUTOMATIC TRANSMISSION
* 5.7L SFI (LT1) (VIN = P) 1995 1,2F - CARS AUTOMATIC TRANSMISSION
DATA STREAM A275
ENGINE USAGE:
5.7L MFI (LT1) (VIN = P) 1994 1Y - CAR MANUAL TRANSMISSION
* 5.7L SFI (LT1) (VIN = P) 1995 1Y - CAR MANUAL TRANSMISSION
DATA STREAM A276
ENGINE USAGE:
5.7L SFI (LT1) (VIN = P) 1994 1,4B 6D - CARS
4.3L SFI (L99) (VIN = T) 1994 1B - CAR
* 5.7L SFI (LT1) (VIN = P) 1995 1,4B 6D - CARS
* 4.3L SFI (L99) (VIN = W) 1995 1B - CAR

Been looking through a lot of ALDL.ds files and good know working TP ADX files. One thing I notice added to TP files in a Mode 1 Message send is extra code added? not just this EE.ADX it is in $OD.ADX and others?

ALDL.ds says: MODE 1 (TRANSMIT FIXED DATA STREAM MESSAGE 0)
ALDL REQUEST:
- MESSAGE ID = $F4
- MESSAGE LENGTH = $57
- MODE NUMBER = $01
- MESSAGE NUMBER = $00
- CHECKSUM

TP Mode 1 Message 0 send says "0xF4 0x57 0x01 0x00 0xB4" So what is the "0xB4" for?

ALDL.ds MODE 1 (TRANSMIT FIXED DATA STREAM MESSAGE 1)
ALDL REQUEST:
- MESSAGE ID = $F4
- MESSAGE LENGTH = $57
- MODE NUMBER = $01
- MESSAGE NUMBER = $01
- CHECKSUM


TP Mode 1 Message1 Send and it says "0xF4 0x57 0x01 0x01 0xB3" So what is the "0xB3" for?

Go to third and last Mode 1 Message 2 and it adds a "0xB2"

Also found in A223.ds Mode 1 Messages for transmit data there are Six. But only 3 are in the EE.adx... I'm wondering if this is why I only get some data? So if I add the other three I may get my data, but really don't know if I should add a 0xB1 on one 0xB0 on another, but then whaat to do for third? Guess if I knew why they were there I would know what to do?

[93V8S10]

0xB4 and 0xB3 are the checksum.

[historystamp]

ALDL REQUEST:
- MESSAGE ID = $F4
- MESSAGE LENGTH = $57
- MODE NUMBER = $01
- MESSAGE NUMBER = $00
- CHECKSUM

TP Mode 1 Message 0 send says "0xF4 0x57 0x01 0x00 0xB4" So what is the "0xB4" for?


The "0xB4" is the checksum.

Luke Skaff's senior engineering project was to build a scanner tool. He documents the commands in Appendix A Table 7. The request command is at the top of the table with the response below.


http://lukeskaff.com/?page_id=305


You can get his original report,
Senior_Project_2007_Automotive_Diagnostic_LCD_Inte rface.pdf


Look under the section (or do a google search).
4. College Senior Project Final Report

Robert

[EagleMark]

ALDL REQUEST:
- MESSAGE ID = $F4
- MESSAGE LENGTH = $57
- MODE NUMBER = $01
- MESSAGE NUMBER = $00
- CHECKSUM

TP Mode 1 Message 0 send says "0xF4 0x57 0x01 0x00 0xB4" So what is the "0xB4" for?

The "0xB4" is the checksum.

Luke Skaff's senior engineering project was to build a scanner tool. He documents the commands in Appendix A Table 7. The request command is at the top of the table with the response below.

http://lukeskaff.com/?page_id=305

You can get his original report,
Senior_Project_2007_Automotive_Diagnostic_LCD_Inte rface.pdf

Look under the section (or do a google search).
4. College Senior Project Final Report

Robert

Great link! I've read his stuff before about the Northstar DIS.

Here's what I found in that Senior Project .pdf

For reference, refer to Appendix A for the list of commands each ECU mode is

activated by. The most basic command set will include in this order: a message ID byte,

message length byte, mode byte, and a checksum byte. The more complex commands

will have other data bytes transmitted after the mode byte and before the checksum byte.

The first command in the command set is the message ID byte which lets the ECU know

what category of command it is receiving. Since all the commands listed above and in

Appendix A are diagnostic commands they all have the same message ID byte of 0xF4.

The next command in the command set is the message length byte. The most basic

command set has a base message length byte of 0x56 and any other commands or data

transmitted increments the message length number per extra byte transmitted. The mode

byte is simply the desired ECU operation mode number. Other data bytes must be

transmitted in the more complex data modes which are: mode 2, mode 3, and mode 4.

The last byte to be transmitted is the checksum byte. The checksum byte is the one’s

complement of the sum of all bytes transmitted.

[EagleMark]

0xB4 and 0xB3 are the checksum.

Ahhh from the guy who has made the coolest xdf and adx!

Now since I am trying to add the other Mode 1 data fixed messages how does one calculate the checksum? I just saw a pattern of it going down... but it should be calculated from something?

I'd sure like to get the EE,adx working for the 94-95 LT1 engines. It connects and gets some data, some wrong data and some NO data...

[historystamp]

I'd sure like to get the EE,adx working for the 94-95 LT1 engines. It connects and gets some data, some wrong data and some NO data...

I assume you know ...

'94 & '95 were the transition years from OBDI and OBDII. Some people refer to it as OBD 1.5. This could be why you are seeing so many data streams.

Checksum is a value calculated from the data that is pasted onto the end of a data stream by the sender. The receiver recalculates the value to compare to the sent checksum. This way the receiver can tell if the data was sent correctly or was corrupted on the wire.

I read calculating the checksum as you sum up all the data. Discard any bits that flow out of the 8 bit value then flip the bit values: 0 to 1 & 1 to 0. ( Called one's compliment. )
0xF4 + 0x56 + 0x01 = 0x14B chopping = 0x4B complimenting = 0xB4
Same result as Luke Skaff's pdf page 21
I'm not sure were the idea of the 0xFF entered the picture. Seems to be a red herring.

Robert