Jump to content

Recommended Posts

Posted

Hello all, ive recently bought a new to me single owner 2014 gmc sierra 4.3 4x4 double cab with 43,000 miles on it. It has flex fuel standard and was wondering wether or not i should run e85. It is available local and pretty cheap, but ive heard that if the truck has ran gas most of its life the e85 would cleanse the deposits and possibly clog the fuel lines or fuel pump. Should it be safe to switch over to e85 ? Or could i just start running 89 since ive also read that its more beneficial running 89 or 93 over 87 due to detonation 

  • Like 1
Posted

Running E85 will be fine.  MPG will suffer drastically, but that’s because mpg drop vs ethanol increase is very linear.  It comes down to prices of fuel, so you will need to calculate cost per mile.

 

I have found running approx E30 mix gives me a better cost per mile vs just straight e85 in my 5.3, mixing about 7 gal e85 and the rest 87.   I use a scanner for ethanol mix readouts.  Mix is usually E24 or better as I have a 91 oct tune and try to keep it above e20.  E85 can be as low as e50 in winter months.

 

Every engine is different.  There was a study done to push ethanol fuels at the pump and they found the different test cars had varying results w the different fuel mixes….so your results may vary.

  • Like 1
Posted

You can run it if you want.  Expect to lose 2-4mpg. 

 

Stock power on 87 is SAE rated 285hp, 305tq.  On E85, SAE rated 297hp and 330tq.

Posted
2 hours ago, scrapen said:

Running E85 will be fine.  MPG will suffer drastically, but that’s because mpg drop vs ethanol increase is very linear.  It comes down to prices of fuel, so you will need to calculate cost per mile.

 

I have found running approx E30 mix gives me a better cost per mile vs just straight e85 in my 5.3, mixing about 7 gal e85 and the rest 87.   I use a scanner for ethanol mix readouts.  Mix is usually E24 or better as I have a 91 oct tune and try to keep it above e20.  E85 can be as low as e50 in winter months.

 

Every engine is different.  There was a study done to push ethanol fuels at the pump and they found the different test cars had varying results w the different fuel mixes….so your results may vary.

Yeah ive somewhat done some calculations for cost per mile and found e85 to be cheaper per mile in the end. So you believe its fine running it despite gas being in the tank for 43,000 miles? No problems with the ethanol cleaning the buildup?

Posted
52 minutes ago, newdude said:

You can run it if you want.  Expect to lose 2-4mpg. 

 

Stock power on 87 is SAE rated 285hp, 305tq.  On E85, SAE rated 297hp and 330tq.

Those numbers seem so much better imo. Will the mpg loss be just in city driving or highway as well

Posted

I don’t know from experience of any clogs, but I would think at just 43k you should be fine.
 

Mileage is always affected across the board.  Of about 3 years of logging (12000 miles), E85 has averaged about 15, mixes around 17, and 18 on premium.  


In terms of cost, mixes have saved me 28% at only 8% mpg loss compared to premium, which I record cost of every time for comparison.

 

e85 saved 31% but 20% mpg loss.  
 

I should note all e85 tests were during summer months, and winter months is mostly premium only.



 

 

Posted

Mine first saw E85 at almost 120K.  No problems whatsoever, these engines love the stuff.  It will take several tanks to get up to full strength and for the computers to adjust for it.  

 

We don't care about reduced range unless we need long range, the measure of performance is cost per mile.

 

After five years, the difference in MPGs between gasoline and E85 is between 18% and 24% depending on the average speed for that tank of fuel.

 

My old Gen IV 5.3 gets its best mpgs with an ethanol content of between 15% and 22% or so.  

Posted

I lose more fuel mileage in the city than on the freeway. Gets about 12-13 around town on E60+ and can still do 20mpg on long freeway trips. Regular fuel gets 14-16mpg and 22ish. These are all summer numbers because I do not run that fuel in the winter, gets way too cold here for that.

  • Like 1

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
  • Latest Articles

  • Posts

    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
    • It was all part of the tiny bit of fuel savings it goes towards what was mandated by the government. Much like cylinder deactivation. That was relaxed by the recent administration. All that doesn’t help the individual buyer. But as a whole helps the manufacturer to try to reach the previous ridiculous past mileage per gallon mandate. So yes it was mandated and added cost to the vehicle. 
    • You do realize that auto stop/start...was never mandated by the fed...right?     EPA Says It's 'Killing' Stop-Start, and Here's What Automakers Have to Say   "Start‑stop technology has never been federally mandated, and the EPA’s recent action removes regulatory incentives associated with it rather than prohibiting its use."
    • Anytime the government mandates something, you can bet on it being absolutely senseless.
    • just logged my best MPG for one leg this am - drove home from the Denver Airport, 45 min drive - all freeway, lots of traffic so speeds were limited and some stop and go, got 17.7 for the ~30 mile trip.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...