Jump to content

HUGE MPG drop after routine tune up?

GMJunkie7
 Share

Recommended Posts

GMJunkie7 New Member

GMJunkie7

Posted
Posted

Hey all, 

 

Here's the story. I've got a 2016 1500 silverado highcountry 5.3 that has for the most part been good to me ( except for the hard shifts and transmission issues alot encounter) 

 

Recently, I gave her the 100k mile tune up. As part of this, I did brakes, and spark plugs. My local Advanced didnt have AC Delco, so I used the "correct" replacement NGK plugs. 

As part of the brake install ( since I tow I installed powerstop brakes) I had to do a brake in procedure involving accelerating to 40-50 mph and doing some hard braking then light braking, then 10 minute ride to cool them down. During this brake in procedure, I got a check engine light. Turned out, I got a bummed spark plug on my cylinder 7. No biggie, replaced the plug and went on my merry way. 

 

However, since I replaced the brakes and spark plugs, I have gotten HORRIBLE MPG. I used to average about 22 on the highway, 16-17 city, and 18 ish overall. Now I am lucky if I'm getting 15 on the highway after shes warmed up and I've been driving for 15-20 minutes at a steady 65-70 with cruise control on. I am ALWAYS babying the gas trying to maximize fuel economy, but no matter how easy I drive, I still get horrible gas milage. I do live in Nebraska, and it has been cold here... but this issue started while it was still 50-60 degrees out, and I have never gotten this bad of gas milage in the winter. Sure it might drop down to 19 on the highway from 22, but never down to 14.

 

One additional thing to note is about 1-2 weeks after the tune up, I did recently get a check engine for the trans temp sensor. I cleared it, and it has yet to come back, but I have noticed the trans temp on the dash is hopping around quite a bit. Could this trans temp sensor have anything to do with the poor MPG? Maybe the trans isn't behaving as it should due to this faulty sensor? Think the spark plugs could be the problem? I used to get north of 450 mile per tank, and recently have barely been able to get 320. 

Any Ideas would be appreciated! 

 

 

CamGTP Senior Enthusiast

CamGTP

Posted
Posted

If I was trying to figure it out I'd be looking at a data log to see how the engine is running on the freeway. Like watching various sensors and fuel trims to see what they are reading.

 

If you haven't ever cleaned the MAF sensor, I would do that too.

  • Like 1
PhilB Enthusiast

PhilB

Posted
Posted

Ditto on what CamGTP said.  Plus since you did a brake job, I would also check to make sure you don't have a brake dragging. 

If you still have the old plugs, you could put them back in to see if your MPGs go back up.  If the MPGs do go back up, then the NGK plugs are the issue.  

 

Just a thought...

  • Like 1
asilverblazer Senior Enthusiast

asilverblazer

Posted
Posted

In addition to the above:

The transmission temperature sensor, if it is bad, could be preventing torque converter clutch lock up; this would lower mpgs, especially on the highway.

  • Like 1
GMJunkie7 New Member

GMJunkie7

Posted
  • Author
Posted
4 hours ago, PhilB said:

Ditto on what CamGTP said.  Plus since you did a brake job, I would also check to make sure you don't have a brake dragging. 

If you still have the old plugs, you could put them back in to see if your MPGs go back up.  If the MPGs do go back up, then the NGK plugs are the issue.  

 

Just a thought...

Unfortunately I dont have the old plugs, otherwise I would do just that. I tossed them with all the packaging from the other components. 

I did think about the brake dragging, but I have checked the rotor temps after a long ride and don't seem to have any big differences in temperature. I'm also not putting any more foot into the pedal, it just seems like as soon as i rest my foot on the pedal the instant MPG meter drops to below 10, even during slow acceleration. 

 

I will for sure try the MAF sensor and report back. Not sure how to look into the data log but I am sure I can figure it out. 

4 hours ago, asilverblazer said:

In addition to the above:

The transmission temperature sensor, if it is bad, could be preventing torque converter clutch lock up; this would lower mpgs, especially on the highway.

This may make the most sense to me. its funny, sometimes it seems like all of a sudden I am getting better gas mileage again ( judging by the instant meter) and I jump back to the trans temp reading and it shows a steady temp. Almost like sometimes the sensor does behave correctly, and when it does, that's when the mpgs go back up, but it could just be my imagination... that instant mpg meter doesnt tell the whole story. 

 

  • Like 1
