GM Technical Document Discussion
GM ALDL Logging and Scanning
Forum rules
To gain access to the Invite Only forum you must be invited by a member of that forum. That member will PM the mods or admins (NOT you) saying that they nominate you for access. THEY will be responsible for your actions. If you don't post and just leech info, you will BOTH be removed. Dont send a PM to the moderators or admins asking for access, you really dont want to see the result. If you submit information, you may simply be invited
To gain access to the Invite Only forum you must be invited by a member of that forum. That member will PM the mods or admins (NOT you) saying that they nominate you for access. THEY will be responsible for your actions. If you don't post and just leech info, you will BOTH be removed. Dont send a PM to the moderators or admins asking for access, you really dont want to see the result. If you submit information, you may simply be invited
by jezzab » Wed May 23, 2012 6:26 pm
Lots of data in one hit huh? ALDL is only 8192baud, try GMLAN at 33000 baud or HSCAN at 250,000+!!
Daily Ute - 2009 Holden VE SSV Ute Single Turbo (IQ, E3 Cluster, EDI) - 586rwhp
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
by jezzab » Wed May 23, 2012 6:41 pm
TazzI wrote:Alright so beginning to understand the 'meanings' of each byte.
use an easy example..
F4 57 01 04 B0
F4 : the device ID that you are addressing
57 : the length of the data in the message (don't quite understand what '57' exactly means.. 57 bytes?)
01 : is the aldl mode, eg 1 which requests dataframes
04 : message number requested (particular section requested?)
B0 : checksum (I calculate this weird..is there a proper way?)
checksum = (FF - F4 - 57 - 01 - 04) = AF +1 = B0
Devices I know so far..
PCM - $F7
BCM - $F1
And you missed a bit off the message length. It the length of the message not including this byte or the checksum plus 0x55. So your example is 2 bytes
Daily Ute - 2009 Holden VE SSV Ute Single Turbo (IQ, E3 Cluster, EDI) - 586rwhp
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
by TazzI » Wed May 23, 2012 11:44 pm
250 000+... 
...Well makes aldl look like a popup book. haha
F4 57 01 04 B0
Oh.. so message length is the F4, 01, 04. Doesn't include itself (57) or the check sum (B0)
ah.. does that mean my 57 is wrong.. 0x55 +3bytes would be 58.. no.
Or message length is everything after itself excluding checksum. eg. 01, 04 = therefore 0x55 +2 = 57.
Hmm think Im beginning to confuse my self!
...Well makes aldl look like a popup book. hahajezzab wrote:And you missed a bit off the message length. It the length of the message not including this byte or the checksum plus 0x55. So your example is 2 bytes
F4 57 01 04 B0
Oh.. so message length is the F4, 01, 04. Doesn't include itself (57) or the check sum (B0)
ah.. does that mean my 57 is wrong.. 0x55 +3bytes would be 58.. no.
Or message length is everything after itself excluding checksum. eg. 01, 04 = therefore 0x55 +2 = 57.
Hmm think Im beginning to confuse my self!
by TazzI » Thu May 24, 2012 12:12 am
Ah I get it now..
F4 57 01 04 B0
55 + 2 = 57
Simple as.
In case anyone doesn't get the check-sum.. (and so I can check if i ever get confused!)
F4+57+01+04 = 0x150
0x150-0x100 = 0x50
0x100 - 0x50 = B0
F4 57 01 04 B0
55 + 2 = 57
Simple as.
In case anyone doesn't get the check-sum.. (and so I can check if i ever get confused!)
F4+57+01+04 = 0x150
0x150-0x100 = 0x50
0x100 - 0x50 = B0
by jezzab » Thu May 24, 2012 8:01 am
Yeah sorry it was a typo. Should have read 2 bytes not 3. Fixed now
Daily Ute - 2009 Holden VE SSV Ute Single Turbo (IQ, E3 Cluster, EDI) - 586rwhp
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
Drag Ute - 2002 Holden VU SS Twin Turbo - 1010rwhp [SOLD]
All VE/VF Module reprogramming. Remote programming with flash box
http://www.facebook.com/jsbperformance
by gruntly69 » Thu May 24, 2012 8:56 am
Not sure how the check sum works with this as it doesn't work with your calculation?
This is the command I've just sent in my VY V6 to lock 3rd gear with TCC disengaged, good for dyno runs!
0xF7 0x58 0x04 0x81 0x00
Can you figure tat 1 out?
This is the command I've just sent in my VY V6 to lock 3rd gear with TCC disengaged, good for dyno runs!
0xF7 0x58 0x04 0x81 0x00
Can you figure tat 1 out?
by TazzI » Thu May 24, 2012 10:58 am
gruntly69 wrote:Not sure how the check sum works with this as it doesn't work with your calculation?
This is the command I've just sent in my VY V6 to lock 3rd gear with TCC disengaged, good for dyno runs!
0xF7 0x58 0x04 0x81 0x00
Can you figure tat 1 out?
Your message length should be 57 (don't include device ID F4 or the message byte itself or the checksum), as the 'message' sent is 04, 58. .... 0x55 +2bytes = 0x57
0xF7+0x57+0x04+0x81 = 0x1D3
0x1D3 - 0x100 = 0xD3
0x100 - 0xD3 = 2D
Following that provides correct calc to what I understand.
*edit
Unless your mean that 0x04 0x81 0x00 is the message? and what the checksum for that?
If so your message length will be 0x58
Checksum will be: 2C
by TazzI » Thu May 24, 2012 11:06 am
.. dam edit time is not long enough!
Grunt, sending through VL's program calculates the checksum automatically. But if your using anything else, you will need to calculate it yourself!
Grunt, sending through VL's program calculates the checksum automatically. But if your using anything else, you will need to calculate it yourself!
by gruntly69 » Thu May 24, 2012 11:47 am
It's just a command sent through tp5 with 2's compliment set as checksum?
So maybe that's what tells it checksum internally?
& yeah edit time isn't long enough!!!!
So maybe that's what tells it checksum internally?
& yeah edit time isn't long enough!!!!
by TazzI » Thu May 24, 2012 12:30 pm
tp5 will require the checksum to be calulated.
0xF7 0x58 0x04 0x81 0x00 0x2C
Using VL's program, only need to send 0xF7 0x58 0x04 0x81 0x00
I haven't attempted tuning my vy yet, think ill have to scrub up on what to do/what does what.
So F7 is the PCM, assuming you get the information from it then edit? What sort of things can you edit/tune?.. Will research it later tonight.
In the mean time iv made a little macro in vb for excel to filter a log taken, if a message reoccurs more then once, it simply adds to a counter.
This is my stand in program till I get this realtime logging filter program up. (may be a while)
0xF7 0x58 0x04 0x81 0x00 0x2C
Using VL's program, only need to send 0xF7 0x58 0x04 0x81 0x00
I haven't attempted tuning my vy yet, think ill have to scrub up on what to do/what does what.
So F7 is the PCM, assuming you get the information from it then edit? What sort of things can you edit/tune?.. Will research it later tonight.
In the mean time iv made a little macro in vb for excel to filter a log taken, if a message reoccurs more then once, it simply adds to a counter.
This is my stand in program till I get this realtime logging filter program up. (may be a while)