Pages: 1 [2] 3 4 ... 26
Author Topic: MED 9.1 basics  (Read 318862 times)
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #15 on: February 18, 2014, 10:20:24 AM »

At some point, many things are just unitless scalars, or used in calculations where the result are some other units where the "natural" unit doesn't make sense because of another scaler (say pi or something - radians vs degrees, etc), or they are inverse units.

So in many case the "meaning" of the value in the CPU may not directly align with any sort of units or scaling that makes sense to you..
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please 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
dream3R
Hero Member
*****

Karma: +18/-8
Offline Offline

Posts: 1194


« Reply #16 on: February 18, 2014, 10:42:19 AM »

At some point, many things are just unitless scalars, or used in calculations where the result are some other units where the "natural" unit doesn't make sense because of another scaler (say pi or something - radians vs degrees, etc), or they are inverse units.

So in many case the "meaning" of the value in the CPU may not directly align with any sort of units or scaling that makes sense to you..

Quite, but the code can't be too different, it still ends's up as the same variable after coming from the same ad convertor and same cpu..

Logged



How to work out values from an A2L Smiley

http://nefariousmotorsports.com/forum/index.php?topic=5525.msg52371#msg52371


Starting Rev's http://nefariousmotorsports.com/forum/index.php?topic=5397.msg51169#msg51169

noobs read this before asking http://nefariousmotorsports.com/forum/index.php?topic=9014.0title=


ORGORIGINAL 05 5120 creator for Volvo
ORIGINAL Datalogger (Freeware) Author
ORGINAL finder of the 'extra' torque' limits
I don't have ME7.01 A2L I just use ID
Basano
Full Member
***

Karma: +90/-3
Offline Offline

Posts: 192


« Reply #17 on: February 19, 2014, 02:33:03 AM »

Added x3 LAMFA maps

BGFAWU
1D6886LAMFA
1D68FELAMFA
1D6976LAMFA

I noticed that even in the defined WinOLS that I'm using as a reference, the values looked a bit strange. The Y-Axis peaks in the centre which can't be correct Huh



After a bit of searching, I found a suggestion about moving an axis and table by one byte:

Increment Y-Axis Start Address by one byte (from 0x1D6879 to 0x1D687A)
Increment Map Start Address by one byte (from 0x1D6885 to 0x1D6886)



Looked a lot better after that Smiley Has anyone else come across this?

Logged
dream3R
Hero Member
*****

Karma: +18/-8
Offline Offline

Posts: 1194


« Reply #18 on: February 19, 2014, 05:48:36 AM »

Is that not the infamous Winols bug that's in 'older' versions?
Logged



How to work out values from an A2L Smiley

http://nefariousmotorsports.com/forum/index.php?topic=5525.msg52371#msg52371


Starting Rev's http://nefariousmotorsports.com/forum/index.php?topic=5397.msg51169#msg51169

noobs read this before asking http://nefariousmotorsports.com/forum/index.php?topic=9014.0title=


ORGORIGINAL 05 5120 creator for Volvo
ORIGINAL Datalogger (Freeware) Author
ORGINAL finder of the 'extra' torque' limits
I don't have ME7.01 A2L I just use ID
overspeed
Sr. Member
****

Karma: +21/-5
Offline Offline

Posts: 387



« Reply #19 on: February 19, 2014, 06:03:21 AM »

My advise, use DAMOS as an orientation... if you look closer you´ll find a bunch of another weird things in some maps.


Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Offline Offline

Posts: 12268


WWW
« Reply #20 on: February 19, 2014, 09:51:08 AM »

Is that not the infamous Winols bug that's in 'older' versions?

Not sure, but there are a lot of DAMOS's OLS's that have 16 bit map locations that are not 16 bit aligned (and thus wrong)
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please 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
Basano
Full Member
***

Karma: +90/-3
Offline Offline

Posts: 192


« Reply #21 on: March 04, 2014, 01:57:48 AM »

Hi all,

So I finally made some changes Cheesy Not very big ones, I'm still very new and it's more a question of changing one thing at a time and understanding the consequences. I haven't posted this in the tunes section of this forum since it's far from a tune!

This is MED9.1 on an Audi S3 2.0 TFSI (UK specification, manual gearbox).

Please bear with me, the tables are number-heavy and I've split things across several posts to make things a bit neater. I've changed just 3 maps:

KFMIRL
KFMIOP
LDRXN


