WGDC Drops. Default to WGDC Base. No PID added

[tony@codewerx]

I’d love to have Boost just below target but I have to ride out PID and it will usually end up reverting to base at some point.
No overboost codes. It will do this every time on back to back tries.



It’s set to 3.0

And you have a N20 scaled flash meaning you got a 3.5 bar map sensor in there ?

 

[chrisdfv]

And you have a N20 scaled flash meaning you got a 3.5 bar map sensor in there ?

Correct. I think 3.0 on a scaled map is 28/29psi if I'm not mistaken.

 

[tony@codewerx]

Correct. I think 3.0 on a scaled map is 28/29psi if I'm not mistaken.

What is the Boost level you are trying to target ?

 

[chrisdfv]

What is the Boost level you are trying to target ?

20psi

 

[tony@codewerx]

20psi

Would you consider lowering the BLM to 2.3 ?

 

[chrisdfv]

Would you consider lowering the BLM to 2.3 ?

To give myself a load cushion?

 

[RSL]

What is your load limit multi and torque max index array set to? You could back off WGDC and raise load target. Do you have any with final WGDC % just out of curiosity? Flags are set to inverse for the boostbox? What revision is the box?

 

[tony@codewerx]

To give myself a load cushion?

To bring some balance.

How did you scale the map sensor ?

 

[chrisdfv]

What is your load limit multi and torque max index array set to? You could back off WGDC and raise load target. Do you have any with final WGDC % just out of curiosity? Flags are set to inverse for the boostbox? What revision is the box?

Looks like my load limit multi isn't stock(can't remember where I picked that up from) and my torque max is stock.

BB version 3 so wgdc 1 is inverted with wgdc after PID. I don't log wgdc 1 to avoid confusion. WGDC after pid is my final output.

To bring some balance.

How did you scale the map sensor ?

See below.

 

[RSL]

Try raising your torque max index to maybe 100 or 120. If you just want to jam it up, 200. That should allow the DME to push load request up IIRC. Other option would be to lower boost actual and raise load target to get back where you want actual.

I was just curious if there was something we're not seeing in the final value, like if it's over 75% or something. Not sure what's triggering the PID off unless it's something specific to boostbox/inverse which I wouldn't know about.

 

[chrisdfv]

Try raising your torque max index to maybe 100 or 120. If you just want to jam it up, 200. That should allow the DME to push load request up IIRC. Other option would be to lower boost actual and raise load target to get back where you want actual.

I was just curious if there was something we're not seeing in the final value, like if it's over 75% or something. Not sure what's triggering the PID off unless it's something specific to boostbox/inverse which I wouldn't know about.

I think I’m going to raise load 5 points and set the boost target to 20psi using BLM.

I don’t think that’s the solution to the pid time out I’m experiencing but it will give me the load cushion you guys want to see haha.

I’m tempted to try the standard air flow strategy instead of setpoint x rpm.
I think chris kontos told me once that setpoint limita part of the P+I function. Possibly what I’m dealing with here.

 

[RSL]

I think I’m going to raise load 5 points and set the boost target to 20psi using BLM.

I don’t think that’s the solution to the pid time out I’m experiencing but it will give me the load cushion you guys want to see haha.

I’m tempted to try the standard air flow strategy instead of setpoint x rpm.
I think chris kontos told me once that setpoint limita part of the P+I function. Possibly what I’m dealing with here.

At least we'll know if load has anything to do with it lol I can't imagine how setpoint would be an issue on a scaled map that low, but I don't have I8 or IJ so I've never used that logic. There's just nothing I see that screams PID problem other than it obviously turning off, so let's just throw shit against the wall and see if any sticks

 

[Jeffman]

I’m also in the same boat as OP. Using an MBoost MHD modified Spxxx bin, which I had posted somewhere on this forum. Stock turbos, stock inlets and outlets. See the WGDC PID zero out. Life got busy so haven’t fired up TunerPro in >9 months. Hope to do so soon, now that I’m installing the MOTIV FlexFuel functionality. Would love to compare bins with OP.
https://datazap.me/u/jeffman/93-oct...og=2&data=2-16-29-30-31&zoom=21-97&mark=48-33

 

[WOT808]

I’m also in the same boat as OP.

The key is to keep boost actual close to target. That means some taper for stock turbos. I set load out of the way and use BLM and boost ceiling to shape boost target. Also, it's best if WGDC base is really close to WGDC After PID

I stopped targeting 24+ because my turbos can only hit that below 4.5k when starting a pull ~3k(I think my turbos are tired) and with WGDC base so high it caused over boost issues during multi-gear pulls (which also makes PID drop).

Log with 24psi target: https://datazap.me/u/m6keharr/bpc-dyno-465

My car spends most of it's time starting pulls ~4k so I'm sticking to 22 target down low with taper to 18ish using BLM.
I'm tempted to just stick with stock scaling , target 21 flat, and not worry about PID drops or over boost after a few gears.

Recent log: https://datazap.me/u/m6keharr/log-1531484409?

We can take a look at your BIN for sure

 

[Jake@MHD]

Torque max index array can be set to 100 across the board. Greater than 100 shouldn't have any benefit, as it is actually a max lookup of requested torque from driver pedal table IIRC. Table should probably be renamed You never request more than 100% of torque in the throttle tables, so 100 in the index table is fine.

 

[chrisdfv]

Well I move load out of the way and set boost target with "boost ceiling" since BLM turned out to be more of pain than I anticipated. Lived life for one pull at 24psi on 93oct
No luck. PID still times out. If i continue to raise my base wgdc to match after pid, for whatever reason my pid will continue to add and I overboost.

I'm going to be trying out the regular air flow tables today.
https://datazap.me/u/cd919/v16

 

[Jake@MHD]

Have you started with PID zeroed out to get your boost as close as possible without it? Then slowly add in and tune PID.

 

[chrisdfv]

Have you started with PID zeroed out to get your boost as close as possible without it? Then slowly add in and tune PID.

I have not. I'm just not sure what happened. My PID used to do great and would never time out. I've compared my current bin to older versions and nothing sans fueling, timing, things related to going to 93 have changed. Now it never wants to remove wgdc.

Even on scaled map targeting similar boost on e40

https://datazap.me/u/cd919/log-1520208143?log=0&data=3-6-22-25-30-31&solo=25

 

[Jake@MHD]

Were you using setpoint x rpm then? When you switch over, it no longer user the airflow adder table, so you have some rework to do. Also, when switching to a scaled tmap, you also have to re-do PID.

 

[chrisdfv]

Were you using setpoint x rpm then? When you switch over, it no longer user the airflow adder table, so you have some rework to do. Also, when switching to a scaled tmap, you also have to re-do PID.

I've always used setpoint x rpm on my single turbo tune, and PID had worked with both non-scaled and scaled map up until recently.

I'm going to be trying the standard wgdc base, spool,and adder tables. Lets see what happens.