|
Title: LDRXN + LDORXN Post by: Bi-turbo on August 12, 2013, 03:39:05 PM Am I right in saying that the LDRXN is the boost control/max specified load
Setting that would be the boost that should be produced LDORXN is this the overboost protection? So if this was set to .2bar across the rpm range then I would get boost cut with anymore than .2bar above what's set in LDRXN? Eg 90 x 10 = 900 + 300 =1200 - 1000 = .2 bar Title: Re: LDRXN + LDORXN Post by: gkzs on August 13, 2013, 04:43:59 AM Am I right in saying that the LDRXN is the boost control/max specified load Setting that would be the boost that should be produced LDORXN is this the overboost protection? So if this was set to .2bar across the rpm range then I would get boost cut with anymore than .2bar above what's set in LDRXN? Eg 90 x 10 = 900 + 300 =1200 - 1000 = .2 bar LDRXN is the max pressure turbo will boost. KFMIRL is the max specified pressure engine can reach and is capped by LDRXN. Over ~0.2bar of LDRXN values, will cause limp mode. LDORXN is load (%) overboost protection. So if you set it to 150%, when engine reads over it (continuous or instantly over ~165%) will cut boost. Title: Re: LDRXN + LDORXN Post by: matchew on August 13, 2013, 04:51:56 AM None of the tables mentioned are boost.
Title: Re: LDRXN + LDORXN Post by: automan001 on August 13, 2013, 05:04:22 AM LDORXN is load (%) overboost protection. So if you set it to 150%, when engine reads over it (continuous or instantly over ~165%) will cut boost. Not quite exact. Its switched in instead of LDRXN/LDRXNZK during overboost. From FR http://www.nefariousmotorsports.com/wiki/index.php/LDRLMX_3.100_(Calculation_of_LDR_Maximum_Cylinder_Charge_rlmax) (http://www.nefariousmotorsports.com/wiki/index.php/LDRLMX_3.100_(Calculation_of_LDR_Maximum_Cylinder_Charge_rlmax)): LDORXN is maximum cylinder charge LDR during E_ldo (overboost error) In the overboost condition (E_ldo) an engine speed dependent limit (LDORXN) is switched in so that both the engine and the turbocharger adequately protected. Switching back also occurs only when resetting the error (E_ldo) and in idle-mode (B_ll). Title: Re: LDRXN + LDORXN Post by: Bi-turbo on August 13, 2013, 05:48:09 AM Great link, some very helpful info in there, thanks
Title: Re: LDRXN + LDORXN Post by: phila_dot on August 13, 2013, 06:40:30 AM LDRXN is the max pressure turbo will boost. KFMIRL is the max specified pressure engine can reach and is capped by LDRXN. Over ~0.2bar of LDRXN values, will cause limp mode. LDORXN is load (%) overboost protection. So if you set it to 150%, when engine reads over it (continuous or instantly over ~165%) will cut boost. None of that is correct. 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. Title: Re: LDRXN + LDORXN Post by: overspeed on August 14, 2013, 09:45:10 AM 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. How PR is converted in load ? ( Better asking: where in Funktionrhamen can I found info about this, I know the "rough formula value/4,266 + 300 = absolute pressure" but I´m interested in from what this "300plus" value came Title: Re: LDRXN + LDORXN Post by: nyet on August 14, 2013, 11:49:48 AM search for rl_w and trace it back to pvpdks_w :P
Title: Re: LDRXN + LDORXN Post by: phila_dot on August 14, 2013, 12:16:52 PM fupsrl_w is used to convert pressure to load
Title: Re: LDRXN + LDORXN Post by: overspeed on August 14, 2013, 12:38:42 PM Thank you both !!!
|