Jump to content

Recommended Posts

Posted

Received the message "service tire monitor system" and when you check the current tire pressures, it shows blank. This truck now has about 24,500 miles on it and is a 2020 year model. My assumption is that this should be a simple warranty fix but since I purchased new tires at 288 miles ( I like the aggressive look of the BFG K02's) the dealership is reluctance to check it. I have to agree that if they, the dealership, deem the issue to be physical damage, not only would the warranty not cover it but I would then have to pay a diagnostic fee and/or labor for dismount/mounting of said tire. It is extremely frustrating how dealers always lie, cheat and deceive at every single opportunity they get to ultimately screw the customer over. Maybe I'm just being a drama queen but after purchasing a $75K truck, if something as trivial as a $15 dollar sensor (at cost, I bet they retail for over $100) I expect them to replace it NO QUESTIONS ASKED if it fails after 2 years. Yes its possible discount tire COULD have damaged it but if they did, would it have worked for 19 months before it went out????? (tires were purchased OCT 2020) Just another example how how bad dealership totally suck at the customer service portion of the auto industry. Long gone are the days of "quality built". Prolly will end up just buying a new senor on ebay and let discount tire install it ( they will install free of charge with certs) . Thanks for listening to my rant, 

20220515_200344.jpg

20220515_225724.jpg

Posted

My experience is that TPMS sensors usually last 8-10 years at which time the battery in them dies.  On my own vehicles I replace all the sensors when I need new tires and the truck is over 8 years old.  I see the dealer's point about not wanting to warranty a sensor that was damaged when the OEM tires were replaced, but the sensor did last quite a while after the tires were changed so I doubt is was damaged.  I think that sensor runs about $75 and if you figure #125/hr. labor it will be a $200 job customer pay. 

Posted

I have 3 replaced free by dealer within 2 yrs. They work for an hour ,then not for 1 hr, then back on ect…….

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