Jump to content

2014 Silverado hesitation when accelerating from stop

MisfireMagnet
 Share

Recommended Posts

MisfireMagnet Enthusiast

MisfireMagnet

Posted
Posted (edited)

Hello,

 

I am hoping that you can help me diagnose what is causing a hesitation on my truck when accelerating from a stop. It sometimes also hesitates when shifting at low speeds 10-30mph

 

Truck Specs

  • 2014 silverado 1500 WT
  • 4.3L V6
  • locking rear end
  • 32,000 miles
  • no codes, using bluedriver scanner
  • red

 

Problem

  • two weeks ago truck took two tries to start
    • never done this before
    • has not happened again
  • last week truck started hesitating on acceleration from stop every time
  • rpms drop from 1500ish to 500ish and then jump back up and truck accelerates
    • I have attached one of the drive logs where you can see the fuel rail pressure drastically change when the engine rpm drops
      • You can see the seven times the truck hesitated at the drops in the graph
  • Started logging other items to see what is happening and found this spike in the temp sensor, attached picture also.
    • intake temp sensor is yellow line and engine rpm is blue line.
      • I highly doubt the temperature actually went from 55F to 135F during my commute.

 

What I have done

  1. Checked transmission fluid, truck level and hot.
    1. Fluid in the dashed good zone between the holes.
    2. No burnt smell.
  2. Found the strange temp reading.
  3. Truck off
  4. Unplugged the mass air flow sensor and drove around large parking lot.
    1. Hesitation completely gone truck drive normally for 5 min.
    2. Check engine light off.
  5. Truck off
  6. Plug in mass air flow sensor and drive around parking lot again.
    1. Hesitation back
    2. Check engine light on with codes for MAF unplugged.
  7. Thought MAF was the issue.
  8. Bought new MAF and air filter
  9. Installed MAF and air filter
  10. Problem gone on test drive for 15min, truck fine, no codes.
  11. Next day, hesitation is back, no codes
  12. Realize I need help.
  13. Post on forum.

 

I'm sure I have left out some important information, just let me know and I'll try to answer.

 

I greatly appreciate the help. Thank you.

 

fuel pressure drive log.png

inlet temp sensor and engine rpm drive log.png

Edited by MisfireMagnet
adding additional diagnostic step i did
MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

Update on diagnosis:

  • I have tried unplugging the battery for 15min to reset sensor parameters. Still having the problems.
  • Truck shifts without hesitation in manual when I am controlling shift points.
    • When I manually shift over/at/under the rpm where the truck automatically tries to shift it is working correctly without any hesitation/jerking.
  • Tried cleaning the original MAF sensor again and re-installing but same issue.
  • Dealer told me without an engine light or code the most they would do is just start cleaning the intake and intake manifold and see if anything changes.
  • Tried fogging the engine compartment with fine water mist to see if rpm dropped slightly.
    • This is probably not as effective on new computer controlled engines. They might adjust before the scanner senses rpm drop.

 

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted (edited)

Update:

  • Check engine light off.
  • Now has some permanent codes.
    • P0097 - intake air temperature sensor 2 circuit low bank 1
    • P00F4 - humidity sensor circuit low
    • P0102 - mass or volume air flow sensor "a" circuit low
    • P0113 - intake air temperature sensor 1 circuit high bank 1
  • I can view the sensor data live for the above codes and they all appear to be working fine.
    • I am thinking the codes could be from my test drive with mass airflow sensor unplugged.
    • Do you know how long it could take for the truck to clear these codes?
  • Checked every wire connector I could reach to make sure it was not loose.
  • Filled truck with 89 octane and added Lucas fuel treatment with injector cleaner.
  • 10 min test drive around neighborhood
    • Hesitation present and some rough idle.
  • Took truck for 30min drive down highway to get everything up to working temperature.
    • Drove in tow/haul to keep engine rpm up, hopefully get the fuel treatment moving through faster.
    • Highway driving 55-65 mph nearly entire time.
    • Accelerated pretty aggressively from low speed after truck was warmed up down highway.
    • Truck acting good at speed.
    • Back in neighborhood after test drive the truck did not hesitate at all and accelerated smooth like it should.
  • I will see what happens tomorrow when the truck is cold.