Firstly, my stock values:

KFMIRL - stock

% / RPM5007008001000124015202000252030003520400045205000552060006520
4.000911.437510.945310.710910.21889.70319.30478.88288.62508.53138.50788.53138.50788.43758.27348.06257.8281
5.999815.726615.281315.070314.625014.109413.687513.171912.843812.656312.585912.562512.492212.351612.140611.906311.6250
8.000219.992219.617219.429718.984418.539118.070317.484417.039116.804716.687516.593816.453116.289116.031315.750015.4219
13.999932.718832.601632.554732.367231.828131.171930.304729.671929.250028.921928.664128.359428.031327.656327.281326.8359
19.999745.421945.304745.234445.046944.695344.109443.148442.351641.765641.203140.710940.218839.750039.257838.789138.2500
30.000366.656366.375066.234466.000065.859465.320364.335963.398462.531361.453160.539159.742259.156358.617258.101657.5391
39.999488.125087.539187.257886.742286.296986.015685.101683.835982.570381.257880.179779.335978.796978.304777.906377.5313
50.0000109.9922109.4766109.1953108.7031108.1406107.5781106.2891104.4609102.7969101.3672100.335999.585999.210999.046999.070399.3281
60.0006132.3516131.9766131.8125131.4375130.9688130.3125128.8828126.7500124.6875122.9531121.7578121.0313120.8672121.1719121.8047122.8359
69.9997154.9453154.7344154.6172154.3594154.0313153.5625152.5078150.6328148.3828146.1797144.6563143.6953143.5781144.1641145.3594147.1875
80.0003177.6797177.5859177.5391177.4219177.2344176.9297176.0391174.4688172.3594170.0859168.3281167.1563166.9453167.5547168.7500170.4375
90.0009200.3203200.3672200.3906200.4141200.4141200.2969199.7109198.4219196.5234194.1797192.2109190.8281190.4531191.0391192.1875193.6172

KFMIOP - stock

% / RPM5007008001000124015202000252030003520400045205000552060006520
10.00783.32793.56603.68193.90174.13974.32284.52124.65394.71504.73334.73484.75164.80194.89655.01255.1498
15.00005.66255.86855.97086.17526.39956.59646.84667.02827.12597.17937.21137.26327.34417.47077.61117.7774
20.01568.01548.18338.27038.45798.66858.88529.18739.41319.54749.63599.70159.79009.903010.057110.223410.4172
35.015615.083315.132115.158115.231315.466315.771516.206416.537516.774016.983017.158517.363017.567417.797918.028318.2968
50.015622.163422.238222.277822.374022.514322.772223.223923.628223.956324.333224.675025.007625.286925.561525.822426.1215
65.015629.219129.345729.408329.518129.586829.859930.336030.798331.240831.797832.287632.699632.000233.271833.514433.7845
80.015636.233536.467036.581436.796636.956837.114037.550438.131738.722239.375339.920040.341240.600640.824940.998841.1514
100.007845.457545.719945.848146.089246.328746.531747.055147.856148.625249.321049.832250.199950.367750.439550.413550.2960
120.000054.498354.701254.800454.992755.221655.509956.140157.043557.905658.659459.193459.536759.610059.475759.204158.7906
150.000067.811667.923067.981068.098468.254168.472368.954569.752570.700171.620272.288572.717372.772272.511371.989471.2036
180.000081.025781.057781.076081.120381.192081.318781.668182.313583.160484.115684.886285.429485.553085.304384.799284.1278

LDRXN - stock

RPM1000150017501850200022502500300035004000450050005500600066006800
%100.0078118.0078125.0156130.0078140.0156172.0078172.0078172.0078172.0078172.0078175.0078175.0078175.0078168.0000158.0156100.0078

I used VCDS to log 4th gear pulls. What I'm mainly looking at here is specified and actual load. With the stock values in the tables above, this is the result I get. Ambient temperatures are nice and cool (about 5 degrees celsius in the evening) and this is all at sea level.

Specified load is 171. Actual load peaks at 191 (coincides with boost peak) and then settles down to follow specified load 171.

« Last Edit: March 04, 2014, 02:01:07 AM by Basano » Logged
Basano
Full Member
***

Karma: +90/-3
Offline Offline

Posts: 192


« Reply #22 on: March 04, 2014, 02:27:07 AM »

Now my changes.

Same again, here are the maps and I’ve marked what I’ve changed.

