|
nyet
|
 |
« Reply #30 on: January 21, 2011, 12:32:01 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.)
Its a known problem with tuner pro switch it from 512x1 to 1x512 and it won't crash |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
nyet
|
|
« Reply #31 on: January 21, 2011, 12:34:59 PM »
|
|
|
Hiya. It's the RPM axis in the timing maps. Some maps use 8bit axis and some use 16 bit rpm axis.
I'll put together a matrix of ME7 timing map name and the axis locations for the M box.
For starters, in the M ecu, KFZW and KFZW2 have axis at file offsets:
X axis: 0x100FF
Y axis: 0x100C2
Spen have you found any other discrepancies. For example, KFZOP/OP2, KFZWMS (all were using 12b04) these are adjacent to the map, so i assume they are ok: DZWTIN (was using 15222) KFZWMN (was using 16b0c) KFZWMNST (was using 16bf4) KFSZT (was using 1a417) I assume scale/offset is 40/0 |
|
|
|
« Last Edit: January 21, 2011, 12:49:23 PM by nyet »
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
nyet
|
|
« Reply #32 on: January 22, 2011, 06:43:54 PM »
|
|
|
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
FR Wilk
Newbie
Karma: +1/-0
 Offline
Posts: 11
|
|
« Reply #33 on: February 11, 2011, 11:19:33 PM »
|
|
|
possible error?  KFZWWLNM X and Y address are the same? XAddress =0x10122 YAddress =0x10122 |
|
|
|
« Last Edit: February 12, 2011, 03:52:54 AM by FR Wilk »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #34 on: February 12, 2011, 04:13:47 PM »
|
|
|
possible error? KFZWWLNM X and Y address are the same? XAddress =0x10122 YAddress =0x10122 Thank you! That definitely looks suspect. Does anbody have any idea what those should be? My guess would be Y = 10097 |
|
|
|
« Last Edit: February 12, 2011, 04:16:09 PM by nyet »
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
FR Wilk
Newbie
Karma: +1/-0
Offline
Posts: 11
|
|
« Reply #35 on: February 12, 2011, 06:11:15 PM »
|
|
|
Also, there are 4 maps "KFDLUR" at
10333
10373
103B3
103F3
There are another 4 that appear to have the same axis as the above.
1022A
1026A
102AA
102EA
Any ideas what they do? Names?
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #36 on: February 12, 2011, 08:41:38 PM »
|
|
|
Sort of pointless do go about it that way. There are thousands of maps. Deciphering what an unknown map does is silly compared to trying to locate a map that you know does something you want to change.
|
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
iznogoud
Full Member
Karma: +13/-0
Offline
Posts: 104
Learning junkie
|
|
« Reply #37 on: February 12, 2011, 08:53:35 PM »
|
|
|
(Glad to know this thread is not dormant.)
Nyet, I tried getting mesim. I think I emailed you about it. Now sure how to get this running or which of the files bundles to get. Help!
|
|
|
|
|
Logged
|
Audi S4 B5 2000 6sp Cactus Green
Audi A4 B6 Avant 1.8T 2001.5 5sp Santorin Blue
|
|
|
spen
Full Member
Karma: +43/-0
Offline
Posts: 112
|
|
« Reply #38 on: March 04, 2011, 07:25:29 AM »
|
|
|
Nyet
I'll check those axes for you. I had to take a break from the internet for a while hence the slow response.
Spen
|
|
|
|
|
Logged
|
|
|
|
spen
Full Member
Karma: +43/-0
Offline
Posts: 112
|
|
« Reply #39 on: March 04, 2011, 08:03:39 AM »
|
|
|
For example, KFZOP/OP2, KFZWMS (all were using 12b04)
KFZWOP rpm axis = SNM16OPUW, 16 words stating at 812B04 (axis length at 0x812B02 {program counter 0x805EF8}
KFZWOP2 is the same
these are adjacent to the map, so i assume they are ok:
DZWTIN (was using 15222) - 1d table scale at 0x815222 {program counter 0x8631A6}
KFZWMN (was using 16b0c) - Internal scales adjacent to the data -0x816B0C, 0x816B1C {program counter 0x88AACC}
KFZWMNST (was using 16bf4) - Internal scales adjacent to the data -0x816BF4, 0x816C04 {program counter 0x88AB76}
KFSZT (was using 1a417) - haven't found this one yet.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #40 on: March 04, 2011, 02:10:07 PM »
|
|
|
KFZWOP rpm axis = SNM16OPUW, 16 words stating at 812B04 (axis length at 0x812B02 {program counter 0x805EF8}
KFZWOP2 is the same
spen, thank you so much. I have changed my map pack. I don't know if i'll release an update just yet; i'll probably wait for a few more corrections first. OH and please look for KFZWMS  thanks in advance. |
|
|
|
« Last Edit: March 04, 2011, 02:22:40 PM by nyet »
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
Rick
|
|
« Reply #41 on: March 22, 2011, 02:32:51 PM »
|
|
|
Nyet,
rpm axis data for timing map in the last xdf you posted look like garbage?
Rick
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #42 on: March 22, 2011, 05:21:31 PM »
|
|
|
Nyet,
rpm axis data for timing map in the last xdf you posted look like garbage?
Rick
12b04 (SNM16OPUW)? Looks fine in winols, but the xdf is autogeneratead, perhaps there was a translation error. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
Rick
|
|
« Reply #43 on: March 23, 2011, 06:52:42 AM »
|
|
|
Probably, not looked at the .kp.
How much of a difference is there between the old incorrect axis values and incorrect?
Old one went from 400 to 6500rpm I think?
Rick
|
|
|
|
|
Logged
|
|
|
|
spen
Full Member
Karma: +43/-0
Offline
Posts: 112
|
|
« Reply #44 on: March 28, 2011, 07:25:09 AM »
|
|
|
Here is KFZWMS in xdf format for the M rom:
%%TABLE%%
000002 UniqueID =0x0
000100 Cat0ID =0x8
040005 Title ="Map with permanent latest possible ignition angle (KFZWMS)"
040011 DescSize =0x32
040010 Desc ="Map with permanent latest possible ignition angle"
040100 Address =0x11bb0
040150 Flags =0x301
040200 ZEq =0.750000 * X,TH|0|0|0|0|
040230 RangeLow =0.0000
040240 RangeHigh =255.0000
040300 Rows =0x10
040305 Cols =0xc
040320 XUnits ="%"
040325 YUnits ="Upm"
040330 ZUnits ="grad KW"
040350 XLabels =0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00
040352 XLabelType =0x1
040354 XEq =0.750000 * X,TH|0|0|0|0|
040360 YLabels =0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00,0.00
040362 YLabelType =0x1
040364 YEq =40.000000 * X,TH|0|0|0|0|
040505 XLabelSource =0x1
040515 YLabelSource =0x1
040600 XAddress =0x100ff
040610 XDataSize =0x1
040620 XAddrStep =1
040650 XOutputDig =0x0
040660 XAxisMin =1000.000000
040670 XAxisMax =1000.000000
040700 YAddress =0x100c2
040710 YDataSize =0x1
040720 YAddrStep =1
040750 YOutputDig =0x0
040760 YAxisMin =1000.000000
040770 YAxisMax =1000.000000
%%END%%
The other axis which Rick says is garbage, isn't. The data is wide, and I suspect the full xdf has it as bytes.
Spen
|
|
|
|
|
Logged
|
|
|
|
|