Edited by MisfireMagnet
typo
ic3man5 Enthusiast

ic3man5

Posted
Posted (edited)

I'm not exactly sure if this is your problem but look into the HP fuel pump. Early models (2014s) were known to have failing fuel pumps (Its under the intake manifold). If your scanner can read the LTFT and STFT (Fuel trims), I would try monitoring that. I'd also check for a vacuum leak.

 

Codes more than likely will stay until you clear them manually. I would say they are probably codes from when you removed the sensor.

 

 

edit: while you are at it inspect the coolant level (OEM radiator / t-stat suck).

Edited by ic3man5
MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

Thanks. I will log the fuel trims next and see if anything is strange.

Codes are now listed as permanent and the truck will have to clear them when it determines the problem is gone. (according to my reader anyways)

All fluids are at correct level.

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

Okay, so the truck ran great for two days and now the hesitation problem is back.

I have taken some snapshots of the fuel trim readings over a time period where there is two hesitations present.

I am going to have to do some research because I don't know what is good for fuel trims.

 

Long term fuel trims against engine rpm here.

image.thumb.png.6469549211cd58966577eb76fd2baf30.png

 

Short term fuel trims against engine rpm here.

image.thumb.png.1cd0527686adec7676f21e1f6b2023f3.png

 

Driving steps here. You can see as I start to accelerate from a stop the RPM increases to 1300ish for a split second and then falls to 600ish before jumping rapidly to 2000ish.

This is engine rpm on the left vertical axis and time in seconds on the horizontal axis.

You should be able to map this activity back to the upper two graphs if needed.

image.thumb.png.4f61f3930919bb70160b6ed03567533f.png

 

Not sure what to do next. The previously listed four codes are still present when I try to read them but the check engine light is still off.

 

 

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

Okay, so I have looked into fuel trims slightly and it seems they ideally should stay even with perfect air/fuel ratio.

Since my STFT is maxing out at +25% that means the PCM is detecting a lean condition short term and is trying to add more fuel.

However, my LTFT is consistently negative at 0 to -14% like the PCM is detecting a rich condition on average and is reducing fuel.

 

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

After noticing that both banks are roughly the same acting I believe it has to be something that must effect both sides.

So ruled out, for the moment anyways, injectors, coils, plugs, and O2 sensors.

Going to check evap purge valve to see if it has any vacuum on the port at idle. After that I might suspect one of the fuel pumps.

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

After driving home from work the engine was hot and I restarted the truck to idle in the driveway.

The evap purge valve was shut for about 20 seconds and then it started to make a popping noise and I could feel intermittent vacuum. 

Should this purge valve be open at hot idle?

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

I tested the evap purge valve on my workbench and I believe it is good.

-held vacuum without leaking no power.

-released immediately when power applied.

 

I monitored my STFT and LTFT and they were negative with the evap hose connected. LTFT was around -15%.

When I unplugged the hose and covered the port with my finger the STFT went to near zero and LTFT about -4%

The truck was warmed up and the ambient temp is 80F.

Does this seem strange? If so I guess the problem might be upstream of the evap purge hose towards the tank.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

Okay, so I have been recording every trip in my truck and stumbled across the following reading.

image.thumb.png.790be0e6540674a693d1d6da1d2ddc7b.png

My engine RPM read over 12,000 rpm for almost two seconds while I was driving steady at 1100 RPM.

This happened several times but I zoomed in on one occurrence for clarity.

You can also see my negative LTFT and maxing out STFT.

At this point I would guess one of the following things is happening.

  1. My BlueDriver scanner malfunctioned several times.
  2. Crankshaft position sensor going bad.
  3. Camshaft position sensor going bad.

Guess I will try to test both of those sensors and see what happens.

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

I have now moved on to checking the throttle position sensor.

My scanner allows me to view Absolute Throttle Position (%)

