Jump to content

Recommended Posts

Posted

Hello everyone, i am new to the fourms and i am sure this has been discussed before in other threads , My question is if i bought the the denali headlights will they work on my regular sle model?
I swaped my regular bulbs with LEd ones and i hate how they look and they are worst then the regular ones I can’t see shit anight.

Thanks in advance :)

 

16 yukon xl sle  

  • 11 months later...
Posted

get a pair of morimoto hid's from the retro fit source! put them in my 15' duramax and cant wait to upgrade the yukon!

Posted
Hello everyone, i am new to the fourms and i am sure this has been discussed before in other threads , My question is if i bought the the denali headlights will they work on my regular sle model?
I swaped my regular bulbs with LEd ones and i hate how they look and they are worst then the regular ones I can’t see shit at night.

Thanks in advance clear.png
 
16 yukon xl sle  


Do you mean the entire HID headlight assembly? They will physically fit, but won’t just plug and play. The issue is the PWM (pulse width modulation) signal on the low beam circuit. It makes the HID ballasts rapidly turn on and off.

I’ve installed them on my SLT and love them.

There are two ways to go about it:

1. Have your BCM programmed and do some wiring (move circuits at the BCM, UEC) along with adding a circuit or two in the forward lamp harness.

2. Use a custom relay harness like I did.

I should be able to make one for you. PM me. It’s been a while since I installed mine and I would need to make sure the parts can still be sourced.


Sent from my iPad using Tapatalk
  • Like 1
  • 1 month later...
Posted
On 12/12/2018 at 9:36 PM, cmatt said:

 


Do you mean the entire HID headlight assembly? They will physically fit, but won’t just plug and play. The issue is the PWM (pulse width modulation) signal on the low beam circuit. It makes the HID ballasts rapidly turn on and off.

I’ve installed them on my SLT and love them.

There are two ways to go about it:

1. Have your BCM programmed and do some wiring (move circuits at the BCM, UEC) along with adding a circuit or two in the forward lamp harness.

2. Use a custom relay harness like I did.

I should be able to make one for you. PM me. It’s been a while since I installed mine and I would need to make sure the parts can still be sourced.


Sent from my iPad using Tapatalk

 

I’ve been thinking about doing this. I know a lot of guys use a retro fit kit, but I really want a plug and play projector for either LEDs or HIDs. Sounds like the Denali projector housing should fit right in to my SLT.. 

Posted
I’ve been thinking about doing this. I know a lot of guys use a retro fit kit, but I really want a plug and play projector for either LEDs or HIDs. Sounds like the Denali projector housing should fit right in to my SLT.. 


Yes, the headlight assemblies will swap right in. That’s exactly what I did on my SLT. A relay harness is needed so the factory HIDs will function properly.


Sent from my iPad using Tapatalk
  • 2 years 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
  • 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, 1,769 Guests (See full list)

  • Latest Articles

  • Posts

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...