Pages: [1] 2
Author Topic: ps_w and WDKUGDN  (Read 11654 times)
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« on: March 16, 2018, 01:43:46 AM »

I'm having issues with trying to match ps_w vs boost and mshfm vs msdk_w via WDUKGDN. Does one affect the other?
The car is heavily modified (1.8T forged, big turbo, RS4 MAF, 80mm Hemi throttle, I.E. manifold, 1000cc injectors, WMI) so I have recently decided to go back to basics as I wanted to get the fuelling much better in order to make the most of the WMI.
So I turned the boost down to spring pressure, turned off WMI and got the attached graphs.
It's all good up to 5000RPM, but then ps_w increases while the boost stays constant. This completely ruins my fuelling above 5000RPM (super rich).
Previously I increased WDKUGDN at 7000RPM (my next point after 5000RPM) to match msdk_w when I was running much higher boost. Is this not the right approach? Are we meant to instead edit KFWDKMSN/KFMSNWDK to get mshfm match msdk_w?

The MLHFM is a direct copy from RS4 file. I guess another option is to underscale it, but this doesn't seem like the right approach.
How exactly is ps_w calculated?
 
Logged
prj
Hero Member
*****

Karma: +915/-426
Offline Offline

Posts: 5835


« Reply #1 on: March 16, 2018, 02:15:10 AM »

ps_w is calculated through inverse VE model (KFURL/KFPRG/KFPBRK(NW)).

It also tries to keep the models close, if you airflows drift too far (msdk_w vs mshfm_w) it will kick in a correction to get closer to msdk_w, this is probably what is happening.
WDKUGDN is not the only thing you have to modify, your KFWDKMSN and KFMSNWDK are probably wrong and no idea how you gonna get them correct with a hemi throttle short of flowbenching one, much easier to use a VAG throttle with a map already existing in ME7.

What is happening in your case is most likely msdk_w is much higher than mshfm_w and you get a correction factor.
You can force that factor to be 1 always, by setting the max and min limits, look in the FR for that, I don't remember off the top of my head what the parameters were called. Something like FKMSsomethingMX/MN.
Logged

PM's will not be answered, so don't even try.
Log your car properly.
nubcake
Sr. Member
****

Karma: +53/-4
Offline Offline

Posts: 401


« Reply #2 on: March 16, 2018, 04:21:15 AM »

I'd probably start with 80mm VAG throttle maps (e.g. rs6?), then as prj mentions - get VE in line.
Then polish up the result.

Basically:
1) Verify MAF & boost sensor are calibrated correctly, set WDK maps close enough.
2) Bring ps_w closer to pvdk_w by adjusting VE. Don't exceed sane values. If it doesn't want to go there, stop and think. Observe AFRs.
3) Bring msdk to mshfm by adjusting throttle maps.

It's essentially a hack, but if done properly - should give a good enough result.
MAF health is crucial with this approach. If it's off - you're going to screw up more, than fix.
And well - car should be absolutely perfect mechanically. No intake leaks, etc.
Logged
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #3 on: March 17, 2018, 07:31:10 AM »

Awesome thanks to both.
I took your advice and copied RS6 map for KFMSNWDK from and .ols file floating on this forum.
I then used Excel + interpolation to calculate KFWDKMSN precisely.
Finally I used using the equation here to populate WDKUGDN:
http://nefariousmotorsports.com/forum/index.php?topic=9221.15
mAir[kg/h] = Vcyl[cc]*rpm[1/min]*rhoL[kg/cc]*60*nCyl (theoretical 100%rl) and multiply it by 0.95 taking PSPVDKUG into account.

This gave the attached result, which is much better than before (and fueling is more consistent).
There is no VVT, so I have set all VVT maps to 18 degrees and disabled it using CDNWS, then set all KFPBRK(NW) to 1.
I have also set FKMSDKMN and FKMSDKMX to 1 as per suggestion from prj.

Now, which is the correct map to modify to get rid of the inconsistency in ps_w at 2,500 RPM and then again at 6,000-7,000 RPM?



« Last Edit: March 17, 2018, 07:37:11 AM by BoobieTrap » Logged
nubcake
Sr. Member
****

Karma: +53/-4
Offline Offline

Posts: 401


« Reply #4 on: March 17, 2018, 01:01:04 PM »

URL/PRG to adjust VE.
Will likely have something wonky in them around 2500ish.
Logged
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #5 on: March 18, 2018, 04:50:08 AM »

Good stuff, think I am getting my head around it.
The latest attempt looks good, on the right track but some further refinement needed to bring ps_w down to correct level in boost.
I've used WDKUGDN to raise ps_w and msdk_w at the same time. I think now I need to lower KFURL to bring ps_w down (independently from msdk_w) and then fine tune wdkugdn further by raising it slightly above 5000RPM.
Logged
prj
Hero Member
*****

Karma: +915/-426
Offline Offline

Posts: 5835


« Reply #6 on: March 19, 2018, 01:56:48 AM »

WDKUGDN should not affect ps_w unless you have a MAF error.
Logged

PM's will not be answered, so don't even try.
Log your car properly.
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #7 on: March 20, 2018, 09:22:01 AM »