With engine-off key-on I went from not-pressed to pressed-to-floor several times and saw the below reading.

Does anyone have the in-spec values for this?

image.thumb.png.a455d27d5a5fc106b959125dbc54fcbd.png

MisfireMagnet Enthusiast

MisfireMagnet

Posted
  • Author
Posted

Okay, so continuing down the path of the throttle position sensor.

I recorded the following data while the truck was hot idling.

I tried to push the pedal with my hand and hold it at the same position repeatedly.

You can see the pedal position at each attempt stay relatively constant but the throttle position sensor dips right after pressing the pedal and then comes back up.

I am thinking that maybe the TPS is bad. Going to look into how to test this sensor next.

image.thumb.png.5dc94b0e340b47a59de05460242c5832.png 

 

ic3man5 Enthusiast

ic3man5

Posted
Posted
On 3/31/2021 at 1:05 PM, MisfireMagnet said:

Okay, so continuing down the path of the throttle position sensor.

I recorded the following data while the truck was hot idling.

I tried to push the pedal with my hand and hold it at the same position repeatedly.

You can see the pedal position at each attempt stay relatively constant but the throttle position sensor dips right after pressing the pedal and then comes back up.

I am thinking that maybe the TPS is bad. Going to look into how to test this sensor next.

image.thumb.png.5dc94b0e340b47a59de05460242c5832.png 

 

You need to turn the engine off and with the key on push the throttle all the way down (WOT). It should be around 80-85%. Bottom should be around 10-20% I believe. You won't see 0-100%.

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

  • Latest Articles

  • Posts

    • Chuck FB
      summer road trips in the 2026 2500HD

      By Chuck FB · Posted

      I thought I would use your thread and add to it as I just did my first longer drive with my truck in the last couple of days. I drove from the Grande Prairie area of Alberta down to Edmonton and most of where I drove in the city was the ring road so fairly free flowing but a bit of stop and go as well in the city. Stayed the night and returned home and not too many stops along the way each way but every restart and certainly every cold start sets it back for fuel mileage. Why I say that is I see some people will cherry pick a fuel mileage leg after the vehicle had been warmed up driveline wise before hand and its a forgiving ( easy rolling drive leg for example ) and call that their fuel mileage which can give a false perception of reality. I was not heavily loaded at all but never the less the flip bak cover, rubber bed mat, various tools etc and extra jerry cans of fuel all way up to a few hundred pounds of dead weight so its not an empty truck. The cold inflation tire pressures are set more near the freezing point so once they are warmed up driving I was showing 45 front and over 40 rear and realize high inflation pressures would help a little in fuel mileage but certainly not the ride on our crap sections of highway. The weather was good so was not raining as that can really drag mileage down, in fact I had a bit of a tail wind on average driving home. Most people on here would never have driven on that freeway to visualize it but its got a fair bit of rolling type of landscape with numerous river valleys. For the most part I had it on cruise set to 62 although kicking it off if I caught it in time before it started down shifting and self braking going down the grades. Most of the more substantial grades its shifting into 7th I believe as 8th just doesn't have it. Total distance round trip was 643 miles and my overall average and I did refuel three times in all, figured out to 17.65 miles per US gallon. My best fuel mileage section refuel within all of this figured out to 18.46 and these are all hand calculated figures. I find if anything that the trucks computer can be over optimistic, sometimes its pretty close but other times its stretching it. On paper persay in theory the truck would have just about made it on fumes for that whole drive without refueling once.    Which made me think of the topic thread of the wonder if these trucks could do 20 mpg and that is a good question, certainly would have to be on an easy going flat highway, no head wind, the right temperature, not packing around a bunch of dead weight and puttering along even slower than I was I would suspect and going steady and not stopping to smell the flowers or take a piss !. It probably is possible but not without effort to attain that with the wind resistance and weight of these trucks. Of course on my drive most people are passing me if they have the power as per loaded highway tractors, never mind a lot of speedy vehicles but the speed limit is 68 and most are at or well over that. 
    • Aimatdeer
      Ac not keeping up

      By Aimatdeer · Posted

      Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...