Jump to content

Pics Of My Truck + New Wheels And Tires


countryboy_db

Recommended Posts

Posted

Hey guys, still fairly new to the forum so i thought id get some pics up here to show you my truck. Still working on figuring out how to get all the specs and stuff and all the information on here but that will come in time. Anyways i just spent all day Saturday cleaning her up all nice and pretty. I also just put on new wheels and tires: 18" Fuel Offroad Guage Blacks on 325/60/18 Nitto Terra Grapplers. Let me know what yall think of the combo, I personally love the "new" look.

 

182718_10150194058484008_506314007_8712752_4029256_n.jpg

180089_10150194057154008_506314007_8712730_3024672_n.jpg

180150_10150194057254008_506314007_8712732_7320668_n.jpg

180157_10150194057364008_506314007_8712733_4820307_n.jpg

180313_10150194057684008_506314007_8712742_7559392_n.jpg

181570_10150194057834008_506314007_8712743_7289100_n.jpg

180041_10150194057949008_506314007_8712747_7041166_n.jpg

179858_10150194058119008_506314007_8712750_26478_n.jpg

182059_10150194058259008_506314007_8712751_6090032_n.jpg

Posted

Thanks guys, what do yall think of the new wheels and tires? I was gonna go with the XD Monsters but it seems everyone around here is already running the monsters or the rockstars so i wanted to go a different route. Im extremely happy with the Fuel Offroads. If any of yall are on the East Coast and are looking to get new wheels and tires soon you have to check out Rimzone in Mooresville NC. They were absolutely excellenct and their prices were crazy cheap compared to everyone else around here.

Posted

truck looks great man... dual antennas on the bumper? where on the bumper? put them on the bed behind the cab like i did... check sig

Posted
truck looks great man... dual antennas on the bumper? where on the bumper? put them on the bed behind the cab like i did... check sig

 

 

I was originally planning on doing dual whips behind the cab but with the tonneau cover itd be a pain to mount them bc the cover is so 3m taped to the bedrails, but idk i might rank it off and put them behind the cab. The only other thing i sorta like about putting them on the bumper is they wont be banging the roofs and rafters of all the parking garages i park in EVERYDAY.... one at college, one at work sometimes upwards to 5 or 6 times a day depending if i have to leave and come back. I wouldnt think that would be good for the antennas not to mention the tuning they require. What do you think?

If i were to put them on the bumper, firestick makes a bumper mount and id put them as far out on each side of the bumper as possible

Posted
Is that chrome door molding stock? Looks good.

 

Yes.

 

 

But are those fender flares the stock ones, I would've thought it came with painted white ones.

 

 

 

The chrome trim is stock, but as far as the fender flares go, no they are not the stock ones. When i bought the truck it didnt have fender flares so i got a fair off of craigslist. The guy i bought them from had a gold truck and didnt like them so i snatched them up and i think they look good on my white truck. I have no idea why it didnt have stock fender flares its a true z71 i guess they original owner didnt want to pay for them or something.

Posted

Nice truck Dane! Looks great! You should tint your windows too! That thing is really clean for almost 12 years old! I wanted the monsters too but I agree way to popular now, I'll have to look into those wheels for my HD! Again nice truck!

  • 4 weeks later...

Archived

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

  • Latest Articles

  • Posts

    • 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? 
    • 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. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • 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.
    • 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...