Building a ADS file from ALDL DS file?

[EagleMark]

Well I'm figurung this ADS file is built from origanal ALDL DS files. I have all them.

Once they are converted or built you have the equivilent for instance $42 is ALDL A033.ds converted is now A033.ads. Import to Tunerpro and you now have an ADX that can be custimized in TP and hand edited in NotePad or EditPad.

Most ds files have been converted and available on TP website but the one I need is not.

Does anyone know how to convert/build an ADS from the DS?

[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 TRANSMISSION
DATA 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?

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?

[EagleMark]

Figured out the extra 0xB4 was the checksum.

Information gathered from:
http://www.gearhead-efi.com/Fuel-Inject ... DL-DS-file

That information pointed me in the right direction. But then got confusing. ECM Guy wrote:
Note:

1. The sum
check is the complement of the message. When the incoming message is added
it
will always have a LSB
of $FF

Well if I add 0xF4 0x57 0x01 0x00 I get a checksum of 0x4C? So that does not correspond to the 0xB4 So I added the 0xFF and got Ox4B? went down? did all this using a calculator. The looked at the Command entry/Edit box in Tunerpro and used the checksum and came out with the same thing... then tried the Checksum box with ones complement and got OxB3 but forgot to add the $FF from above and then got the correct Checksum that was there in the first place 0xB4.

So conclusion when building an ADX from ALDL is use info from ALDL.ds for that Mode 1 data message
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" Click the Checksum box and choose 2's complement and you will get the 0XFF added to it plus incoming message for the correct Checksum of 0xB4 for that message. Copy it and add it to hex stream.
0xF4 0x57 0x01 0x00
and paste 0xB4 to get.
0xF4 0x57 0x01 0x00 0xB4

$B4 or 0XB4 is 180 in decimal. I still have not figured out exactly what is uses to get that number, but at this point TunerPro has another built in feature to serve this purpose!

Then if you have the correct hex string 0xF4 0x57 0x01 0x00 0xB4 you can use the Checksum button to check, it should come back as 0x00 in Sum. 0x00 in 1's Compliment and 0xFF in 2's Complement.