Pages: [1] 2 3
Author Topic: Underscaled MAF = Underscaled rl_w question about ignition  (Read 20572 times)
bbernd
Guest
« on: April 10, 2013, 01:40:57 AM »

Hi, to get into the underscaled MAF stuff, I did some runs with only underscaled MAF on F-Box without changing anything else but undercaled MAF + adjust fueling like mentioned by prj in another posting. Just to learn from it step by step.

After a short log, I recognized the expected result on rl_w.

With stock MAF curve rl pretty quick hits 191,7 on VCDS so you get to the last column in KFZW.

With underscaled MAF rl stays much longer on lower values and does not hit 191,7 anymore. Maybe with more boost it will.

So the timing table runs totally off, because the real amount of air in cylinders is higher than the calculated load signal. So this will result in to much timing for the real load points if do not change the entire timing table. (remember stock file only MAF scale)

I wonder nobody ever mentioned the effects from downscaling MAF on ingintion maps - or am I missing something?

Are there more side effects?


 Embarrassed
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #1 on: April 10, 2013, 02:23:40 AM »

Why not scale the maf so max load is always right around 191? That way you're using the entire map, not just parts of it? There are degrees of underscaling, you can tailor it to your own requirements.
Logged

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 experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
bbernd
Guest
« Reply #2 on: April 10, 2013, 03:28:13 AM »

I know but if I modify the ecu with more boost and scale the MAF to a range of 0 - 191,7 the real rl will be f.e. 0-250.

So at rescaled rl 140 the real rl will be f.e. 191,7

So if I leave the KFZW/2 stock (only for example) I will get to much timing on mid range load areas.

Top rpm Timing at 140 load:
19,500
19,500
22,500
24,750
23,250

Top rpm Timing at 200 load:
6,000
8,250
10,500
11,250
9,750

So I get 23,250 deg at real load 200 instead of 9,750 cause ecu thinks it is only 140

I can see this behavior on VCDS because the ecu starts pulling timing via knock control with rescaled maf
Logged
prj
Hero Member
*****

Karma: +1072/-481
Offline Offline

Posts: 6038


« Reply #3 on: April 10, 2013, 04:13:58 AM »

So don't scale the MAF, and use 16 bit axes for ignition.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
bbernd
Guest
« Reply #4 on: April 10, 2013, 04:28:39 AM »

So don't scale the MAF...

Now I'm confused...
Logged
NOTORIOUS VR
Administrator
Hero Member
*****

Karma: +58/-7
Offline Offline

Posts: 1056


« Reply #5 on: April 10, 2013, 06:36:09 AM »

If you are maxing out the MAF and underscale, even turning up the boost will not help... 5V is the max the MAF will "see"
Logged

SCHNELL ENGINEERING BLOG ·  STANDALONE ECUS · TUNING · DYNO · WIRING · PARTS · VEMS
Google Talk: NOTORIOUS.VR
n00bs start here: http://s4wiki.com/wiki/Tuning
bbernd
Guest
« Reply #6 on: April 10, 2013, 09:07:43 AM »

If you are maxing out the MAF and underscale, even turning up the boost will not help... 5V is the max the MAF will "see"

this is clear..  the MAF is not maxed out, its just underscaled. Like to prevent to hit max rl_w. 

The question is not if it is right or wrong to do this, its only about understanding the relations.

the only question is - if somebody is underscaling his maf, does he only scale KFLF at the same time as mentioned:

http://nefariousmotorsports.com/forum/index.php?topic=2747.0 and on S4WIKI

because I see, it will harm correct timing by reading the wrong columns in KFZW/2 etc.

so there is a lot more to do - right?  cheers  Wink
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #7 on: April 10, 2013, 09:12:01 AM »

You have to tune timing near the top of the load range anyway... if anything, underscaling near the max gives you a few more cells to play with.

Be advised, though, I ran into an odd problem with underscaling on one car (still dont know why)

http://nefariousmotorsports.com/forum/index.php?topic=3562.0title=
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
jibberjive
Hero Member
*****

Karma: +23/-2
Offline Offline

Posts: 536


« Reply #8 on: April 11, 2013, 08:24:04 PM »

So, is the only way to be able to break the 191 rl_w limit and have a fully scaled MAF by doing the 5120 hack?  This is assuming that the car is hitting the limit, of course.
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12270


WWW
« Reply #9 on: April 11, 2013, 08:38:22 PM »

the 5120 limit is only good for ps_w.

to break the 191 rl limit you need RS4 or ME7.1.1
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
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #10 on: April 11, 2013, 08:46:55 PM »

the 5120 limit is only good for ps_w.

to break the 191 rl limit you need RS4 or ME7.1.1

What are we talking in terms of the rs4 limits? I hear a lot of talk about a 16bit load axis in the m-box, but haven't seen it implemented.

Just curious.
Logged

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 experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
jibberjive
Hero Member
*****

Karma: +23/-2
Offline Offline

Posts: 536


« Reply #11 on: April 11, 2013, 09:21:30 PM »

the 5120 limit is only good for ps_w.

to break the 191 rl limit you need RS4 or ME7.1.1
Admittedly, I haven't delved much into the specifics of the 5120 mod yet.  So that in no way resolves the 191 rl_w cap then?  And if one were to make the load axes of the m-box 16bit, that still wouldn't resolve the 191 limit, would it?  Isn't the limit based on the variables, and not the axes?
Logged
matchew
Hero Member
*****

Karma: +47/-22
Offline Offline

Posts: 503


« Reply #12 on: April 11, 2013, 09:36:41 PM »

rl_w is NOT limited to 181
Logged
jibberjive
Hero Member
*****

Karma: +23/-2
Offline Offline

Posts: 536


« Reply #13 on: April 11, 2013, 10:10:48 PM »

rl_w is NOT limited to 181
Actually I should have known that, as all of the _w variables are 16 bit, right?  So what is the root of the 191 limit with the m-box then, as the axes of corresponding maps don't actually limit load, they will just use the highest value for anything above 191? I will have to review all of the 191 limit threads shortly, so excuse my ignorance if it's clearly worked out already in those threads.
Logged
catbed
Sr. Member
****

Karma: +8/-2
Offline Offline

Posts: 300


« Reply #14 on: April 11, 2013, 10:52:41 PM »

Actually I should have known that, as all of the _w variables are 16 bit, right?  So what is the root of the 191 limit with the m-box then, as the axes of corresponding maps don't actually limit load, they will just use the highest value for anything above 191? I will have to review all of the 191 limit threads shortly, so excuse my ignorance if it's clearly worked out already in those threads.

It was my understanding that KFZW/2 had axes limited to 191. So you could not tune ignition timing with loads >191, and it would just use the value found in the last column of the table. Only ways to circumvent this is to use RS4 flash, or change the axes to 16bit.
« Last Edit: April 11, 2013, 10:54:39 PM by catbed » Logged
Pages: [1] 2 3
  Print  
 
Jump to:  

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