I spent much, much too much time worrying about the relationship between KFMIRL and KRMIOP. I read some amazing posts and I’m not going to go into it any further right now since it’s been covered elsewhere far better than I could do! Suffice it to say, KFMIRL values are raised slightly, KFMIOP axis is rescaled to match the increased values in KFMIRL and values in KFMIOP on the changed axis are interpolated accordingly. I believe it’s mathematically OK.

KFMIRL - v1

4.000911.437510.945310.710910.21889.70319.30478.88288.62508.53138.50788.53138.50788.43758.27348.06257.8281
5.999815.726615.281315.070314.625014.109413.687513.171912.843812.656312.585912.562512.492212.351612.140611.906311.6250
8.000219.992219.617219.429718.984418.539118.070317.484417.039116.804716.687516.593816.453116.289116.031315.750015.4219
13.999932.718832.601632.554732.367231.828131.171930.304729.671929.250028.921928.664128.359428.031327.656327.281326.8359
19.999745.421945.304745.234445.046944.695344.109443.148442.351641.765641.203140.710940.218839.750039.257838.789138.2500
30.000366.656366.375066.234466.000065.859465.320364.335963.398462.531361.453160.539159.742259.156358.617258.101657.5391
39.999488.125087.539187.257886.742286.296986.015685.101683.835982.570381.257880.179779.335978.796978.304777.906377.5313
50.0000109.9922109.4766109.1953108.7031108.1406107.5781106.2891104.4609102.7969101.3672100.335999.585999.210999.046999.070399.3281
60.0006132.3516131.9766131.8125131.4375130.9688130.3125128.8828126.7500124.6875122.9531121.7578121.0313120.8672121.1719121.8047122.8359
69.9997154.9453154.7344154.6172154.3594154.0313153.5625152.5078150.6328148.3828146.1797144.6563143.6953143.5781144.1641145.3594147.1875
80.0003179.6841179.4398179.2805179.0032178.9535179.1020178.9808177.8739175.6823172.8974170.8025169.3654169.1139169.7420171.2305173.4012
90.0009211.6003212.1133212.3823212.7985213.0964212.5937211.7293210.0845208.1243205.7168203.7935202.5029202.1585203.0555204.5441206.2987

KFMIOP - v1

% / RPM5007008001000124015202000252030003520400045205000552060006520
10.00783.32793.56603.68193.90174.13974.32284.52124.65394.71504.73334.73484.75164.80194.89655.01255.1498
15.00005.66255.86855.97086.17526.39956.59646.84667.02827.12597.17937.21137.26327.34417.47077.61117.7774
20.01568.01548.18338.27038.45798.66858.88529.18739.41319.54749.63599.70159.79009.903010.057110.223410.4172
35.015615.083315.132115.158115.231315.466315.771516.206416.537516.774016.983017.158517.363017.567417.797918.028318.2968
50.015622.163422.238222.277822.374022.514322.772223.223923.628223.956324.333224.675025.007625.286925.561525.822426.1215
65.015629.219129.345729.408329.518129.586829.859930.336030.798331.240831.797832.287632.699632.000233.271833.514433.7845
80.015636.233536.467036.581436.796636.956837.114037.550438.131738.722239.375339.920040.341240.600640.824940.998841.1514
100.007845.457545.719945.848146.089246.328746.531747.055147.856148.625249.321049.832250.199950.367750.439550.413550.2960
120.000054.498354.701254.800454.992755.221655.509956.140157.043557.905658.659459.193459.536759.610059.475759.204158.7906
160.000072.099972.170572.209272.298972.395172.559672.922373.577274.424375.353976.042376.512376.580776.322175.767874.9619
200.000086.956987.048787.118687.240087.226487.024286.884487.123587.714188.491889.060589.424689.515889.350789.023888.5631

« Last Edit: March 04, 2014, 02:28:39 AM by Basano » Logged
Basano
Full Member
***

Karma: +90/-3
Offline Offline

Posts: 192


« Reply #23 on: March 04, 2014, 02:32:10 AM »

LDRXN - v1

RPM1000150017501850200022502500300035004000450050005500600066006800
%100.0078118.0078125.0156130.0078145.0000175.0000198.0000198.0000198.0000198.0000198.0000198.0000198.0000170.0000158.0156100.0078

And here are the results. Conditions pretty much the same as the stock log (same time of day, similar temperatures, same stretch of road etc).

