|
elRey
|
 |
« on: April 13, 2012, 09:46:31 PM »
|
|
|
Has anyone else noticed that mrfa input wraps around to 0% column in LAMFA?
I've noticed that if my 0% column is set to 1 then when mrfa reaches ~95% it returns 1.
If I set 0% column to .8 then mfra > 95% it returns .8
Anyone else?
|
|
|
|
|
Logged
|
|
|
|
|
phila_dot
|
|
« Reply #1 on: April 13, 2012, 10:20:52 PM »
|
|
|
My axis is 50-100 in increments of 10 and behaves normally.
Why have a zero column?
|
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #2 on: April 13, 2012, 10:26:00 PM »
|
|
|
My axis is 50-100 in increments of 10 and behaves normally.
Why have a zero column?
Axis was screwed in stock bin. I'll try non zero first column and see if behavior persists. Thanks, Rey |
|
|
|
|
Logged
|
|
|
|
|
Snow Trooper
|
|
« Reply #3 on: April 14, 2012, 01:38:29 AM »
|
|
|
for driver requested the FR sugests no zero row.
I use a zero row but have experienced no issues.
|
|
|
|
|
Logged
|
cartoons?
6A 61 72 65 64 40 76 6C 6D 73 70 65 63
|
|
|
nokiafix
Full Member
Karma: +19/-2
 Offline
Posts: 124
|
|
« Reply #4 on: June 28, 2012, 01:05:30 AM »
|
|
|
Row 1 is 0 not 50
Nick
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #5 on: June 28, 2012, 08:36:16 AM »
|
|
|
No, stock axis is 0.5-1.0, which is probably a typo.
The correct "stock" values should be 50-100.
|
|
|
|
|
Logged
|
|
|
|
nokiafix
Full Member
Karma: +19/-2
Offline
Posts: 124
|
|
« Reply #6 on: June 28, 2012, 10:56:51 AM »
|
|
|
Stock should be 0  change your 50 row to .85 then log lambda. I alway thought it was 50 until it started to use ols300, and now use 0 Nick |
|
|
|
|
Logged
|
|
|
|
nokiafix
Full Member
Karma: +19/-2
Offline
Posts: 124
|
|
« Reply #7 on: June 28, 2012, 11:01:04 AM »
|
|
|
or another way to put it is 50 will = 0
but the correct way to read it in the map is 50 to 100
maybe I am confusing, lol
|
|
|
|
« Last Edit: June 28, 2012, 11:18:29 AM by nokiafix »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #8 on: June 28, 2012, 11:26:23 AM »
|
|
|
Stock should be 0 change your 50 row to .85 then log lambda. I alway thought it was 50 until it started to use ols300, and now use 0 hmm. can you explain your reasoning? granted, mine is pretty half assed, i just assumed the typo is an off by 100x thing (% vs correction factor) |
|
|
|
|
Logged
|
|
|
|
nokiafix
Full Member
Karma: +19/-2
Offline
Posts: 124
|
|
« Reply #9 on: June 28, 2012, 11:35:22 AM »
|
|
|
hmm. can you explain your reasoning? granted, mine is pretty half assed, i just assumed the typo is an off by 100x thing (% vs correction factor)
In map packs it seems the scale 50-99% is correct but I alway thought LAMFA lambda would start at 50%, but when using live logging linked with OLS300 on 1.8T maps, I found the first row 50 is being used as a look up for idle conditions, and during coast off throttle its being read from. I will try and make a youtube video of what I have been seeing. I have not logged direct mrfa_w to see what its reading a idle. |
|
|
|
|
Logged
|
|
|
|
AndiS4
Full Member
Karma: +1/-0
Offline
Posts: 117
|
|
« Reply #10 on: June 29, 2012, 01:53:09 AM »
|
|
|
I thought a lot about this weird lamfa configuration.
The point in stock files having axis values of 0.5 to 1.0 is, that it does not matter. This is because stock they are set to 1.0 Lambda.
So if driver requested torque is over 1.0%, Lamfa value is used from the last coloumn wich is always 1.0.
Only if you want to change your Lambda / AFR in req tq areas higher 1.0%, you have to change the values for 1% coloumn.
Example:
So i you want to have Lambda from 50% to WOT at 0.75, you only have to set the last coloumn to 50.00 and the map values of this coloumn to 0.75...
Lambda will follow the last coloumn of lamfa from 50% on to WOT..
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #11 on: June 29, 2012, 07:59:27 AM »
|
|
|
In map packs it seems the scale 50-99% is correct but I alway thought LAMFA lambda would start at 50%, but when using live logging linked with OLS300 on 1.8T maps, I found the first row 50 is being used as a look up for idle conditions, and during coast off throttle its being read from.
Yes, that is because 50 really means 50 and below. I.e. you don't want it to behave differently between 0 and 50, then once it is >50, interpolate between the 50 line and the next one If mrfa is <=50, always use the 50 line. All lookups work this way. |
|
|
|
« Last Edit: June 29, 2012, 08:01:01 AM by nyet »
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #12 on: June 29, 2012, 10:48:48 AM »
|
|
|
All I can say is when my first column = 0%, WOT = first column values. I'll post logs of this behavior. I confirm it by changing lambda for first row and WOT lamfa reflected my new values. But it was a small margin that was affected. ~>96% is where it would jump back to using first column.
Logs to come.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #13 on: June 29, 2012, 10:52:48 AM »
|
|
|
make sure you log mrfa  |
|
|
|
|
Logged
|
|
|
|
|
elRey
|
|
« Reply #14 on: June 29, 2012, 10:54:34 AM »
|
|
|
I did.
|
|
|
|
|
Logged
|
|
|
|
|
