Jump to content

Suburban accelerates when put in gear

Marty T
 Share

Recommended Posts

Marty T Enthusiast

Marty T

Posted
Posted

I have a 2005 Suburban 1500 LT 5.3 with 161,000 miles. Runs drives and shifts real well. I have had diagnosed twice now but have been given much to go on. Problem is it idles fine at approximately 600 rpm in neutral but when put in reverse or drive it pulls. The throttle plate opens from 4% to 14% open and the vehicle will accelerate almost to the point of shifting into 2nd gear without touching the gas pedal. A Chevy service facility recalibrated my throttle body and then replaced it with a known good on from another vehicle….same problem. I then got a new ecm and they reprogrammed it….same problem. After some time on the phone with their tech people they decided it was something transmission related…maybe torque converter related. I then took it to a reputable trans shop where they had better equipment to diagnose transmissions. They said the vehicle definitely had an issue that needed to be fixed but the trans checked out great and there were no problems there. Their tech people said the only other thing that could throw a load would be the mass airflow sensor. Not wanting to spend a lot at this point I took the vehicle home and replaced the maf with a used part from a local yard….same problem. The vehicle shows no codes and has a 4L60E trans. I am in need of some help from someone who may have encountered this problem before or has any ideas. Thanks so much for the help.

swathdiver Senior Enthusiast

swathdiver

Posted
Posted

I would also check for a vacuum leak.  When the throttle body was replaced with the donor, was the truck driven around long enough for the computer to relearn, maybe 20-50 miles?

 

It is my understanding that 14% is way too much, should not really be more than 10% which would indicate a dirty plate and normal about 5%.

Marty T Enthusiast

Marty T

Posted
  • Author
Posted

I do not believe it was driven after the TB was replaced but it was calibrated. I'm not real aware of what needs to be done but was assured the TB was ruled out as suspect, It had this acceleration problem when I bought it and could see someone had put a new aftermarket TB on it and was extremely clean inside. My Chevy service tech is saying trans and my trans guy said MAF, which I ruled out. Stumped. Thank you for your reply.

Marty T Enthusiast

Marty T

Posted
  • Author
Posted

I will see if it has an IAC. Anyone out there know if it has and if so would it relate to the problem I am having? What may be a test for it?

SierraHD17 Senior Enthusiast

SierraHD17

Posted
Posted

You won't have an IAC as your truck is drive by wire.  Has anyone paid attention or swapped the TAC module on the firewall?  It's the communication link between the pedal and the throttle body.  Otherwise something has to be loading the truck somewhere.

  • Thanks 1
Marty T Enthusiast

Marty T

Posted
  • Author
Posted

The TAC is something that has not been done. Can it be tested or just change it out?. Could you please describe this part and the full name so I might understand it better and I can do some research. Sounds like a possibility if it's a critical component between the TB and Pedal. Thanks for the help.

SierraHD17 Senior Enthusiast

SierraHD17

Posted
Posted

Throttle actuator control.  It's the brains of your throttle circuit and also handles cruise control.  It's a box on the firewall right beside the brake booster.  For tests.. just swap it with a known working one for simplicity.

Marty T Enthusiast

Marty T

Posted
  • Author
Posted

Thank you. I will try it. This seems to be leading to a torque converter clutch issue I think. Any way I can test this? I'm trying all the simpler and cheaper suggestions first but I think a new trans and torque converter is in the future. Just hard to go that direction when the shop says everything is fine with the trans with their diagnostic tools.

  • 3 years later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined

  • Who's Online   3 Members, 0 Anonymous, 2,074 Guests (See full list)

  • Latest Articles

  • Posts

    • CamGTP
      Gas Prices

      By CamGTP · Posted

      Paid $2.72 for E85 today.
    • Atlas
      Gas Prices

      By Atlas · Posted

      Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • scotthvac.net
      2022-24 halogen - led grille swap

      By scotthvac.net · Posted

      2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • davester
      Replacement Radiator

      By davester · Posted

      And use RA's 5% discount code if you buy from them.  google for the code, one is always available.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...