technovative
October 26th, 2010, 09:25 PM
I've determined that the A256 DATA Stream Specifications apply to my car but I'm not quite sure how to use the specs to crerate a defintion file. I'm mainly interested in being able to retrieve DTC's.
In the specs $E4 is indicated as the Message ID, is that what I should enter as the Module ID in the def file?
I created a Request named ALDL0 I noticed that the Request frame is automatically generated based on the Module ID entered, do I need to enter any parameters?
According to the specs:
..HEAD03L NUMBER OF DATA WORDS - 21
..HEAD04L ALDL MODE 1 MESSAGE 2 RESPONSE
WORD# DATA NAME DESCRIPTION
1 NOMALFCT MALFUNCTION COUNTER
2 DGSFLHY0 HISTORY DIAGNOSTIC CODES BYTE 0
0 NOT USED
1 NOT USED
2 NOT USED
3 NOT USED
4 MALF CODE 98 INVALID PCM PROGRAM
5 MALF CODE 75 EGR1 SOLENOID ERROR
6 MALF CODE 76 EGR2 SOLENOID ERROR
7 MALF CODE 77 EGR3 SOLENOID ERROR
So would the start byte for this attribute be 0?
In the specs $E4 is indicated as the Message ID, is that what I should enter as the Module ID in the def file?
I created a Request named ALDL0 I noticed that the Request frame is automatically generated based on the Module ID entered, do I need to enter any parameters?
According to the specs:
..HEAD03L NUMBER OF DATA WORDS - 21
..HEAD04L ALDL MODE 1 MESSAGE 2 RESPONSE
WORD# DATA NAME DESCRIPTION
1 NOMALFCT MALFUNCTION COUNTER
2 DGSFLHY0 HISTORY DIAGNOSTIC CODES BYTE 0
0 NOT USED
1 NOT USED
2 NOT USED
3 NOT USED
4 MALF CODE 98 INVALID PCM PROGRAM
5 MALF CODE 75 EGR1 SOLENOID ERROR
6 MALF CODE 76 EGR2 SOLENOID ERROR
7 MALF CODE 77 EGR3 SOLENOID ERROR
So would the start byte for this attribute be 0?