Jump to content

Recommended Posts

Posted (edited)

 

Edited by laketboy
Posted

In the summer I average 17 mpg. On my mostly rural commute. Live in a hill town it's about a 1800 ft elevation change from home to work about 25 miles away. I have the Diablo intune running 87 octane tune. Tires calibrated correctly and AFM turned off. I lose almost a 1 mile per gallon in winter.

I can get 21-22 mpg on the highway over along trip. I am also running duratracs 277/65r 20

So what about the winter and summer that changes how much mpg you get?

Posted

Engines run richer because the air is more dense and also winter blend fuel is not as efficient. Occasionally I do let the truck warm up also

21-22 @ 75? or what speed? Not bad on 34" tires and a lift!

Posted (edited)

Here's my set up.

 

Anthem A712 Defender wrapped around Toyo Open County A/T II Extreme. 275/55r/20

 

IMG_3548.jpg

 

IMG_3547.jpg

Edited by acc412
  • Like 2
Posted

 

 

 

Did you by chance have a picture down the side (from the rear) of your truck after the bilstein/305/55/20 G2s? I was curious roughly how far they might stick out. I feel like my stock 275/55/20 are fairly flush. Curious what to expect when I go up to the 305 g2's

Posted (edited)

Here you go. Sorry pics are a little dark. They hardly stick out and are almost flush. Maybe 1/2-3/4" max. I don't like the look with tires much outside the wheel wells until you go with 6"+ lift and and the 36-37" or larger tires, then some still get them out there and they don't look great IMO...

Did you by chance have a picture down the side (from the rear) of your truck after the bilstein/305/55/20 G2s? I was curious roughly how far they might stick out. I feel like my stock 275/55/20 are fairly flush. Curious what to expect when I go up to the 305 g2's

 

post-166178-0-70688200-1484683688_thumb.jpg

post-166178-0-75656200-1484683693_thumb.jpg

post-166178-0-70688200-1484683688_thumb.jpg

post-166178-0-75656200-1484683693_thumb.jpg

post-166178-0-70688200-1484683688_thumb.jpg

post-166178-0-75656200-1484683693_thumb.jpg

post-166178-0-70688200-1484683688_thumb.jpg

post-166178-0-75656200-1484683693_thumb.jpg

Edited by laketboy
  • Like 1
Posted

Here you go. They hardly stick out and are almost flush. Maybe 1/2-3/4" max. I don't like the look with tires much outside the wheel wells until you go with 6"+ lift and and the 36-37" or larger tires, then some still get them out there and they don;t look great IMO...

 

Thanks. I have similar opinions. I was worried how far it may have possibly stuck out. I'd rather have more width in the tire, but if it meant the tire was going to stick out obnoxiously then I would be willing to sacrifice tire width if it meant not having my tires way out.

Posted

Thanks. I have similar opinions. I was worried how far it may have possibly stuck out. I'd rather have more width in the tire, but if it meant the tire was going to stick out obnoxiously then I would be willing to sacrifice tire width if it meant not having my tires way out.

Agreed! Reminder these are on 20x9 with +18 offset. Continue to be impressed with how great these ride and how quiet they are.

Posted

21-22 @ 75? or what speed? Not bad on 34" tires and a lift!

 

Mixed speeds of 65 mph to 80 mph. Probably averaged 70. This was on my camping trip last summer. I honestly do not hit the highway often
Posted

My fuel economy has dropped significantly in the city with my new tires. I was getting 15 to 16 in the city now I'm averaging 10 to 12. Didn't expect this much of a drop. I have a cai and exhaust. Any ideas?

Posted

My fuel economy has dropped significantly in the city with my new tires. I was getting 15 to 16 in the city now I'm averaging 10 to 12. Didn't expect this much of a drop. I have a cai and exhaust. Any ideas?

 

 

What size/weight tires? Did you recalibrate your speed 'O? Are you driving a little harder trying out the new shoes like everyone does like when they get a new exhaust or CAI?

  • Like 1
Posted

My tire size is 285/70/17. I did not recalibrate yet. I know the mpc difference and take that into account but my normal driving has dropped and I'm not pushing it

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

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • 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?
    • 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
    • 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...