Title: fine tuning WDKUGDN - what to log for 95% charge? Post by: elRey on April 04, 2014, 07:29:27 PM When fine tuning WDKUGDN, what should I log to see when 95% charge is reached?
Thanks, Rey Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: titi65 on April 04, 2014, 11:37:09 PM I think that:
PressureIntake - ResidualPressureCylinder near= rl; PressureIntake x Kfpsdsskp(rev/s,pressure) - kfprg(rev/s) nearly= rl; So, you can log intake pressure and substract to kfprg. When you find throtle angle witch deliver 0.95 RL, you've got your WDKUGDN . (I think) Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: catbed on April 08, 2014, 10:15:39 AM When I was looking at this, I thought you could not log it as it was calculated. There is no pressure sensor in the manifold to compare pre/post throttle plate pressures.
EDIT: removed variable. I think to populate WDKUGDN with correct values a pressure sensor in the manifold is needed. Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: titi65 on April 08, 2014, 10:40:42 AM Excuse me, my ME7 got a pressure sensor instead of MAF . . .
Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: elRey on April 09, 2014, 06:51:10 AM If WDKUGDN is not used in calculating the charge it references, then I don't see why I couldn't just log the calculated charge to tune it, right? If so, what is the variable of the calculated charge?
Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: userpike on April 09, 2014, 11:02:11 AM The FR says NMOT_W is the source-x for WDKUGDN and shows "wdkugd_w" is the output variable for WDKUGDN.
"This function is part of the normalized target air mass msndkoos_w the target angle wdksgv_w to control the throttle valve calculated. By the angle for the unthrottled operation wdkugd_w (output from speed-dependent characteristic WDKUGDN in BGMSZS%) is the target angle defined by the map KFWDKMSN. This is the inverse map of KFMSNWDK (from BGMSZS%) and is on the built-in throttle valve positioner adjusted. If the above is the normalized target air mass value calculated from KFWDKMSN larger than the Angle wdkugd_w, so is the condition for unthrottled operation B_ugds = true." Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: catbed on April 09, 2014, 11:31:09 AM If WDKUGDN is not used in calculating the charge it references, then I don't see why I couldn't just log the calculated charge to tune it, right? If so, what is the variable of the calculated charge? I believe it is vpsspls_w Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: elRey on April 09, 2014, 03:18:09 PM The FR says NMOT_W is the source-x for WDKUGDN and shows "wdkugd_w" is the output variable for WDKUGDN. "This function is part of the normalized target air mass msndkoos_w the target angle wdksgv_w to control the throttle valve calculated. By the angle for the unthrottled operation wdkugd_w (output from speed-dependent characteristic WDKUGDN in BGMSZS%) is the target angle defined by the map KFWDKMSN. This is the inverse map of KFMSNWDK (from BGMSZS%) and is on the built-in throttle valve positioner adjusted. If the above is the normalized target air mass value calculated from KFWDKMSN larger than the Angle wdkugd_w, so is the condition for unthrottled operation B_ugds = true." OK, the question is how do I log/monitor to find out the ideal threshold for B_ugds. I believe it is vpsspls_w Thank you. I'll try this. Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: catbed on April 09, 2014, 06:00:13 PM Thank you. I'll try this. Actually I take that back. Try pspvdk_w. FR says it is "quotient: int.manif.pressure divided by pressure upstream of throttle valve" Also, psspvdkb_w and psspvdk_w Title: Re: fine tuning WDKUGDN - what to log for 95% charge? Post by: dream3R on January 01, 2016, 10:38:28 PM Actually I take that back. Try pspvdk_w. FR says it is "quotient: int.manif.pressure divided by pressure upstream of throttle valve" Also, psspvdkb_w and psspvdk_w ere's the code I found not complete vars tho, moved one. seg020:CCAA sub_ACCAA: ; CODE XREF: interrupt_sub_B81C+CP seg020:CCAA movbz r4, mste_wrong seg020:CCAE mov [-r0], r4 seg020:CCB0 mov r12, rlfglmsm_w seg020:CCB4 mov r13, umsrln_w seg020:CCB8 mov r14, #2155h seg020:CCBC calls 4, divide_sub seg020:CCC0 mov r5, [r0+] seg020:CCC2 sub r4, r5 seg020:CCC4 jmpr cc_NC, loc_ACCC8 seg020:CCC6 mov r4, #0 seg020:CCC8 seg020:CCC8 loc_ACCC8: ; CODE XREF: sub_ACCAA+1Aj seg020:CCC8 mov word_302BCE, r4 seg020:CCCC mov r12, #6B62h ; WDKUGDN seg020:CCD0 mov r13, nmot_word_3019A8 seg020:CCD4 calls 4, sub_41146 seg020:CCD8 mov wdkugd_w, r4 seg020:CCDC rets |