This time the specified load is higher at 191 and the actual load stays there as well. Specified and actual boost are higher as well (and still have that little spike at the beginning, same as stock)



If you've read down as far as here, thank you for staying with me  Cheesy My question is, why is specified load not any higher than 191, despite there being enough headroom in the maps? I did find some information here which looked relevant

LDRXN is basic max specified load. There's an additive for overboost if active, then factors for knock, IAT, oil temp, and coolant temp. These can all raise or lower max specified load rlmxko_w.

Then max PR is converted to load and limits rlmxko_w.

If there are errors in EGT sensors, IAT sensor, either CTS, or oil temp, then max pressure is converted to load and limits max specified load as well.

If lde exceeds KFDLDULS for a period of time, then max specified load is also limited to LDORXN.

Finally, there's an additive for adaptation channels (lemmi).

This final max specified load, rlmax, limits the output of KFMIRL.


I've got two maps I'm thinking of changing next (LDPBN and KFLDHBN) and was wondering if they'd affect the specified load. I know KFTARX could be a factor as well but my temperatures are pretty low.

Thanks!
« Last Edit: March 04, 2014, 02:43:08 AM by Basano » Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6035


« Reply #24 on: March 04, 2014, 03:53:22 AM »

Lower KFLDIMX to fix boost overshoot.
Load is irrelevant at this point as it is above diagnostic limit.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
oldcarguy85
Full Member
***

Karma: +15/-1
Offline Offline

Posts: 247


« Reply #25 on: March 04, 2014, 05:44:19 AM »

It's LDPBN for sure. Stock it's 2250 across the board. This equates to a little over 18psi which would easily equate to your 191 load. I changed this to 2550 across the board

I've been told LDPBN has a slightly different meaning in med9. By definition in me7 it's max pressure under error condition or something. In med9 I think it's just max pressure.

Logged
Basano
Full Member
***

Karma: +90/-3
Offline Offline

Posts: 192


« Reply #26 on: March 04, 2014, 06:28:34 AM »

Thanks all,

I think I've got three answers here.

1) Although the specified load value inside the ECU may indeed rise, the diagnostic protocol can only output a max value of 191.
2) Fix the boost spike by lowering KFLDIMX. I'll log the WGDC tonight and see what the steady state value converges to. I'll use that as a basis to start.
3) LDPBN. My specified boost in the logs seemed to settle around 2250, so I'll update LDPBN.

Once again, thanks for all the suggestions and replies. I could just have copied stuff but then I would not have understood what it was that I was copying Cheesy
Logged
BenR
Jr. Member
**

Karma: +2/-1
Offline Offline

Posts: 38


« Reply #27 on: March 06, 2014, 10:43:32 PM »

You changed the values in KFMIOP. Why not the axis in KFMIRL?
Logged
Basano
Full Member
***

Karma: +90/-3
Offline Offline

Posts: 192


« Reply #28 on: March 07, 2014, 03:36:24 AM »

Hi,

The axis in KFMIRL is torque. I don’t think it you can rescale the axis past 100% since that is WOT already. You can’t get more wide open than WOT 

From the s4wiki “make sure the 100% torque request (rtlsol) row requests enough load”

So I left the axis in KFMIRL alone and changed the values in the last two rows to request more load. I changed the last two rows to ramp up smoothly.

Then I looked at KFMIOP, I changed the axis in KFMIOP to reflect the new higher numbers in KFMIRL (>202) and then recalculated the last two rows in KFMIOP so that they aligned with the new axis.

I spent ages and ages playing with linear interpolation in excel to fit nice curves to everything.

I probably haven’t explained very well, but this was pretty comprehensive.
 

Logged
Basano
Full Member
***

Karma: +90/-3
Offline Offline

Posts: 192


« Reply #29 on: March 07, 2014, 04:36:17 AM »

I’m still struggling with that initial boost spike  Sad

I’ve done some logging and the graph is below.

1)   After the initial spike, actual boost tracks requested boost very nicely
2)   Requested boost is 2350mbar and the spike reaches about 2600mbar
3)   The spike lasts for about 500 rpm (2900 rpm  – 3400 rpm)
4)   WGDC starts at 95 % before settling down around 50 %



I think I’ve misunderstood what to do with KFLDIMX.

KFLDIMX – stock

