Jump to content

Recommended Posts

Posted

I have searched but reviews on long term reliability don't seem to pop up much. I want to upgrade my lights on my 2015 Silverado 1500 LT. I would like to go to projectors for a better pattern and better light penetration for overall night driving. I know there are a lot of DIY kits out that can be bought, but cutting open my own headlights make me a little nervous if for some reason it does not work I would be out a vehicle. Any one have any suggestions for a full swap assembly or locations for cheap stock headlights that I wouldn't be out too much if I end up botching the retrofit?

 

Thanks in advance. 

Posted (edited)
1 hour ago, pjerzy said:

I have searched but reviews on long term reliability don't seem to pop up much. I want to upgrade my lights on my 2015 Silverado 1500 LT. I would like to go to projectors for a better pattern and better light penetration for overall night driving. I know there are a lot of DIY kits out that can be bought, but cutting open my own headlights make me a little nervous if for some reason it does not work I would be out a vehicle. Any one have any suggestions for a full swap assembly or locations for cheap stock headlights that I wouldn't be out too much if I end up botching the retrofit?

 

Thanks in advance. 

The only thing you can botch is cutting the housing and reglueing it back together.

 

Lets say after you cut the back of the housing off your dog comes around and takes those pieces and chews them up. Aka total destruction. Your bulb is in no way attached to those pieces. You could reinstall them on your truck with the entire back portion of the headlight missing.

 

My point is the only thing you can screw up on is a lack of properly sealing the fixture. In which case your headlights will still work until you can find a replacement.

 

If I had to do it over again, I’d buy a hot knife to cut the plastic housing. The dremel cutting left too rough of surface and it got plastic shavings in the housing. All you doing is cutting the back of the housing off and then glueing it back on. It’s pretty simple. It’s only purpose is to seal the headlight.

Edited by truckguy82
Posted
6 minutes ago, truckguy82 said:

The only thing you can botch is cutting the housing and reglueing it back together.

 

Lets say after you cut the back of the housing off your dog comes around and takes those pieces and chews them up. Aka total destruction. Your bulb is in no way attached to those pieces. You could reinstall them on your truck with the entire back portion of the headlight missing.

 

My point is the only thing you can screw up on is a lack of properly sealing the fixture. In which case your headlights will still work until you can find a replacement.

 

If I had to do it over again, I’d buy a hot knife to cut the plastic housing. The dremel cutting left too rough of surface and it got plastic shavings in the housing. All you doing is cutting the back of the housing off and then glueing it back on. It’s pretty simple. It’s only purpose is to seal the headlight.

No need for a hot knife for these k2 trucks. They’re permaseal, but not terrible. Can be baked in the oven and opened up. Just use butyl glue to reseal and you’re done. 

Posted
Just now, cbrsilv15 said:

No need for a hot knife for these k2 trucks. They’re permaseal, but not terrible. Can be baked in the oven and opened up. Just use butyl glue to reseal and you’re done. 

I did the cutting method, never tried it that way so can’t comment.

Posted

For the Sierra guys that have opened up your headlights did you leave the LED control module attached to the lights when you baked them? 

Posted

I made an account just to post this so if I didn't follow some rules sorry. I also didn't read through the 200+ pages on this post either since I can't find anything about this online.

 

I got some hids and ballasts from a friend for free and installed them last night. I ordered a relay harness with capacitors and installed that as well. He says everything was working correctly when he took it out of his vehicle. Although he didn't have to use a harness.

 

Heres a YouTube video of the issue

 

My issue is that anytime the truck is in park, running or off, it turns the headlights on like I just unlocked the truck or turned the headlight switch. It flashes twice then will sometimes go off sometimes won't. It does it at random times to sometimes its 5 seconds between when it flashes sometimes its a 3 minutes +. If I unplug the relays in the harness it still does it, if I unbolt the ground it still does it. I've checked ever connection and am gonna go double check in a minute.

 

Any ideas or suggestions would be greatly appreciated thanks.

Posted
For the Sierra guys that have opened up your headlights did you leave the LED control module attached to the lights when you baked them? 
Yes

Sent from my SM-N950U using Tapatalk

  • 4 weeks later...
Posted

