Jump to content

A different kind of 6.2 question

SierraJoe1110
 Share

Recommended Posts

EX-F150 owner Enthusiast

EX-F150 owner

Posted
Posted (edited)

I live in Central Ohio and had to drive North of Detroit to get mine. I called every dealer east of the Mississppi looking for a Black on Black with every option and the max towing package. They were the only dealer to have one. I am lucky I got a supplier discount so I did not have to negotiate for it

I purchased mine from Madision Ohio. I live in Northern VA. The seling dealer shipped it down to me when I purchased it. Funny, sounds like we have the exact same trucks. Mine also has the NHT with every option available. MSRP was just a tad over 52K. Was discounted to 40K as a model year left over. Mine is Granite black on black.

 

There was not much to pick from around here when I was shopping. I couldn't even get my local Chevy dealer to order one for me :nonod:

Edited by EX-F150 owner
RyanbabZ71 Senior Enthusiast

RyanbabZ71

Posted
Posted

I ordered mine October 2009. I believe mine was one of the 1st 2010 LT 6.2's

 

 

Ryan

 

 

SierraJoe1110 Enthusiast

SierraJoe1110

Posted
  • Author
Posted

Funny story. I wen to the dealer where I bought my truck, my mom bought her Envoy and my dad bought his new Sierra, just poking around. I was talking to the salesman we all dealt with and I mentioned this 6.2 dilemma. It just so happens last March he ordered a extended cab 6.2. He trades his trucks every two years and said he will give me a call when he orders his '14 and we can make a deal. I won't be forgetting that, and I guess I have a year to save my pennies!

mferry22 Enthusiast

mferry22

Posted
Posted

I live in Ma. and my dealer only had a 6.2 in the LTZ trim and $50k so they had to get one from another dealer about 200 miles away with the options I wanted. I also agree that trade in value wont be to much more than a 5.3 but I think private party sales they would get alot more especially if there are problems with the new gens afm.

music Senior Enthusiast

music

Posted
Posted

I live in Ma. and my dealer only had a 6.2 in the LTZ trim and $50k so they had to get one from another dealer about 200 miles away with the options I wanted. I also agree that trade in value wont be to much more than a 5.3 but I think private party sales they would get alot more especially if there are problems with the new gens afm.

 

I think the opposite is true for most folks. The common question I hear is "what kind of mpg does it get". I don't think I've ever been asked "how fast is it" in real life, by adult men. I personally would pay a little more for one, but I'm in the large minority to even know the difference between the options. I wouldn't know much at all if I didn't visit this site!

mossbum Enthusiast

mossbum

Posted
Posted

I live in Northeast Arkansas which is serious farm country so that might explain why there are so many in my area. In a recent dealer search I came up with about 10 brand new 6.2s within about an hour drive. SLE/LT as well as SLT/LTZ and with both rear end options.

Big Whiskey Senior Enthusiast

Big Whiskey

Posted
Posted

I live in Northeast Arkansas which is serious farm country so that might explain why there are so many in my area. In a recent dealer search I came up with about 10 brand new 6.2s within about an hour drive. SLE/LT as well as SLT/LTZ and with both rear end options.

Wow. That's impressive. If that was the case where I live, I'd have a 6.2 for sure.

VMaxtastic Enthusiast

VMaxtastic

Posted
Posted (edited)

I just ordered my 2013 through one dealer, who got it from another about 50 miles away. There are a few around here, in Western Canada, for sale. But finding the right one is tricky. I was picky.

 

They are delivering it to me at work (I'm in the oil patch) on Tuesday, and taking my Vmax as a trade.

Edited by VMaxtastic
VMaxtastic Enthusiast

VMaxtastic

Posted
Posted

Around here they can be found easily on GMC lots......Not many at all on Chevy lots, maybe 2 or 3, they usually have to order them.

Same here... No Chevy 6.2 in sight, they were all GMC

Z28turtle New Member

Z28turtle

Posted
Posted

I live in Ontario and a dealer (Vickars) in Winnipeg found one in Saskatchewan. They are like hens teeth around here.

MikeNH Senior Enthusiast

MikeNH

Posted
Posted
I live in Ontario and a dealer (Vickars) in Winnipeg found one in Saskatchewan. They are like hens teeth around here.

 

 

That's cause that fancy Canadian gas costs so much more than the American stuff.

 

 

 

Nevermind that the gas in my tank now likely was made from oil recovered in Alberta. :lol:

 

 

Sent from my iPhone using Tapatalk

  • 8 years later...
swathdiver Senior Enthusiast

swathdiver

Posted
Posted (edited)
On 2/18/2013 at 10:57 PM, SierraJoe1110 said:

So I gotta know... I am always looking at the dealer inventory, never know when the new truck bug might bite. I would only trade my truck for a 6.2. I have never ever seen one fore sale in M.A. or C.T. So I gotta know, where the heck do all you 6.2 drivers live that they seem so plentiful. Its just weird that there are none around here

Yes, I know this thread is old but have been currently looking for the last year.  Someone currently on the hunt might benefit from what I've learned.

 

Most of the NHTs I find are in and around the Rocky Mountains and have also found one of those Houston ones and another in Kansas. 

 

Most are Crew Cabs, Extended Cab NHTs are more rare then hens teeth.

Edited by swathdiver
additional information

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   6 Members, 1 Anonymous, 1,658 Guests (See full list)

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