Kylefentz

truck is a 2004 rcsb which had a 4.3 nv3500 but swapped that out for a turbo lq4/80e out of a 06 sierra 2500. the lq4,80e, harness, TAC module and pedal assembly, cluster and fuse box are all from the same truck. had local tuner install a base tune and was told to reach 80mph tpo assure there is no vibrations, leaks, ect. for the dyno tune. my problem is, the engine idles great but cannot rev above 3000 rpm nor reach even 40 mph. initial 10-20 seconds the engine can be revved but then goes into some sort of a limp mode. fault codes present are p0102 and p0103 for MAF circuitry. the setup does not have a maf and only a IAT so im assuming it was tuned per SD. the trans wont shift unless you feather and pedal and if it does shift by itself its at the wrong times.

the pictures are scan tool values at IDLE. why does the torque request signal read -865 at all times. what does this mean and would it cause my issue. Ive tried contacting my tuner and he will not return any questions I have. any help would be more than appreciated. thanks dudes

smokeshow

iTrader: (16)

If I had a dollar for every time this question was asked lol... You must calibrate or disable throttle position rationality diagnostics.

Kylefentz

so, how do I do that. is that HPtuners thing or can I perform this with a scan tool?

madmann26

iTrader: (7)

You need to find a more reliable tooner.

06murder

Would been easier for you to keep doc man

Kylefentz

looking back at this post after getting MPVI2 and learning a few things it is almost embarrassing but we all start somewhere. My issue was in the DBW max rotation table and once changed HPtuners warns you that changing this table could brick your ecm. Where I live a used P59 ecm is 30 bucks. thankfully it DID NOT brick my pcm but did fix that current issue. sorry to anyone who came to this thread for hope and only found a deadend.

2002_Z28_Six_Speed

iTrader: (20)

I had this issue too when I swapped to a 408. It wouldn't rev up and go into REP. I can't remember the exact name of the table but it was definitely in the calibration.