Jump to content

Recommended Posts

Posted

I've owned my 2019 Yukon for a year now and I've noticed pretty much straight away that the cargo area is entirely un-illuminated.  With the exception of the lights above the 3rd row seating, there is nothing beyond that, which is somewhat rare as most other even smaller SUVs and crossovers have "at least" sub-par cargo area illumination.  I also recognize that this issue would be even more prominent in a longer wheel base Yukon XL or Suburban due to having a larger cargo area behind the 3rd row.

 

I know there's plenty of things I can add, LED strip lights, LED fixtures, etc.  I'm also electrically savvy so tying them into the factory dome light illumination circuit would not be difficult.  However I'm interested to see what others have done, if they have decided to tackle the issue of having a less-than-ideally illuminated cargo area in their Tahoe/Suburban/Yukon/Escalade.  Thanks!

Posted (edited)

i have a '15 burb.   it has 3 lights behind 3rd row.  so hasnt been an issue

 

i recall someone adding a small LED strip at back

another user bought the 2 light setup from dealer & cut it into back plastic

another drilled & Added 3 or 4 eagle eye LEDs (super bright setup)

Edited by gat0r
Posted
5 hours ago, gat0r said:

i have a '15 burb.   it has 3 lights behind 3rd row.  so hasnt been an issue

 

i recall someone adding a small LED strip at back

another user bought the 2 light setup from dealer & cut it into back plastic

another drilled & Added 3 or 4 eagle eye LEDs (super bright setup)

Would you care to share a picture of those lights in your truck?  I wasn't aware that any of the full size SUVs were given any lights in the cargo area.

Posted

It seems that this factory cargo light was only available on 2015 models as per the other threads on TahoeYukonForum.com.  Strange that it was discontinued.

Would you happen to be able to upload a picture of your cargo light that has 3 lights in it?

From the looks of it, the 2 light fixtures have the molded "cutout" in the center for the possible 3rd light.

 

Strange.  The truck models are becoming more and more about light illumination but then in this instance, the newer models actually had a cargo light deleted.

Posted
6 hours ago, gat0r said:

3rd-row-lights_sm.jpg

Thanks - awesome!  It's fact that this 4th light fixture was only available on the 2015 model year.  I'm beginning to wonder if it was also only available on the extended length SUVs as well.  The standard length SUVs don't have a lot of flat roof behind the 3rd row light.  If I was going to add lights it would probably be on the plastic trim adjacent to the tailgate.

  • 2 years later...
Posted

I guess we don't drive our 2020 enough to notice that it's not bright enough in the back.  I'll get out to garage when I fly home and see.

  • 2 weeks later...

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