Jump to content

Purchasing a '14 Sierra (First Truck) Have a few Questions

JGMC

Recommended Posts

JGMC Enthusiast

JGMC

Posted
Posted

Hi all, it's getting about the time to get a new vehicle, and while I had decided that I was going to go with full truck this time around, I recently settled on the Sierra after looking at whats out there and test-driving them. I currently drive an '03 Envoy SLT 4WD that I bought new 10 years ago and am buying in Dec/Jan. (May be earlier if I have to order)

 

 

I work as an environmental scientist (wetland restoration), and enjoy hunting/fishing/paddlesports.

 

Functionality I need:

  • Haul muddy equipment/clothing (I currently use large rubbermaid bins in the trunk)
  • Work reliably in the sand, mud up to 6", and snow (No longer trust current 4WD system in my Envoy)
  • Tow 12-16 foot rigid inflatables and center consoles (2-5000 lbs w/trailer)
  • Good MPG (In the truck world)

 

The features I want are:

  • Crew Cab Short Box
  • SLE Trim
  • Value package
  • Convenience Package
  • All-Terrain Package
  • Integrated trailer brake
  • Black, Iridium, or Stealth Grey
  • 5.3 V8

Aftermarket additions I am considering:

  • Diamondback 270-S tonneau
  • Bedrug Bedliner
  • Some sort of simple, black, nerf board/step
  • Front/Rear Mudflaps
  • All Weather floormats
  • Some sort of simple bull bar
  • Two forward roof mounted widebeam lights
  • Two Rear roof mounted lights that I can point where needed

Now for the questions I have.

  1. Should I go with the 3.42 rear ratio or the 3.08? I'm coming from the 4.1 on the Envoy, and my MPG avg is around 12. I would much rather see that at 18.
  2. Do I really need the V8, or should I get the V6?
  3. I have no interest in any big lift, I need the bed of the truck to be easily accessible for equipment/entry. Will the stock configuration of the All-Terrain be suitable for my needs?
  4. Will leveling the front add any functionality besides appearance?
  5. Can you get the rear sliding window with the all-terrain? I couldn't find it on the website.
  6. Any other additions/aftermarket or factory/dealer you would recommend?

 

 

On a side note, anyone else notice that the all-terrain package option is missing on the GMC Build-It-now? You can add the components which appears to add the package, but it doesn't list it as an added package now.

 

I was also trying to get the LPO/RPO codes for the packages/options to send out to dealers but having problems finding them for the 2014 Sierras, any ideas?

 

Thanks for your thoughts/feedback/help I do appreciate it.

 

 

 

GMC-AT Senior Enthusiast

GMC-AT

Posted
Posted

1. 3.42 - end of story. Do some research.. pretty much everyone that got the 3.08 hates it.

 

2. V8 ( dont think you can get a V6 with All Terrain)

 

3. Yes

 

4. Not really - but I does make the truck look better.

 

5. Yes, I have it on mine.

 

6. just get what you need.. as noted above..

newdude Senior Enthusiast

newdude

Posted
Posted

- 3.42 gears and the 5.3 all the way. Will give you the towing grunt you need but also get fuel economy. Best of both worlds the 3.42 and 6 speed transmission.

 

- As for accessories...I may be slightly biased...but...GM makes some pretty nice boards if you aren't looking for one that is "special." Black or chrome, 4 or 6 inch, and they mount up from behind the rocker panel area, not using the body mounts like some aftermarket running boards do. Body mount mounted boards can lead to squeaks/creaks down the road with the body mounts.

 

- Floormats, in my opinion, Weathertech. I have had 3 sets and love them.

 

- The OEM molded mudflaps are quite popular and look good and function nice.

 

- Have you considered a spray in bedliner vs the bed rug?

 

- The GM LED bed cargo lights are a nice addition. They plug right in and work with the cargo light switch in the truck. If you consider these, make sure they are on the window sticker already as its only a $60 option. If you buy them after you buy a truck, its $135.

 

RPO codes:

 

All Terrain package: GAT

 

SLE Value Package: PDU

 

SLE Convenience Package: PDD

 

LPO, Black tubular assist steps, 4": RVS

 

LPO, Black tubular assist step, 6": RVQ

 

LPO, Front and Rear Molded Splash Guards: VQK

 

Trailer Brake Controller: JL1

 

3.42 axle ratio: GU6

 

Cargo Box LED Lighting: UF2

redwngr Senior Enthusiast

redwngr

Posted
Posted

Consider the double cab with the standard box. (which today is the 6.5 footer as the 8 footer we used call 'standard' is now labelled a 'long' box)

Same wheelbase (both are 143.5" WB), but more outside storage (assuming that rear seat passengers is occasional rather than everyday)

 

Crew cab, standard box would be a 153" wb. ( fwiw, the heavier series 2500/3500series crew cabs are only available as std box or long box.)

 

Black trucks are gorgeous when clean, but .......you know the rest. And they get hotter sitting in the sun.

crushNchowda Senior Enthusiast

crushNchowda

Posted
Posted

I'm one of the people here who hated the 3.08 w/ 5.3 combo, so much so that I traded the truck back in on a 3.42 equipped black All terrain SLT - couldn't be happier. Based on what you're going to do w/ the truck, I would absolutely get the 3.42s - my MPG only suffered .7 overall. And I'm a very good barometer for that considering I drove the 3.08 for 5,000 miles and the 3.42 for 3,000 miles so far. If you're worried about MPG I wouldn't step up to the 3.73 as you'll probably lose another .5-1 mpg and then you're dipping into like 17hwy ouch.

 

ALso based on what you say you'll use the truck for I would absolutely get the bed sprayed w/ rhino liner or line-x, and not the bed rug.

 

Lastly, based on what you say you'll be using it for it may make sense to order an All Terrain with the chrome bumper that has the integrated assist steps, most AT's come w/ body matched bumpes and no step.

 

I have a black AT w/ the chrome 6" steps and body colored "higher end" OEM mudguards - great looking combo.

 

Lastly, I also have the weathertech mats and love them. And, I went crew cab long bed, its huge but it is basically like a luxury SUV w/ a giant bed and nice rims.....

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • 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?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...