iznogoud
Full Member
Karma: +13/-0
 Offline
Posts: 104
Learning junkie
|
 |
« Reply #15 on: November 10, 2010, 05:08:45 PM »
|
|
|
Some maps do share the same axis data.
Yes, that I can understand. But there is a difference between sharing a unique map, or have two different axes-maps that are identical in terms of their contents but are found in different locations. With my brute-force naive searching there is no way to distinguish between the two. I can write a piece of code that takes maps that have the same axis-map data and see if the incidences are the same (in terms of how many those map pairs or triplets, etc, are). But there is no way of associating any axis-map with any particular map that uses it from the definitions. I think that is where the assembly should be helpful. Anyway, I will take this as far as I can with this conventional thinking and we'll go from there. |
|
|
|
« Last Edit: November 10, 2010, 05:11:10 PM by iznogoud »
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
torch
Newbie
Karma: +2/-0
Offline
Posts: 5
|
|
« Reply #16 on: November 11, 2010, 07:16:13 AM »
|
|
|
I ran into this same thing in my Mitsubishi days. There are multiple maps with the same data (AFR in that case) and no indication as to which was being used. With our quick flashing tools from Tony, we can find them the same way I used to. Just zero the map out. If it was being used you can tell pretty rapidly. This obviously won't work for accumulated data maps, but I think you get my point. Granted, in the Mitsubishi there were only like 5 AFR and a few timing maps to hack with, but what's the fun of a simple system?
Matt
|
|
|
|
|
Logged
|
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #17 on: November 11, 2010, 03:28:42 PM »
|
|
|
I will modify tp.c to uniquely identify the axes-maps. We can make changes systematically and have somebody with a simulator run the bin file. It can get tedious but it is a input-output way of reverse engineering this.
|
|
|
|
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #18 on: November 12, 2010, 09:22:17 AM »
|
|
|
I do not know how helpful this is, but it shows that several maps share axes-maps.
|
|
|
|
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
|
nyet
|
|
« Reply #19 on: November 14, 2010, 07:56:26 PM »
|
|
|
my mesim project parses bins with my xdf/map locations fine.
For example, it can read a bin file and extract min/max from every table...
whatever you are doing to parse the bin, your code is probably doing it wrong.
pointer arithmetic, or lack of proper ntohl/htonl/ntohs/htons
|
|
|
|
|
Logged
|
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #20 on: November 14, 2010, 09:39:24 PM »
|
|
|
The code is posted above. It does not look at the data (no conversion or casting) so it only does addressing. I double-checked the data it extracts for each of the tables and looked at that address location in the bin with a hexeditor and those match fine.
I am saying that the XDF I am using, which is yours, has some minor issues here and there. Like for example the last map is pointing to a blank spot of FF FF FF...
I am not claiming that I know what is going on. I am basing all of this off your work! There has got to be an error in that tp.c code. I will find it.
|
|
|
|
« Last Edit: November 14, 2010, 09:43:38 PM by iznogoud »
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #21 on: November 14, 2010, 09:58:03 PM »
|
|
|
Double-checked a few maps of my output with what hex values TunerPro shows. Attached is a screen grab showing the first table and the last map that I think is problematic. You can see on the title bar which files are loaded. I may just have bad files. Something is up nonetheless.
|
|
|
|
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
|
nyet
|
|
« Reply #22 on: November 15, 2010, 05:26:10 PM »
|
|
|
--> "Linearization of MAF voltage" <--
Cols (X) = 512 , Rows (Y) = 1
Xaddress = 0x0 (0)
Xsize in bytes: 1024
Xdata: ffd8 ffe0 0010 4a46 4946 0001 0101 00f0 00f0 0000 ffed 160e 5068 6f74 6f73 686f 7020 332e 3000 3842 494d 0404 0000 0000 002c 1c01 5a00 031b 2547 1c02 0000 0200 001c 0219 0016 5072 6f66 6573 7369 6f6e 616c 2070 686f 746f 7320 5334 0000 3842 494d 0425 0000 0000 0010 44e6 b4a2 e3ba a66e e247 b86f 102a 57df 3842 494d 03ed 0000 0000 0010 00f0 0000 0001 0001 00f0 0000 0001 0001 3842 494d 0426 0000 0000 000e 0000 0000 0000 0000 0000 3f80 0000 3842 494d 040d 0000 0000 0004 0000 001e 3842 494d 0419 0000 0000 0004 0000 001e 3842 494d 03f3 0000 0000 0009 0000 0000 0000 0000 0100 3842 494d 2710 0000 0000 000a 0001 0000 0000 0000 0001 3842 494d 03f5 0000 0000 0048 002f 6666 0001 006c 6666 0006 0000 0000 0001 002f 6666 0001 00a1 999a 0006 0000 0000 0001 0032 0000 0001 005a 0000 0006 0000 0000 0001 0035 0000 0001 002d 0000 0006 0000 0000 0001 3842 494d 03f8 0000 0000 0070 0000 ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff 03e8 0000 0000 ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff 03e8 0000 0000 ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff 03e8 0000 0000 ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff ffff 03e8 0000 3842 494d 0400 0000 0000 0002 0001 3842 494d 0402 0000 0000 0004 0000 0000 3842 494d 0430 0000 0000 0002 0101 3842 494d 042d 0000 0000 0006 0001 0000 0002 3842 494d 0408 0000 0000 0010 0000 0001 0000 0240 0000 0240 0000 0000 3842 494d 041e 0000 0000 0004 0000 0000 3842 494d 041a 0000 0000 0345 0000 0006 0000 0000 0000 0000 0000 0a20 0000 0f20 0000 0008 005f 004d 0053 0050 0030 0030 0034 0038 0000 0001 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 0000 0000 0000 0000 0000 0f20 0000 0a20 0000 0000 0000 0000 0000 0000 0000 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 0000 1000 0000 0100 0000 0000 006e 756c 6c00 0000 0200 0000 0662 6f75 6e64 734f 626a 6300 0000 0100 0000 0000 0052 6374 3100 0000 0400 0000 0054 6f70 206c 6f6e 6700 0000 0000 0000 004c 6566 746c 6f6e 6700 0000 0000 0000 0042 746f 6d6c 6f6e 6700 000a 2000 0000 0052 6768 746c 6f6e 6700 000f 2000 0000 0673 6c69 6365 7356 6c4c 7300 0000 014f 626a 6300 0000 0100 0000 0000 0573 6c69 6365 0000 0012 0000 0007 736c 6963 6549 446c 6f6e 6700 0000 0000 0000 0767 726f 7570 4944 6c6f 6e67 0000 0000 0000 0006 6f72 6967 696e 656e 756d 0000 000c 4553 6c69 6365 4f72 6967 696e 0000 000d 6175 746f 4765 6e65 7261 7465 6400 0000 0054 7970 6565 6e75 6d00 0000 0a45 536c 6963 6554 7970 6500 0000 0049 6d67 2000 0000 0662 6f75 6e64 734f 626a 6300 0000 0100 0000 0000 0052 6374 3100 0000 0400 0000 0054 6f70 206c 6f6e 6700 0000 0000 0000 004c 6566
That doesn't look like 14254 at all |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #23 on: November 15, 2010, 05:27:13 PM »
|
|
|
Double-checked a few maps of my output with what hex values TunerPro shows. Attached is a screen grab showing the first table and the last map that I think is problematic. You can see on the title bar which files are loaded. I may just have bad files. Something is up nonetheless.
That last table is unused in M-Box |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #24 on: November 15, 2010, 05:28:57 PM »
|
|
|
The code is posted above. It does not look at the data (no conversion or casting)
for 16 and 32 bit values, you will have to (at least) be endian aware. |
|
|
|
|
Logged
|
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #25 on: November 15, 2010, 06:09:15 PM »
|
|
|
The code is posted above. It does not look at the data (no conversion or casting)
for 16 and 32 bit values, you will have to (at least) be endian aware. Correct. This file seems to be LSB (little endian) by looking at what I am picking up and what TunerPro shows on the HEX mode of the tables (what I have in the image above). This is for the actual maps, so I am certain I am getting those axes read correctly. I will look at mesim again. (I did not know about that unused map.) |
|
|
|
« Last Edit: November 15, 2010, 06:20:59 PM by iznogoud »
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #26 on: November 15, 2010, 06:13:09 PM »
|
|
|
--> "Linearization of MAF voltage" <--
Cols (X) = 512 , Rows (Y) = 1
Xaddress = 0x0 (0)
Xsize in bytes: 1024
Xdata: ffd8 ffe0 0010 4a46 4946 00
That doesn't look like 14254 at all That is a special map that does not have Axes data. Get the latest tp.c and re-run it. I think that section of the printout is not relevant anyway. The HTML files that are generated are the important ones. I re-run it again. The tp.c I am using recognizes that there is something special about that map and just treats it as a 1D array for the 256 values. Here is my printout: ---------------------------------------
Table: 17
Title: "Linearization of MAF voltage"
SizeInBits: 16
Address: 0x14254 (82516)
Rows: 0x1 (1)
Cols: 0x200 (512)
========================================
= There may be a problem with this map =
= No X/Y data map addresses detected. =
= Assuming 1D array... =
========================================
---------------------------------------
The one you were running uses the "default value" for XAddress which is 0x0 and so it reads crap from the top of the file. I fixed that sometime ago; it fooled me once. |
|
|
|
« Last Edit: November 15, 2010, 06:22:49 PM by iznogoud »
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
|
nyet
|
|
« Reply #27 on: November 16, 2010, 04:43:12 PM »
|
|
|
The one you were running uses the "default value" for XAddress which is 0x0 and so it reads crap from the top of the file. I fixed that sometime ago; it fooled me once.
Aha! Good find! Ok that makes sense. How should one encode "no axis data" in an xdf record? I can fix up my xdf to do that as well. No wonder this xdf crashes tuner pro when you open this table... |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #28 on: November 16, 2010, 04:48:47 PM »
|
|
|
oh, never mind.
my .xdf actually is correct (that i can tell), it uses hard coded xaxis lables (512 of them) and XLabelType = 2
|
|
|
|
|
Logged
|
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #29 on: November 16, 2010, 09:59:43 PM »
|
|
|
Will dig into it again. TunerPro consistently crashed on that map for me.
(Edit) I noticed in the past that when the labels are there TunerPro is happy reading it, but still crashes.
(Had zero seconds to breathe today and now I am spent and ready for bed.)
|
|
|
|
« Last Edit: November 16, 2010, 10:02:01 PM by iznogoud »
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
|
