Issues with DoD and Half Power After Delete

[nkfry]

Hey guys, I've been racking my brain trying to figure out what I'm missing here. I did the Texas Speed DoD delete with a stock non DoD cam and after turning DoD off in the file, setting the PRNDL and gear to disabled under DoD, not reporting error on any of the DoD cylinders or activations, and multiple reflashes I still get half power as soon as I apply any throttle, if I let the truck sit idle it will have no issue.

Truck is a 2009 GMC Sierra w/ 5.3 non VVT and 120k miles, all stock just deleted the DoD.

I will call HPTuners in an hour or so to see if they have any input here, but I feel like I've covered all of my bases and still I get cylinders 1, 4 & 6 activation circuit/open but there is no error reported on cylinder 7, which is weird because it is also a DoD cylinder and all 4 are set to not report errors or set SES light.

Any insight is appreciated, file attached for reference. Dad Truck- TQ management, throttle, DoD off 1.hpt

[Tom @ Overdrive]

Put your throttle tables back to stock. If the codes set and read (permanent) they will always live in the background. But not be causing a MIL.

[mbray01]

You answered your own question, as soon as you touch throttle, its your throttle settings

[nkfry]

Put your throttle tables back to stock. If the codes set and read (permanent) they will always live in the background. But not be causing a MIL.

Thanks for the response Tom, I had a thought about that especially knowing the warning in the throttle tables, I was trying to enhance the driver demand because the stock response is absolute garbage. I'll try to set the throttle tables back to stock, but there were no codes for the throttle table just the 3/4 DoD cylinder circuits being permanently open.

But thinking further into this now; the truck runs fine at idle with zero pedal demand but as soon as I roll on about 5% throttle demand is when I set the faults and get half power.

Mbray, I had a suspicion but again, no faults set for the throttle led me to believe I was chasing an issue with the DoD fault codes and reporting.