ALDL Definitions

[DieselBob]

I was wondering if there was a use for this kind of sheet?
I dont have a problem modifying it to suit any $ mask just need the stream order.
It was kind of a project to put back something into the open source world of GM ECU's.
I've used all sorts of pages myself DrBob's cal page, the ECM Guy, DIY EFI, EFILive and TunerPro to mention a few.
Thought i might be able to help someone else......

[VL400]

Its handy info to have out there for sure so thanks for compiling it all I normally use the commanded spark advance to confirm the ECU and timing marks line up when initially getting new installs running - can then confirm everything was happy rather than leaving lots of expensive bits on the race track.

[DieselBob]

No worries.

I was wondering if anyone had a test bench for a VR ecu they could run some commands through
it to confirm the accuracy of the conversions?
I've got a 1227808 bench haven't modded it yet for the VR and still trying to "acquire" an ECU

Haven't tried them on my VR it's the get to work machine

I use this kind of thing for truoble shooting having the sheet makes generating the instrucion set easier.

Thanks VL400 and DrBob for the info much appreciated

[DieselBob]

Another question....

Mode 1
0xF4 0x57 0x01 0x00
gets Engine Data

0xF4 0x57 0x01 0x04
gets Trans Data

Looked about and cant find any info on the other messages available to Mode 1

Any Suggestions??

[VL400]

In VR its like this ...
Message 0 = All engine
Message 1 = Engine inputs
Message 2 = Engine outputs
Message 3 = Malf history
Message 4 = All trans
Message 5 = Trans inputs
Message 6 = Trans outputs (In 12P this is a defineable message as its normally not used)
Message 7 = Tech-1 cal
Message 8 = Tech-1 cal
Message 9 = Tech-1 cal
Message 10 = Tech-1 cal

[DieselBob]

Thanks again

[DieselBob]

Ok update to previous.

Sheet now 90% complete - have checked on Vr series II

Will work with either EFILiveV4 or TunerPro
Will take input from one and has the ability to generate a Hex Stream for the other

Checksum probs sorted

Only Byte not working is the SLEW values
Still working on that

Any body with suggestions feel free.......

[DieselBob]

Quick Question on Logging


When the log plots into the history table how does it filter the values?

e.g Main Spark Table is RPM vs kPA

The table has 400 Rpm breaks and 10 kPA from 20 to 70 then 5 upto 100...

I'm wondering how the data between the displayed values are handled...
Does the history table take 100 Rpm either side for example?
Do the kPA values have an error built in as well?

[DieselBob]

Ok dug around and found an answer interpolation.....

Another question

MODE 2 memory downloads
Looked at VL400's ALDL basics and no answer there
I've found some stuff for 64 bits per message of .bin and LTFC values but they are again sketchy at best.

Thinking maybe Trans cells as well??
if anyone has info or a direction to look much appreciated....

Seems to be alot in the stream that is not labeled..... Mostly curious but might be useful

[VL400]

Mode 2 gets you 64 bytes from anywhere in the ECUs memory, so can dump the RAM or the cal or the whole bin. You just specify a start address from where you want the 64 bytes.

Defining the RAM is a big task though so its undocumented.