reardiff Enthusiast

reardiff

Posted
Posted

If you have a 2016 with 6.2, there's extended coverage on the trans temp sensor. GM released a special coverage that extends the warranty to repair this, up to 10 years or 120,000 miles. It's special coverage #N192291660.  This isn't a cheap fix, mine went out not long ago and was $900 out of pocket. They have to drop the pan and replace the sensor and harness. For whatever reason the special coverage only applies to model year 2016. Although I'm not sure this has anything to do with your MPG issue, I had the same as you with erratic trans temp readings then eventually a check engine light that would come on and off but didn't seem to change MPG.

 

Here's a separate post on it you may find helpful. 

 

 

 

 

 

  • Like 1
newdude Senior Enthusiast

newdude

Posted
Posted

Are you getting any codes for transmission temp sensor fault?  

 

If you have no brake drag, and the transmission temp sensor isn't at fault, I'd get a set of OEM plugs.  Use the old # 12622441 and not the new one 19459511.  Don't get an "OE equivalent".  

  • Like 2
GMJunkie7 New Member

GMJunkie7

Posted
  • Author
Posted
2 hours ago, newdude said:

Are you getting any codes for transmission temp sensor fault?  

 

If you have no brake drag, and the transmission temp sensor isn't at fault, I'd get a set of OEM plugs.  Use the old # 12622441 and not the new one 19459511.  Don't get an "OE equivalent".  

I did have a code for the trans temp P0711/ P0700 When the codes were there, the shifting was very erratic. I cleared the codes to see if they would return, and they have not. It's been almost 3 weeks since those codes popped up and then were cleared. Shifting has returned to normal, but the trans temp display sometimes bounces +- 5 to 7 degrees every few seconds. 

 

I have a heard time believing the NGK plugs could be at fault, but again, there's not much else it could be I suppose. 

newdude Senior Enthusiast

newdude

Posted
Posted
48 minutes ago, GMJunkie7 said:

I did have a code for the trans temp P0711/ P0700 When the codes were there, the shifting was very erratic. I cleared the codes to see if they would return, and they have not. It's been almost 3 weeks since those codes popped up and then were cleared. Shifting has returned to normal, but the trans temp display sometimes bounces +- 5 to 7 degrees every few seconds. 

 

I have a heard time believing the NGK plugs could be at fault, but again, there's not much else it could be I suppose. 

 

 

Start with the P0711 first then.  As someone else mentioned already the converter might not be locking due to it not knowing the fluid temp which could decrease MPG.

 

As for the plugs, you'd be surprised.  Modern GMs are VERY sensitive to aftermarket engine components.  Plugs, wires, MAF, MAP and especially O2 sensors.

 

 

  • Like 3
  • 5 months 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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   7 Members, 0 Anonymous, 1,689 Guests (See full list)

  • Latest Articles

  • Posts

    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • 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 agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
    • Grumpy Bear
      OCI, not when but why?

      By Grumpy Bear · Posted

      I went to the county a few years back to dispute my property taxes. To do that I hired an appraiser and a lawyer. The County Assessor wished to argue that the homes in my neighborhood the appraiser used were all 'distressed properties" and not representative of the "Market Average".    My response was," Of the 50 homes in our subdivision 43 of them were "distressed properties" under bank foreclosure and as such "Distressed IS the market". Lawyer about choked on his coffee and handed the Assessor the 'receipts'.    I won that case on the evidence provided by the Lawyer and the Appraiser.    We have the same thing going on here. My statements were based on the GOVERNMENTS NATIONAL DATA and yours on local markets in areas of your interest. They are both correct....   Thing is, this divergence was based on NATIONAL and not on LOCAL. I think you even understand that. But like you said, we are both stubborn and hardheaded.    I do not see any advantage to disengagement.  But that said we can step back to compose ourselves. 
    • revmanii
      Looking at ordering a '26 WT because I want a std cab, std bed

      By revmanii · Posted

      Trust me I appreciate the comments and concerns. It's what I was looking for to help me evaluate the situation and what I want to do. I have decided to move forward with the BORA hubcentric slip on 3/8" (.375") with the extended lugs nuts. Fedex says they should be here Monday :). Meanwhile, the dealer got the remote start and Patriot spray in bed liner done over the last couple of days. Also, I installed an inline stop/start eliminator today. Starts back up in what whatever mode you shut it off in, so you don't have to hit the button every time you fire up.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...