Asking quite a bit of stock turbos, honestly, those corrections aren't that bad. Little E85 might be all it needs if it's that borderline. Could always try playing with VANOS or reducing timing request there by 0.5-1° too.(Flash time redundancy.)
You're probably right about coils not fixing timing corrections. Compression-based ignition versus spark-based ignition. Duh.
Get me some ethanol to suppress the compression-based ignition!
Glad I'm not the only one. I start typing something and then it hits me when I see it writing lolJust needed @RSL to say it out loud
Here you go. Let me know what you think.Also, definitely log IAT. I always log oil temp as well. That could be the source of your corrections.
Id like to take a look at your .bin if you'd be willing to share it.
@Jeffman @all4bspinnin @Jeffman going to start on rpm x setpoint control tonight. Did u guys tune with the original wgdc tables before and prefer rpm×setpoint? I was gonna go over my previous logs and build the table off of final wgdc %
I started with the stock base WGDC table and then worked off my logged actual WGDC values to 1) avoid boost oscillations in the transition after Spool up into the max Torque region (at about 3500-4000 rpm), and 2) to keep boost high and hit Load targets all the way out to 5500 rpm before drop off.Did u guys tune with the original wgdc tables before and prefer rpm×setpoint? I was gonna go over my previous logs and build the table off of final wgdc %
One thing id like to caution you on before you get started is how fast boost can come online with the stockers using this logic. I would personally do what jeffman did and limit your overall wgdc to 70 to 80% vs going 100%. It takes some time but once its dialed in, its amazing.
jyamona said:Base, pre-control, adder, ceiling adder, and wgdc spool are ignored. I'd recommend 0'ing them out, as well as the wgdc to pos and pos back set to 0 as well. You just want to use the new table + PID
Take a look at my logs. My WGDC (RPM x Boost Setpoint) table is 70-80 at low rpm, but my logged numbers during Spool up and higher are 98-99! Lots of swooshing! So even though I'm using this logic there are still PID corrections apparently being made to actual WGDC to hit Load targets.
Compare WGDC Bank 1% (actual) versus WGDC base value % (table):
http://datazap.me/u/jeffman/xhp-sta...ool?log=0&data=2-14-29-30&zoom=32-108&mark=51