My problem seems to be that the computer is opening the throttle blade too much during part throttle, which causes very poor shifting. My torque tables are stock, BARO sensor is broken out, MAF is calibrated, and VVE is pretty good.
My theory is that for a given cylinder airmass demand, the computer is opening the throttle too much, because it does not know it is under pressure flow. Low pressure ratio (0.8 and below) and WOT everything is fine. It is just during part throttle that the blade opens too far, actual torque goes way above driver demand torque, and the trans does not like this, so it pulls more timing during the shits.
I seem to have found a possible work around by jacking up the VVE tables in the boost sections, to over 6000, which is super high, but it uses MAF only in those areas so the fueling is fine. This makes the computer think the engine is super efficient and does not need much throttle blade to meet the airflow demand.
The other thing I tried was changing the map sensor config to TC-MAP-TIAP-BARO, when i first did this and started the truck the throttle did not work at all and it gave a BARO sensor code. So I dug up the ECU pin out for the only factory turbo car I could find with a E92 ecm, the ATS-V, which has as TIAP and separate BARO sensor and wired a BARO sensor into my truck.. it did not throw a BARO code, but the throttle still did not work. I assume this is because it was referencing a bunch of hidden tables in the ECU that are zeroed out for my application.
I know there are plenty of boosted cars with breakout sensors, does no one else have this problem? Do you all just turn off shift torque management as a work around? or crank up the base spark table? Both of these options I would rather not do...
I understand that for the Gen 4 stuff, HP made an OS that prevented BARO update, which I think would be a good fix for this. I could breakout the BARO from the MAF, wire up a 3-bar sensor, then put it back in the charge pipe and have better throttle control.
Has anyone pushed HPtuners to turn off BARO update so we can run a proper TIAP sensor?