Jump to content

Trade my truck for a jeep

Zrodie21

By Zrodie21
in The Off-Topic Bar

Recommended Posts

Zrodie21 Enthusiast

Zrodie21

Posted
Posted

Should I trade my truck for a jeep

 

Mine is a 2014 Silverado 1500 5.3 V8 with 7 inch lift 35s dual exhaust and color matched front grille with 59000 miles on it.

His is an 07 with 91000 miles and a lot of upgrades.

 

 

Sent from my iPhone using Tapatalk

 

https://r.tapatalk.com/shareLink?url=http%3A%2F%2Fwww%2Egmfullsize%2Ecom%2Findex%2Ephp%3Fposts%2F5875681%2F&share_tid=305489&share_fid=11691&share_type=t&share_pid=5875681

 

 

Sent from my iPhone using Tapatalk

SouthernSilveradoGuy85 Senior Enthusiast

SouthernSilveradoGuy85

Posted
Posted

I would say no. You'd be down grading for a smaller vehicle that isn't that practical with ugly rims and low pro off-road tires that too me doesn't make much sense. The LEDs around the rotors look cheezy to try to show off the rims even more. Personally the only thing I like on that Jeep is the front bumper with a Winch. Something tells me he's never used the Winch and might not even know how to use it. If a Jeep owner actually uses it off-road they wouldn't get those rims and low pro tires. Aftermarket stuff doesn't add value like some people think and hope they do. If you feel like you don't need a truck and would prefer a Jeep then buy a stock Jeep and do it up exactly how you'd want.

Zrodie21 Enthusiast

Zrodie21

Posted
  • Author
Posted

Lol thanks guys. I don't know what I was thinkin [emoji23]

 

 

Sent from my iPhone using Tapatalk

BlackZ71Silverado Senior Enthusiast

BlackZ71Silverado

Posted
Posted

NO! Absolutely not!

 

Jeeps are good to have as a second or third vehicle but not a primary in place of a truck, no way.

I actually just got rid of my 2015 Malibu and picked up a 2016 Wrangler Sport S. It's a nice little puddle jumper but really small inside and not really comfortable to be honest. The 6 speed is fun to drive and the little V6 is pretty impressive so far. I got it just because I guess, I had a Jeep CJ7 in high school and have been wanting another Jeep so I went for it. A lot of upgrades planned so it's going to be a money pit, just like my CJ was!

BIGDOGx Senior Enthusiast

BIGDOGx

Posted
Posted

Sure if your buddy is kicking in another 10 grand or so to offset the values on both. Looks like Jeeps in the 07 year with near 100k on the od go anywhere from 15-20 grand dealer price. Your truck is anywhere from 25-30 grand dealer price imo depending on options.

 

IMO why? That Jeep no offense is hideous imo, your truck is twice the vehicle then that jeep will ever be no matter how much cash he sinks into it. My advice is hell no especially if you are talking even swap, I would question if that is actually a real friend if he thinks they are identical in value, only in a jeep lovers mind!

Zrodie21 Enthusiast

Zrodie21

Posted
  • Author
Posted

I preciate the insight guys. I must've been drunk when I was even considering it. Lol

 

 

Sent from my iPhone using Tapatalk

MikeNH Senior Enthusiast

MikeNH

Posted
Posted

No. I own a 2 door and disagree that they're poor daily drivers but the 2007-2011s had the dog of a 3.8L V6. They were slow stock, never mind bigger tires and those terrible rims. 2011 got a much upgraded interior and 2012 got the much better 3.6L V6 and a better automatic transmission.

KARNUT Senior Enthusiast

KARNUT

Posted
Posted

I find it amusing when people call a different brand a pos, know a couple guy who gut pretty good money for older jeeps. More than same year model ford or GM. When the last time anyone heard of a 1,000,000 mile GM or Ford p/u like the Tundra just bought back by Toyota. Nothing but regular mantiness.

KARNUT Senior Enthusiast

KARNUT

Posted
Posted

I'm not a small jeep person myself. I was just amazed on how popular they are. A brother of a long time employee has an old 2 door (C J ) I think, 15 years old lifted big tires soft or hard top beat on pretty good keeps on going. Depends on what you like, it's just not ones better than the other.

SnakeEyeSS Senior Enthusiast

SnakeEyeSS

Posted
Posted

Jeeps can't be good off road. The one I was just behind slowed down To 15 mph to go over railroad tracks while The corolla~ in front of it went 40. :lol:

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