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

[Six_Shooter]

It's not overly difficult, just time consuming.

What you have to do is use the parameters that are stated in the DS file as the information you need to imput in to TP to create the ADS or ADX.

Look for my 160 Baud ADX tutorial on the Tuner Pro site, IIRC it's in the Scanner Pro forum. There are some differences when building an 8192 baud ADS/ADX, but most of the information is a straight across copy.

--==edit==--

here are a couple links:
160 Baud ADX tutorial

A thread I started previous to the one above, that has some information about the bitmasks and such that can get a bit confusing:
Creating ADX files...

[EagleMark]

I looked over some 160 baud stuff I am familar with like the $42 which is from A033.ds and it made sense comparing it to an ads or adx file... I think I could do that... but there is no need they are all done...

But when I looked at the 8192 baud stuff and compared it to known files nothing made sense? Commands listed in ds were not correct in ads or adx... that is hard to follow... I figured if I could compare some stuff I could figure out why my EE.adx shows weird data...

I think this is going to be a long learning curve...

[Six_Shooter]

You have to make sure you are using the correct .DS file to compare to. Sometimes there are multiple .DS files listed for the same or similar applications.

[EagleMark]

Done that several times. The one for EE was written using A223.ds for a Y car. Commands do not match up to EE.adx but are close, extras were added? Couple were wrong? Like 0x57 should be 0x56 from the ALDL.ds

My car is A276.ds I started with the EE.ADX and re wrote all commands exactly from A276.ds and will try it out later.

EE.adx for LT1 can not work on Y car, F car and B car because they all use differant ds files. I verified this by getting a trail of DataMaster and there is a differant setting for each car... for instance CCM has to be silenced on Y car. B car does not have CCM tied into datastream but does have SDM or SIR and EBCM tied into serial data that would need to be silenced. The way I redid the commands were straight from the A276.ds and it looks like they are in there. For comparison my commands are twice as long as origanal EE.adx...

But then again I checked the $OD.adx stuff and it did not match up to ALDL data A219 or A217, I forget which, again extras were added... So even if I get them right I need to know more about how TP uses them... or what the extras are?

[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