Jump to content

Recommended Posts

Posted

Hi folks - getting close to getting a ntm truck.  Currently pretty interested in a 2018 Sierra 1500 SLE (with i think kodiak edition).

 

Truck has 52000kms on it. Red in color, black wheels, remote start, heated seats blah blah blah

 

Some earlier questions I have for you guys if you can:

 

1. Truck looks levelled - other than asking dealer how can I tell it is has been levelled? 

2. Any issues you would warn me out or to look at?  Yes I know how to use forum but threads are all over the place - i think generally its a pretty decent drivetrain right?

3. In the grille there is this row of small orange dots - i cannot tell if they are a factory something or what the hell they are - any thoughts?

4. Are those stock wheels do you think?

 

Link here:  https://www.herrongm.com/VehicleDetails/used-2018-GMC-Sierra_1500-SLE-New_Glasgow-NS/4743513013

 

I am sure I will have more questions over the coming days and appreciate everyones replies.

 

Thanks

Yzinger

 

Posted

Wheels appear to be oem maybe dealer swapped, as in didn't come on the truck, but upgraded from the dealer. The dots look like some sort of aftermarket running lights. The truck is definitely leveled, maybe too much. Main issues with the drive train are slight vibrations and potential lifter failure. I had one go out on my 15 at 67k, thankfully under warranty.

Sent from my SM-G998U using Tapatalk

Posted

Leveled, aftermarket lights. Trucks are good, just remember more people come online to complain then anything else so don't take it all to heart. Take care of the truck and it will take care of you.

Posted (edited)

yeah i do know to take anything on internet with a grain of salt.  Just making sure no tranny or motor etc ongoing issues.

 

Dealer told me 20inch wheels.  Maybe those orange lights are just cosmetic type for looks - me no likey so would likely remove them.

 

I also really like a spray in box liner and the remote start.

 

Oh one other thing i can recall - notice the black in middle of hood, it seems it is almost a sticker for lack of a better word. Maybe some sort of paint protection but why only there?

 

Thanks for your replies fellas.

Edited by yzinger
Posted (edited)

Wheels are factory but off of the wrong generation of truck but still fit.  Those are from a new T1 2019-2021 Sierra Elevation trim truck.  That truck was factory built with 17" aluminum wheels with LT265/70R17 C load tires, Bridgestone Dueler AT RHS.

 

Looks like PO put exhaust on it as well as the hood deflector and window visors.  Lights in the grille too from the PO as that's not a factory thing.  Same for the hood graphic and tonneau.

 

Clean history in GM land.  Just a starter motor under warranty (not uncommon).   

 

Has 3.08 gearing so if you are towing keep that in mind as that truck will be rated for 6,100lbs towing.  

 

 

Edited by newdude
Posted

thanks alot - dealer did tell after i posted that they are off another truck that the customer didnt want.

 

I just hope it wasnt a previously 6inch lift truck ?

 

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
  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
    • Just don't turn the steering wheel as much?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...