hPa / RPM1000125015001750200022502500275030003500400045005000550060006500
0¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦5.0000¦10.0000¦10.0000¦10.0000¦10.0000¦10.0000¦10.0000
300¦19.0000¦19.0000¦19.0000¦19.0000¦19.0000¦19.0000¦16.8750¦15.0000¦14.0650¦17.1900¦21.2500¦21.7200¦22.1900¦23.1250¦25.0000¦26.8750
400¦25.3350¦25.3350¦25.3350¦25.3350¦25.3350¦25.3350¦22.5000¦20.0000¦18.7500¦21.2500¦25.0000¦25.6250¦26.2500¦27.5000¦30.0000¦32.5000
500¦31.6650¦31.6650¦31.6650¦31.6650¦31.6650¦31.6650¦28.1250¦25.0000¦23.4400¦25.3150¦28.7500¦29.5300¦30.3150¦31.8750¦35.0000¦38.1250
1000¦63.3350¦63.3350¦63.3350¦63.3350¦63.3350¦63.3350¦56.2500¦50.0000¦46.8750¦45.6250¦47.5000¦49.0650¦50.6250¦53.7500¦60.0000¦66.2500
1200¦76.0000¦76.0000¦76.0000¦76.0000¦76.0000¦76.0000¦67.5000¦60.0000¦56.2500¦53.7500¦55.0000¦56.8750¦58.7500¦62.5000¦70.0000¦77.5000
1500¦95.0000¦95.0000¦95.0000¦95.0000¦95.0000¦95.0000¦84.3750¦75.0000¦70.3150¦65.9400¦66.2500¦68.5950¦70.9400¦75.6250¦85.0000¦94.3750
1600¦95.0000¦95.0000¦95.0000¦95.0000¦95.0000¦95.0000¦90.0000¦80.0000¦75.0000¦70.0000¦70.0000¦72.5000¦75.0000¦80.0000¦90.0000¦95.0000

KFLDIMX – v8

hPa / RPM1000125015001750200022502500275030003500400045005000550060006500
0¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦0.0000¦5.0000¦10.0000¦10.0000¦10.0000¦10.0000¦10.0000¦10.0000
300¦19.0000¦19.0000¦19.0000¦19.0000¦19.0000¦19.0000¦16.8750¦15.0000¦14.0650¦17.1900¦21.2500¦21.7200¦22.1900¦23.1250¦25.0000¦26.8750
400¦25.3350¦25.3350¦25.3350¦25.3350¦25.3350¦25.3350¦22.5000¦20.0000¦18.7500¦21.2500¦25.0000¦25.6250¦26.2500¦27.5000¦30.0000¦32.5000
500¦31.6650¦31.6650¦31.6650¦31.6650¦31.6650¦31.6650¦28.1250¦25.0000¦23.4400¦25.3150¦28.7500¦29.5300¦30.3150¦31.8750¦35.0000¦38.1250
1000¦63.3350¦63.3350¦63.3350¦63.3350¦63.3350¦63.3350¦56.2500¦50.0000¦46.8750¦45.6250¦47.5000¦49.0650¦50.6250¦53.7500¦60.0000¦66.2500
1200¦76.0000¦76.0000¦76.0000¦76.0000¦76.0000¦76.0000¦67.5000¦60.0000¦56.2500¦53.7500¦55.0000¦56.8750¦58.7500¦62.5000¦70.0000¦77.5000
1500¦95.0000¦95.0000¦95.0000¦95.0000¦95.0000¦ 76.0000¦ 67.5000 ¦ 60.0000 ¦ 56.2500 ¦ 56.2500 ¦66.2500¦68.5950¦70.9400¦75.6250¦85.0000¦94.3750
1600¦95.0000¦95.0000¦95.0000¦95.0000¦95.0000¦ 76.0000¦ 67.5000 ¦ 60.0000 ¦ 56.2500 ¦56.2500¦70.0000¦72.5000¦75.0000¦80.0000¦90.0000¦95.0000

In general, you want KFLDIMX to follow what you expect your WGDC to be in the steady state, so after peak boost, you should set this to where you want the WGDC to settle.

I probably haven't understood this properly.

Am I reducing it in the right place? I've reduced just a small part of it, but should I be reducing the entire row instead of just a few entries?I've also been very conservative and just made small changes. Should I be taking the whole row down to around 50? I don't have a problem when it settles down, it's just the initial spike  Undecided




Logged
Pages: 1 [2] 3 4 ... 26
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.131 seconds with 17 queries. (Pretty URLs adds 0.002s, 0q)