Request IDs from 00 to 3F
Request IDs from 00 to 3F
Request IDs from 00 to 3F
Values on my car before I started it up and definition if known:
00 22
01 46
02 e4
03 00
04 19
05 3d
06 51 Timing
07 85 Coolant
08 8c
09 85
0a 8c
0b 85
0c 80 F Trim
0d 9e F Trim - had some meth in the tank
0e 80 F Trim
0f 80 O2 fb
10 3b
11 3d
12 3b EGR temp
13 00 O2
14 a2 Bat
15 cc Barom
16 56 ISC
17 24 TPS
18 20
19 00
1a 00 Airflow
1b 7e
1c 00
1d 00 Accel
1e 30
1f 00
20 00
21 00 RPM
22 40
23 01
24 a7
25 56
26 00 Knock
27 ff Octane
28 1d
29 00 IPW
2a 00
2b 00
2c 00
2d 43
2e 00
2f 00
30 00
31 80
32 80
33 19
34 00
35 24
36 00
37 00
38 4b
39 02
3a 80 AIT
3b 00
3c 00
3d 00
3e 00
3f 00
Values on my car before I started it up and definition if known:
00 22
01 46
02 e4
03 00
04 19
05 3d
06 51 Timing
07 85 Coolant
08 8c
09 85
0a 8c
0b 85
0c 80 F Trim
0d 9e F Trim - had some meth in the tank

0e 80 F Trim
0f 80 O2 fb
10 3b
11 3d
12 3b EGR temp
13 00 O2
14 a2 Bat
15 cc Barom
16 56 ISC
17 24 TPS
18 20
19 00
1a 00 Airflow
1b 7e
1c 00
1d 00 Accel
1e 30
1f 00
20 00
21 00 RPM
22 40
23 01
24 a7
25 56
26 00 Knock
27 ff Octane
28 1d
29 00 IPW
2a 00
2b 00
2c 00
2d 43
2e 00
2f 00
30 00
31 80
32 80
33 19
34 00
35 24
36 00
37 00
38 4b
39 02
3a 80 AIT
3b 00
3c 00
3d 00
3e 00
3f 00
PID 04 - Get Calculated Load - send string ‘010406’
Receive 13 bytes
Returns one byte response in location 12-13 of received data
Calculated load% = b/255*100
I got this off attached document, hope it helps.
Receive 13 bytes
Returns one byte response in location 12-13 of received data
Calculated load% = b/255*100
I got this off attached document, hope it helps.
Hmm, the two we need to find are calculated load and air mass.. We have the OBD-II pids, but it doesn't correlate to the order of the MUT Codes..
My car idles with 20% load on my old OBD-II scanner, perhaps you can look for a value that represents 20%? Probably be something like 15 or 14 hex..
My car idles with 20% load on my old OBD-II scanner, perhaps you can look for a value that represents 20%? Probably be something like 15 or 14 hex..
Hmm, another thought is load may be harder to calculate since it may be dependent on your axis definition (from 10-260 or 0-260) etc... Since its in increments of 10, it may "Drop the zero" in its representation of load value..
I think on our car, the load can be a value in excess of 100%.. just as our mapping shows for the axis.. Oh who knows, I'm too tired to think logically...
I think on our car, the load can be a value in excess of 100%.. just as our mapping shows for the axis.. Oh who knows, I'm too tired to think logically...
Trending Topics
A lot of the scalings are similar to the scalings used in the ECU, and thankfully we have a lot of byte definitions which helps my small brain over words or longs.
A load measurement will I think probably not be constrained to the contents of your load table - if it goes beyond the ends it will probably just use the last column like most MAF based ECUs do in this situation.
My OBD logger clipped at 100% load unfortunately.
The dream would be to also find say the high byte of the airflow signal - I'll be watching &H19 over 5000 RPM.
Neither of my immobiliser bytes are in this section, but of note I just plugged in a JDM GSR ECU and it runs my car - like a standalone would.
A load measurement will I think probably not be constrained to the contents of your load table - if it goes beyond the ends it will probably just use the last column like most MAF based ECUs do in this situation.
My OBD logger clipped at 100% load unfortunately.
The dream would be to also find say the high byte of the airflow signal - I'll be watching &H19 over 5000 RPM.
Neither of my immobiliser bytes are in this section, but of note I just plugged in a JDM GSR ECU and it runs my car - like a standalone would.
Originally Posted by MalibuJack
Can you PM me the value in the Immobilizer table? I'm curious if thats the "Universal" key..
Any success with that Jack? I'd try it if I could get it in a PM.
I've looked for the immobilizer code all the way up through about 0xc?. I stopped when I turned the engine fan on.
I kinda got scared to try any more. I didn't find any codes that matched on my Ebay ECU.I was going to log and post all the initializations of all the points but the logger doesn't log the custom data by default. I'm not sure if it can.
I have the code, I have to test it on my spare ECU.. Bench harness isn't done yet
It looks like a plain old immobilizer code though... so I have to actually try it.
The other codes are request ID's.. He posted a file that will let you log all of them so we can correlate the data to useful info..
It looks like a plain old immobilizer code though... so I have to actually try it.The other codes are request ID's.. He posted a file that will let you log all of them so we can correlate the data to useful info..
Originally Posted by MalibuJack
The other codes are request ID's.. He posted a file that will let you log all of them so we can correlate the data to useful info..
I'm aware of that. I was running through all of the request ID's looking for the immobilizer code. When I got into the 0xC? range it started to cycle relays. Not only did it startle me when I turned my fan on(with the key in the ON position but the engine not running) but I decided to stop looking at that point. I wasn't sure what effect the codes may have. That open source DSM logger site that you posted mentioned some codes in the 0xF? range that cycle some relays when the ignition is ON but not started. Supposedly they do not cycle the relays when the car is started, they simply return 0xFF.
jcsbanks, I have noticed that you have spent quite a bit of time researching the requests and I would like to bump for an update on what you have found. I would post what I have but it amounts to bubcas from lack of time due to work, 4 kids and my only laptop is used by my wife for her web site/buisness pretty much throughout the evening, rendering my play time with the laptop about nil til I save to buy another.



