Jump to content

Thinking Of Trading My 08 Sierra Sle Vmax For A 07 Silvy Vmax Ltz

Josh185

Recommended Posts

Josh185 Enthusiast

Josh185

Posted
Posted

Ok, so here is the story, A few months ago I bought a 2008 Sierra Vmax CCSB SLE trim. The truck is pretty basic aside from it having the Vmax drive train. Cloth interior with basic audio head unit and HVAC system. Its 4x4 with the Z71 package, 3.73 gears and a G80 locker. Pic of it is in my sig.

 

Now, today I found out that the same dealership has an 2007 Silverado Vmax CCSB LTZ trim. Being the LTZ trim, it is much nicer equipped. Drivetrain wise, its exactly the same, but interior wise, its like upgrading to a Cadillac. It has a DVD/NAV head unit with Bose sound system, auto HVAC, rear entertainment system, sunroof, and ebony leather. External color is Black, which I do like a little better than my dark blue. The Silvy has 42k miles vs mine with 44k miles.

 

Here is where my debate is. My uncle whom works at this dealership and whom I bought my Sierra from, says he may be able to get me an even or near even trade. I will probably go see it in person tomorrow. I really like the Silvy LTZ because of its color and added options but I am not sure its worth trading an 08 for an 07. Is the trade process worth it?

 

I am looking for opinions from the folks here to see if I should give it a serious try. What would you do in my situation?

 

- Josh

summerfieldmd Enthusiast

summerfieldmd

Posted
Posted

Do it! Same body styles, so I think its no harm done. On thing maybe is the whole 5 year drive terrain warranty will be coming up... but im sure u can get a hook up for an extension or something.

Stevens03 Senior Enthusiast

Stevens03

Posted
Posted

Never never ever settle. It always costs you more. :dunno:

 

I say go for it. A few years from now, it will be a wash anyways. The LTZ will be worth more than the SLE so in the end, it will still be a wash. Just go over the truck good before making a decision. :)

MikeNH Senior Enthusiast

MikeNH

Posted
Posted

I don't know if these trucks had issues with the first model year but I'd be apprehensive about buying a truck from the very first of the 900s.

Stevens03 Senior Enthusiast

Stevens03

Posted
Posted
I don't know if these trucks had issues with the first model year but I'd be apprehensive about buying a truck from the very first of the 900s.

 

I owned an 07 SLT Vmax and had near zero issues :)

beave84 Enthusiast

beave84

Posted
Posted

If the payments are cool with your wallet..go for it. Its so much more rig and it seems you current truck ins't quite what you wanted so I say do it. The fact that its a year older won't matter much on value since you added so much in extras... the nav/dvd upgrade is a $2200 option alone on a new one.

mfennema Enthusiast

mfennema

Posted
Posted

If I were in your shoes I'd do it. The upgrades would be very nice other than the Bose....not my favorite.

 

I haven't had many problems with my 07 either so I don't think I'd worry about that being an issue.

dogzapper Enthusiast

dogzapper

Posted
Posted

Absolutely DO IT.

 

The LTZ is soooo nice. That and the NAV unit will help your new truck retain value.

 

Steve

 

PS. We need photos of you and your new truck. :grin:

L76PWRD Enthusiast

L76PWRD

Posted
Posted

I wouldn't do it, If I were to trade my V-Max it would only be for a 2012 Silverado LTZ 6.2l with 6 Speed. But if I was in your situation I would the LTZ is a nice upgrade from an LT which is similar to an SLE. In a trade in with similar miles, the LTZ would bring in more money than the SLE. I love my LTZ only options I wish it had would be the power sliding rear window & sunroof, it has everything else. When buying a truck never settle for less if you can.

music Senior Enthusiast

music

Posted
Posted

Well, since you asked what "I" would do... I would keep what I had. I prefer the SLE/LT trim in a truck and don't care for built-in NAV/DVD/etc. systems, so that makes it easy. I'm not much for trading a good vehicle for an unknown... but that's me. It doesn't matter what "I" like though, since I won't be driving it :)

Doug_Scott Senior Enthusiast

Doug_Scott

Posted
Posted
I wouldn't do it, If I were to trade my V-Max it would only be for a 2012 Silverado LTZ 6.2l with 6 Speed. But if I was in your situation I would the LTZ is a nice upgrade from an LT which is similar to an SLE. In a trade in with similar miles, the LTZ would bring in more money than the SLE. I love my LTZ only options I wish it had would be the power sliding rear window & sunroof, it has everything else. When buying a truck never settle for less if you can.

 

Which is it, you would do it, or you wouldn't do it?

crepitus Enthusiast

crepitus

Posted
Posted
Well, since you asked what "I" would do... I would keep what I had. I prefer the SLE/LT trim in a truck and don't care for built-in NAV/DVD/etc. systems, so that makes it easy. I'm not much for trading a good vehicle for an unknown... but that's me. It doesn't matter what "I" like though, since I won't be driving it :)

Yeah the only thing I would be scared of is getting someone elses headache.

L76PWRD Enthusiast

L76PWRD

Posted
Posted
I wouldn't do it, If I were to trade my V-Max it would only be for a 2012 Silverado LTZ 6.2l with 6 Speed. But if I was in your situation I would the LTZ is a nice upgrade from an LT which is similar to an SLE. In a trade in with similar miles, the LTZ would bring in more money than the SLE. I love my LTZ only options I wish it had would be the power sliding rear window & sunroof, it has everything else. When buying a truck never settle for less if you can.

 

Which is it, you would do it, or you wouldn't do it?

 

 

Wat I meant was that in his situation I would trade it in and I meant that if I were to trade in my V-Max it would only be for a 2012 Silverado LTZ 6.2l with 6 Speed Auto.

Archived

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

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,770
    Total Members
    8,960
    Most Online
    Paul8556
    Newest Member
    Paul8556
    Joined

  • Who's Online   4 Members, 0 Anonymous, 592 Guests (See full list)

  • Latest Articles

  • Posts

    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Coastie05
      2027 GMC Sierra: Official Discussion

      By Coastie05 · Posted

      Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • Jake87
      2027 GMC Sierra: Official Discussion

      By Jake87 · Posted

      AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • NDKoze
      2027 GMC Sierra: Official Discussion

      By NDKoze · Posted

      If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...