qoncept wrote:Alright, anyone care to give me a quick crash course (or point me to something that'll explain it) in reading these hex values? I'm trying to make a spreadsheet that looks something like what you'd see in a tuning app for main ignition. The RPM was easy enough, but I'm confused on load.
For RPM, spiider listed 293AA-293C7 on a 2004 rom. 293AA through 293AD are 10 00 18 00 respectively. So do I skip every other block? I figured when I got to load it'd have 00 every other block again, but it doesn't, and I'm not getting a consistent change in values by going through them like I expected, either way.
Sorry I'm such a newb but I don't really know where to look.
Spiider was kind enough to show the translation of LOAD data in the OEM image:
0E 14 19 9A 25 1F 30 A4 39 9A 42 8F 4A E1 53 33 5C 29 65 1F 6B 85 71 EC 79 9A 7E B8"
Translates to:
0.44 0.80 1.16 1.52 1.80 2.08 2.34 2.60 2.88 3.16 3.36 3.56 3.80 3.96 (air per cylinder charge in grams)
So when I analyze a few of those values (the decimal places are just a copy and paste from the Windows Calculator utility, I know that they are obviously not all significant digits
) as follows:
0x0E14= 3604 (base10); 0.44/3604 = .00012208657047724750277469478357381
0x4AE1 = 19169(base10); 2.34/19169 = .00012207209557097396838645730085033
0X7EB8= 32440(base10); 3.96/32440 = 0.000122071516646115906288532675709
Therefore it is clear that the hex values are 0 based (i.e. 0 means 0 grams air / cylinder charge), and they scale by 1 = 0.000122 grams air / cylinder charge.
So 0x0001 = 0.000122 grams air / cylinder charge, and 0x0002 = 0.000244 grams air / cylinder charge, etc.
HTH!
Adrian