i have a 2015 gmc sierra sle carbon 22 edition, ended up buying the 2015 GMC HD 2500 LED lights with the DRL in them. opened them up and swapped projectors for the rx350's with the sti-r clear lenses that were optically tuned and paired them with the xb35 morimoto ballasts and d2s 35w morimoto bulbs, diode dynamic switchback DRL. had nothing but problems with them, including the 7443 switchback bulbs from morimoto which i've replaced 3 times in less than a year. ended up re-opening and ditching all things morimoto for the 4th gen 45w hylux ballasts, the new osram 66240 cbb 7000K 35w bulbs, and the 7443 gtr lighting carbide switchback turn signals. shouldn't have let myself be convinced originally to go with the morimoto shit as it was against my better judgement but i listened to a seasoned retrofitter and wasted ton of money and time on subpar equipment. light output is far superior, i enjoy the color temp more its not really 7000k its more like 5500K as i know the higher watt ballasts step down the color temp some as well. much better performing component combination to compliment the rx350 and sti-r lens. 

  • 5 weeks later...
Posted
On 5/3/2019 at 10:49 PM, mr4wdLTZ said:

Here are some night shots.

 

mini D2S 5.0 kit with 35 watt hylux ballasts. 5500K D2S bulbs.

 

The D2S exceeded my expectations once I was able to line them up and take a drive tonight. The 5.0 is on or with my FXRs in my old trucks. With a fraction of the modification necessary to make it work.

 

the splitter that allows the bi-xenon high beam function in conjunction with the factory halogen high beams really enhances the brights. I did add some syllabi’s silverstar ultra 9005s while I had it all apart. Better than stock but not the same color temperature. That’s ok. The output is outstanding. 

 

i highly recommend @FastWS6TA kits.

07557AB3-5538-42F8-B7DF-5E74AA2F4CD6.jpeg

2579537C-D7C5-4B5F-98AC-6A470E0D3D1D.jpeg

Hey man, I see you mention that you use D2S Bulbs with this setup.  Which D2S Bulbs are you using and with what connectors?  I'm running D2H bulbs as most use with this retrofit because I was worried D2S Bulbs with connectors would not fit under the stock headlight caps.

  • 3 weeks later...
Posted
On 6/11/2019 at 9:24 PM, Keith Rox said:

i have a 2015 gmc sierra sle carbon 22 edition, ended up buying the 2015 GMC HD 2500 LED lights with the DRL in them. opened them up and swapped projectors for the rx350's with the sti-r clear lenses that were optically tuned and paired them with the xb35 morimoto ballasts and d2s 35w morimoto bulbs, diode dynamic switchback DRL. had nothing but problems with them, including the 7443 switchback bulbs from morimoto which i've replaced 3 times in less than a year. ended up re-opening and ditching all things morimoto for the 4th gen 45w hylux ballasts, the new osram 66240 cbb 7000K 35w bulbs, and the 7443 gtr lighting carbide switchback turn signals. shouldn't have let myself be convinced originally to go with the morimoto shit as it was against my better judgement but i listened to a seasoned retrofitter and wasted ton of money and time on subpar equipment. light output is far superior, i enjoy the color temp more its not really 7000k its more like 5500K as i know the higher watt ballasts step down the color temp some as well. much better performing component combination to compliment the rx350 and sti-r lens. 

Hylux ballast is the key. Morimoto bulbs are fine

Posted
7 hours ago, truckguy82 said:

Hylux ballast is the key. Morimoto bulbs are fine

morimoto ballasts are garbage, and my experience with the led bulbs they make for all things other than headlights do not seem to last long and suffer heat degradation with a much higher failure rate than every other major brand i’ve used. i’ve outfitted no less than 10 of my family members cars with all LED bulbs for interior and accent lighting and i’ve had to replace morimoto on numerous occasions. i’ve not had a single failure from any of the other brands, not once in 5 years. their headlight bulbs might be a different story as my experience with them is limited to this one experience and i didn’t try them with the hylux bulbs but they definitely have a subpar lux output comparatively to the top osram and philips bulbs. they are a budget bulb though so i think that’s kind of the significant take away is you can afford to replace them 2-3x’s as often if cost is your primary concern.

Posted
On 4/24/2019 at 11:22 AM, FastWS6TA said:

gmforum_10%

Use that code at checkout.

Sent from my SM-N950U using Tapatalk
 

Is there a new code? Order page says this one is invalid

Posted

So I have the 35W system........issue that just stated a month ago is as follows:

 

drivers side would work sometimes ......then go out.......now its out completely:

I tested the bulb, wiring, adaptor and I am at a loss.......I am guessing it is the ignitor or the ballast.....

 

Thoughts .... 

 

Posted

Probably ballast.  My passenger side did the same thing.  Was the ballast.  Replaced it and never had the issue again.

  • 3 weeks later...
Posted (edited)

Such a headache. How come factory headlights last a life time but aftermarket, no matter cost, crap out, the first year?? 

 

Edited by Vulcan762

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

    • Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...