Ok, well I looked through the FR and I think this is the section that is screwing with my fueling and ps_w calculations:
"with positive load jumps, the alpha / n signal can be more dynamically accurate than the HFM signal, especially if it is areas where strong pulsations occur. In this case, it is possible to exceed a threshold value to switch to the alpha / n signal for an applicable time TDPSLGRD."
Basically, my AFR is way below target on WOT (10.8 instead of 12.5) but lambda control is consistently adding over 10%!

So it looks like it is more important to get msdk and mshfm to match first before addressing ps_w and pvdk_w?
Logged
prj
Hero Member
*****

Karma: +915/-426
Offline Offline

Posts: 5835


« Reply #8 on: March 20, 2018, 10:33:27 AM »

That's why I told you set FKMSDKMN and FKMSDKMX to 1.
It makes sure that this does not happen.
Logged

PM's will not be answered, so don't even try.
Log your car properly.
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #9 on: March 20, 2018, 10:50:24 AM »

But I did set them to 1!
What else would cause my fueling look like this (lambda control 1.175!):
Logged
nubcake
Sr. Member
****

Karma: +53/-4
Offline Offline

Posts: 401


« Reply #10 on: March 20, 2018, 05:03:12 PM »

rlroh_w, rlzuhfs_w
If they diverge - something's triggering switchover to alpha-n and you investigate it.
If they don't - can also log rkukg_w (fueling transients compensation) and check that.
If none of the above look suspicious - you adjust HFM corrections and VE, I guess. (It can get really messy here if you're unsure about what you're doing - hence my note about "sane values" in the previous post).


EDIT: right, re-read your post. It looks like it's not really about alpha-n vs hfm anymore.
Frankly, I've never seen such behavior previously. Have no idea, why the eff would frm_w be like that when you're already overfueling.

EDIT2: it almost looks like your controller is disabled under WOT (and just keeps the latest val?)
« Last Edit: March 20, 2018, 05:36:31 PM by nubcake » Logged
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #11 on: March 22, 2018, 03:21:37 PM »

well my inline 044 was leaking, maybe it tripped some ECU monitors.
I got another higher flow pump on the way but I am away over Easter so will have to wait until April before further progress.
Logged
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #12 on: April 12, 2018, 01:40:11 AM »

Reading further, the culprit might be LALIUSMN, in my file this was set to 0.8, I will try to lower it and see how it goes.
Logged
BoobieTrap
Full Member
***

Karma: +3/-0
Offline Offline

Posts: 74


« Reply #13 on: April 15, 2018, 12:58:13 PM »

well, new inline pump and lower LALIUSMN has sorted frm_w.

WDKUGDN sorted out WOT msdk_w (few minor adjustments still needed), KISRM dialled in the dynamic msdk_w, MSLG for idle msdk_w and KFWDKMSN/KFMSNWDK for low throttle msdk_w and finally msdk follows mshfm pretty well at all times.

KFURL + KFPRG sorted out ps_w.

Still dialing in FKKVS for the WMI as there are a few areas where frm_w is working hard but everything should come together soon.



Logged
ottosan
Full Member
***

Karma: +5/-5
Offline Offline

Posts: 91


« Reply #14 on: November 29, 2020, 03:58:19 PM »

Awesome thanks to both.
I took your advice and copied RS6 map for KFMSNWDK from and .ols file floating on this forum.
I then used Excel + interpolation to calculate KFWDKMSN precisely.
Finally I used using the equation here to populate WDKUGDN:
http://nefariousmotorsports.com/forum/index.php?topic=9221.15
mAir[kg/h] = Vcyl[cc]*rpm[1/min]*rhoL[kg/cc]*60*nCyl (theoretical 100%rl) and multiply it by 0.95 taking PSPVDKUG into account.

This gave the attached result, which is much better than before (and fueling is more consistent).
There is no VVT, so I have set all VVT maps to 18 degrees and disabled it using CDNWS, then set all KFPBRK(NW) to 1.
I have also set FKMSDKMN and FKMSDKMX to 1 as per suggestion from prj.

Now, which is the correct map to modify to get rid of the inconsistency in ps_w at 2,500 RPM and then again at 6,000-7,000 RPM?






Hello BoobieTrap,

I'm having trouble calibrating bigger TB.
The TB is from 3.6 FSI N/A VW Tuareg(almos the same size as yours) The values from the software of Tuareg are not working correctly  because the ECU is MED9.1 and instead of RPM axis they have Pressure ratio values. 

As you mentioned above, you copied KFMSNWDK from RS6 file and calculated KFWDKMSN in excel. Could you please tell, did you copied only Z values from KFMSNWDK of RS6 or axis data as well? I assume you have just copied Z values and therefor you calculated KFWDKMSN in Excel using interpolation?

There is one more thing that is unclear to me. How did you calculated WDKUGDN? I have used the stock values and calculated air mass(kg/hr) for WDKUGDN but my calculation of % is not matching the stock value. Could you please tell how did you converted kg/hr to TB%?

Thank you in Advance,

 
Logged
Pages: [1] 2
  Print  
 
Jump to:  

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