Jump to content

New used truck issue


Recommended Posts

Posted

Gotta vent a little. After searching for a 15 suburban with the options for my wife I found 1 in Connecticut for a gd price. 2 hrs away, dealer very helpfull over phone and made the process of buying easy. Start to drive the car home and service park assist and side assist came on. Really truck has 16000 miles. Get home notice that the radio bezel is cracked. Bit the onstart button to do free trial and says cant connect. Where on a roll here. Go to show my wife how to use the radio and hit has navigation by telematics.

 

So now contacted the dealer to see what and if anything they are gonna do for me and now have to bring in the truck the 30th to get services. Fml. Other than that 24 mpg and drives nice. It was a fleet vehicle which explains the telematics, so now gonna contact mvi to upgrade the radio or can the dealer do it?

 

Sent from my SM-G900P using Tapatalk

Posted

Fleet vehicle = You nightmare has just started. If it was a GM vehicle, it was likely a buy back that was turned in before the official buy back occurred to keep its record clean. The broken dash often is a sign of unrepaired collision damage. If it was a rent car, remember the golden rule. What is the difference between a rent car and a Jeep? There are some places a Jeep can't go so you rent a car for the off road adventure instead. Sure hope the dealer has a return policy in case this thing turns worse.

Posted

CAr still has remainder on warranty. Goin in next week. The dash is fine, its the radio bezel that has a crack in it. Other than that drives nice, but well see

 

Sent from my SM-G900P using Tapatalk

  • 2 weeks later...

Archived

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

  • Latest Articles

  • Posts

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

  • Popular Contributors

×
×
  • Create New...