Jump to content

Recommended Posts

Posted

I use 89 octane at the advice of Blackbear tuning. They recommend at minimum using 89 octane even on STOCK tuning (for the 5.3 and 4.3). 6.2 motors should be using a minimum of 91.

Posted

I use regular 87 for daily driving and I use premium 91 for towing my 6000lbs camper... sometimes the boat too at 3500lbs, but not always... depends on how full tank already was... but only premium 91 in the boat or else it pings.

Unless you are tuned for the higher octane or have the 6.2L engine, you are wasting your money filling up with 91 octane. Putting higher octane in your truck because you are towing something will not help with anything but making your wallet lighter.

 

 

Sent from my crappy iPhone 6

using Tapatalk

Posted

I use 89 octane at the advice of Blackbear tuning. They recommend at minimum using 89 octane even on STOCK tuning (for the 5.3 and 4.3). 6.2 motors should be using a minimum of 91.

That must have been you that I heard that from. Why did he recommend 89? Was it due to what he was seeing via engine knock sensors? My thoughts are that perhaps it was with 87 he saw some knock retarding happening while 89 was just enough to avoid it and 92+ wasn't necessary?

  • Like 1
Posted (edited)

89. These engines have to high of a compression ration to run the cheap stuff.

Edited by haider320
  • Like 3
Posted

I ran several tanks over two months with 93 and saw absolutely no difference from 87. Now I stick with 87 and save ~$10 a tank.

  • Like 2
Posted

I use 87 exclusively and only fill up at Shell, BP, Chevron, or Mobil. My lifetime average fuel economy is 18.1 mpg for 8,000 miles. My typical highway economy is 21 mpg. I cannot run e85 because my 2015 engine is not compatible.

Posted

E85 or mid grade gas. E85 locally mid grade on trips.

 

 

Sent from my iPhone using Tapatalk

Posted

The 5.3 can get by with 87 but I bet it will show better numbers with 89 over the long run, the 6.2 with approximately 11.5:1 compression needs the good stuff, 93 octane is all my truck sees.

Posted

Unless you are tuned for the higher octane or have the 6.2L engine, you are wasting your money filling up with 91 octane. Putting higher octane in your truck because you are towing something will not help with anything but making your wallet lighter.

 

 

Sent from my crappy iPhone 6

using Tapatalk

It won't get me any better fuel economy and certainly costs me more, all true... but has better additives and runs cooler. It's worth the extra $$$ to run cooler when towing to me.

Posted (edited)

I have the 6.2 so I run 92 or 93 depending on where I gas up.

Edited by Last C5
Posted (edited)

E85 or mid grade gas. E85 locally mid grade on trips.

 

 

Sent from my iPhone using Tapatalk

This.

 

I average around 18-18.5 with e85 and 20.5-21 with 89. Financially it doesn't make any since to run regular gas as long as I can find e85.

Edited by Stars_Fan
Posted

E85 or mid grade gas. E85 locally mid grade on trips.

 

 

Sent from my iPhone using Tapatalk

 

Same thing here! Except I only use e85 when home and use gas when I go up north. I wonder if the motor will ever have long term effects with using roughly 95% of my fuel being e85. Thats what a warranty is for.

Posted

This.

 

I average around 18-18.5 with e85 and 20.5-21 with 89. Financially it doesn't make any since to run regular gas as long as I can find e85.

I pay between 1.35-1.65 for E 85, even if was the same price as mid grade gas Id buy it for the extra HP. I only use gas when I can't get E85 traveling.

 

 

Sent from my iPhone using Tapatalk

Posted

It won't get me any better fuel economy and certainly costs me more, all true... but has better additives and runs cooler. It's worth the extra $$$ to run cooler when towing to me.

This has me confused, can you explain why it would run cooler?

Posted

Ethanol burns cooler than gas, but your engine has to burn more e85 which makes it run hotter than burning gas.

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • 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.
    • 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.
    • 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?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...