Jump to content

Endurante221b's Silverado 1500 (K2XX): Modifications to consid


Endurante221b

Recommended Posts

Posted

Just wanted to get some ideas as to what you might have found to be useful or cool to install on your truck. As per the title, I am looking forward to ideas that would fit a K2XX platform Silverado 1500. Mine is a 2016 LT crew cab standard bed. Things that I have been thinking about have been a spray on bed liner from LINE-X and an aftermarket exhaust that would be legal in CA. Hope to hear about quality gems out there and even the sad stories about bad quality parts so that we may all learn. Diagrams and pictures and first hand examples are much appreciated! If you post about exhausts, please tell me for what vehicle length its for please (short bed, standard bed, long bed). Thank you for your participation!



Posted

So I have to apologize. I didn't realize up until just recently that there have been plenty more than just 3 generations of the Chevrolet Silverado. Previously, my thread title here was:

"Endurante221b's Silverado 1500 (3rd Gen.): Modifications to consider."

Please excuse the mistake and feel free to provide additional information to clarify my understanding. Thank you!

Posted

2016 denali CC Short bed 6.2 8spd.

Peragon color matched bed cover.

Had factory spray in liner but I bought a DeeZee 1/2 thick rubber mat for the bed anyway.

Hypertech 2.0 part 2000 hand held tuner.

GM Borla catback dual exhaust

Husky underseat storage for back seat.

Husky exact fit floor liners.

post-127028-0-36240500-1474850418_thumb.jpg
post-127028-0-28094300-1476485477_thumb.jpg
Exhaust / bed cover and tuner seems to be a combination that produces good gas mileage LOL

 

Currently interested in a CAI there are some cool ones out there but wanting a clear topped one like the Cold Air Induction setup in the near chrome finish, looks pretty cool to me........... PRODUCT CODE: 512-0103

Availability: In stock

2014 - 2016 SILVERADO AND SIERRA 1500 TRUCKS WITH 6.2L V8 COLD AIR INTAKE (NEAR-CHROME FINISH)
Posted

That DeeZee rubber mat sounds like a great idea!

Have you experienced any drone with the Borla catback dual exhaust? If so, at what rpms?

SoCal-SD has a cool CAI pic too!

Thanks for the ideas!

Posted

 

2016 denali CC Short bed 6.2 8spd.

Peragon color matched bed cover.

Had factory spray in liner but I bought a DeeZee 1/2 thick rubber mat for the bed anyway.

Hypertech 2.0 part 2000 hand held tuner.

GM Borla catback dual exhaust

Husky underseat storage for back seat.

Husky exact fit floor liners.

Exhaust / bed cover and tuner seems to be a combination that produces good gas mileage LOL

 

Currently interested in a CAI there are some cool ones out there but wanting a clear topped one like the Cold Air Induction setup in the near chrome finish, looks pretty cool to me........... PRODUCT CODE: 512-0103

Availability: In stock

2014 - 2016 SILVERADO AND SIERRA 1500 TRUCKS WITH 6.2L V8 COLD AIR INTAKE (NEAR-CHROME FINISH)

 

 

Did you notice an increase in mpg before the tune? How much did you pay for the tune?

Archived

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

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...