Jump to content

Recommended Posts

Posted

I took my truck to a dealer for an oil change. I got it back and noticed that the top corner of the headlamp area is caved in (see pic). There is about a 1/8” gap... So guess where you’re hip would be touching the vehicle if you were unscrewing the oil cap?? Ding, ding, ding, yes as a 6 foot person my hip would be touching that area of the headlight if I had to unscrew the oil cap. So what happened did he lay on it? This is so frustrating..not sure it’s worth complaining about. It flexes now if you push on it. It wasn’t like this before (I wash it every week so I would know).

 

My questions are...

1. Will water get in that crack and cause any problem?

 

2. Can I bend it back in place?

79DC3635-E591-43DB-A6BC-D2A83CC6D346.jpeg

Posted

Cant hurt to take it back and say WTF?

 

I ALWAYS go over the truck with the advisor when I drop it off ... followed by me inspecting it before I leave when its done.

Posted
3 hours ago, steve841 said:

Cant hurt to take it back and say WTF?

 

I ALWAYS go over the truck with the advisor when I drop it off ... followed by me inspecting it before I leave when its done.

Yea, I hear ya. I’m just afraid that may introduce more issues if they fix it. I went over the entire vehicle, but not with the service advisor unfortunately.

 

It looks like that piece is just a plastic trim piece around the headlight. It must be somewhat malleable.

  • Thanks 1
Posted
13 hours ago, JimmyT said:

Yea, I hear ya. I’m just afraid that may introduce more issues if they fix it. I went over the entire vehicle, but not with the service advisor unfortunately.

 

It looks like that piece is just a plastic trim piece around the headlight. It must be somewhat malleable.

Malleable.  Perfect word for all the body parts on these new trucks! All so they can fall apart at the slightest touch for 5 star crash ratings. 

Posted

I'm surprised the dealer isn't doing inspection on arrival. 

Advisors where I go inspect every one on their own.

 

Prevents them getting blamed for something that it arrived with, and gives then a chance to check tires/wipers and possibly upsell. 

 

I've never noticed them inspecting them on the way out. That's still a 'do it yourself' at that location.

 

 

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 2,189 Guests (See full list)

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