What do you mean fknbrkn? Or, rather, what do you see that suggests that?

Also, sorry if I uploaded a ludicrously-long log--I thought I trimmed it but now I'm wondering if I accidentally uploaded the entirety of it where I accidentally triggered it to start and was too cold to stop and restart it.  The third gear pull is near the very end, and I stopped the log a few seconds after that pull.

Not sure i understand what setting DRL to 0 does except totally disable the PID?

thats correct
same as cwmdapp 7 / kfldrapp 0

gives base boost and allows initial fueling setup wo killing the engine


msdk is the calculated air mass
check the threads about ps_w msdk and so on
long story short: while msdk had too much differ from mlhfm_w rl_w drops significantly and also fueling goes off

raise ldrxn / hbn to avoid TB closure; plsol  1500 mbar is too low here

OK, on second thought, I think I'm going to leave MLHFM alone unless you guys think there's an issue there. The tool did the calculations based on what I believe to be accurate measurements, so we'll let that be for now.

I was reading up on WDKUGDN. S4 Wiki suggests that divergence of msdk_w and mshfm_w could be brought into alignment with changes to this map and BGSRM.

This thread seems to lend credence to that: http://nefariousmotorsports.com/forum/index.php?topic=7404.15 and it also suggests that msdk_w and mshfm_w really should trend together in a way that they aren't near the top half of my range. I'll run the car with the changes that I outlined last night (LDRXN and KFLDHBN increased to keep the throttle open) and log that, but if msdk_w and mshfm_w don't trend well, then I'll dig into WDKUGDN.

Thoughts?

OK, I gave this some thought last night while I was lying awake listening to tree branches rattle against my house in a wind storm. Because, if I'm up at 0400, I might as well be doing something useful.

I decided to try to rescale the MLHFM table. Just to see what it did. I ran MAFADJUST and gave it the parameters 60 and 72 for old and new MAF ID. I had previously given it 60 and 73. That did not seem to help. fra_w was now .902, and it seems like msdk_w   and mshfm_w divergence started a little sooner.

Again, and sorry for this, but the weather here has been really gnarly. We have a lot of snow blowing across roads at the moment, so the safest thing I could do was run a second gear pull. I applied the parking brake to drag the engine a bit so it could load up. I'm hoping the highway clears up a bit today so I can get out and safely do a third gear pull.

I'm attempting a run later today (hopefully with better roads) where I've rescaled MLHFM by running MAFADJUST with parameters 60 and 74 this time. I am attempting to bracket this, I guess, and see if we can find a scaling that keeps msdk_w and mshfm_w a bit closer together.

Or, hey, I could change something else. Let me know what you think. I'll leave this log here for you. It was a little long, so I trimmed it.

Most recent binary and a log of the run. I changed KFMIOP scaling and some of the values values in the table. I wrote this up last night and submitted it, but it looks like the submission didn't go through.

New binary. I normalized KFLDRL. It ran pretty good--way better than it ran this early into the first time. There was some oscillation, but it wasn't extreme, and it didn't overboost like crazy and max out the pressure sensor. The log is around here somewhere. I apparently forgot to commit the branch for this and the log is still on my laptop at home. I believe I have it here.

There is a weird-looking airflow spike that shows up in ps_w and a few other variables. Can anybody shred light on that or recommend a correction? I have been referencing the wiki, but I can't make up my mind where I should go next. If I can avoid pre-control linearization, I'd be very happy (the high WGDC runs make me nervous with a bigger turbo).