Jump to content

Recommended Posts

Posted

capacitor to eliminate flicker and relay to take load of HID system instead of over loading stock headlight wiring.

  • Like 1
Posted

Ok, so both are recommended for each kit then, correct? Headlights as well as fog lights?

 

 

Sent from my iPhone using Tapatalk

Posted

Ok, so both are recommended for each kit then, correct? Headlights as well as fog lights?

Sent from my iPhone using Tapatalk

Yes you could go with. Both I don't know much about opt7 my canbus system from ddm is a 35 watt system and it has everything built into the ballets and I didn't need the relay harness on my 15 Sierra it doesn't hert to have it

Posted

Yes you could go with. Both I don't know much about opt7 my canbus system from ddm is a 35 watt system and it has everything built into the ballets and I didn't need the relay harness on my 15 Sierra it doesn't hert to have it

I have tried putco led headlights and opt 7, no problems with installation, but the get dimmer over time (as many led's seem to do), additionally, visibility in rain was awful. I am now on morimoto XB's (4500k), a vast improvement.

  • Like 1
Posted (edited)

Has anyone swapped out the new 2016 Silverado HID's with TRS HID's?

I just completed an adapter kit to do just this. Email me at [email protected] and you can try it out.

 

b0f1534847d9961bfb0ad48bdd7286c1.jpg

 

Sent from my SM-N920V using Tapatalk

Edited by FastWS6TA
Posted

So back in August I installed FX-R's and Mori HIDs. Instead of baking the lens off I cut the housing open per FastHeadlight's instructions. When finished I used 4" wide roofing repair tape (the aluminum backed mastic tape) to wrap around the housing and then even used a torch to heat the tape to the point that the mastic was almost starting to melt and really pushed it down all around to get a good seal. I then drilled holes in the dust caps and installed the TRS supplied grommets. The issue I've noticed recently is that whenever it has been raining or early mornings that the windows are fogged (so high humidity conditions), the inside of the headlight lenses are fogged. It goes away a few days after the rain has ended. I feel good about the seal around the housing, but could that much moisture really be coming in around the grommet in the dust cap? Has anyone else noticed this after a HID retro? There's no water droplets, just a fine fog that the heat of the light burns off in the center. I would think having any moisture in there would be detrimental to the life of the bulbs. Something to worry about?

Posted (edited)

So despite having an led's powered by a seperate relay harness kit I broke down and installed the Morimoto Elite hid kit today, 35w ballast and 5500k bulbs, have to admit they are what everyone in the forum claims...needless to say I am suitably impressed!

 

Further to that I like the five year warranty too.

Edited by Comscan
  • Like 2
Posted (edited)

If you want brighter light go with a 50Watt ballast instead of the 35Watt. The bulb rating affects the color of the light more than the brightness. The Retrofit Source sells Morimoto kits online. I just installed one and it works great. Get on their website chat line and they can point you in the right direction. Ask the guy on the chat line for a discount code and you get 10% off.

Edited by vacuman
Posted

Get some.of these and put them in the headlights. Even a little humidity inside the lights can create fogging. A drop of water turns into a lot of fog when it evaporates. These packs will absorb any humidity in the lights.

 

https://www.theretrofitsource.com/silica-gel-moisture-packs-48728.html

 

Sent from my SM-N920V using Tapatalk

Got them on order. Thanks!

Posted (edited)

I installed a Morimoto 35watt 5500K HID kit from The Retrofit Source a couple of days ago. I just got back from a 200 mile freeway trip from Vegas to Ca. 3 lane interstate through the boondocks.

 

These lights are freaking amazing! Excellent clear white light across 3 lanes and 15ft to each side and at least 150ft ahead all without annoying other drivers. The whole trip on low beam. No need for HB at all. I did this same trip a month ago with the stock flashlights and was convinced I had to do something.

 

Best money I ever spent on a vehicle.

Edited by vacuman
Posted

Well, add me to the list. I just installed the Morimoto HID 5500k kit in my Sierra. I also installed the Morimoto LED fog light replacement kit. [emoji15] WOW.

 

The fit and finish was definitely as professional as others have described. The color and beam pattern is fantastic.

14fc96350bc995812d9589c347def4ef.jpg HIGH BEAMS AND FOGS.

 

a9a32ffc2905d6690a7ba9ac43f9d472.jpg LOW BEAMS ONLY

 

eeec98b8d625a25b5fef82de13c4ef3e.jpg FOG LIGHTS ONLY

 

1f0e1d75699c60e247376a50f219bca0.jpg LOW BEAMS AND FOGS FACING OUT FROM MY GARAGE.

 

My only question is on the last photo, notice the two "high spots" of light. Any input on why that is occurring?

 

 

 

Sent from my iPhone using Tapatalk

Posted

The light pattern looks similar to the one I just installed. I don't think it's an installation problem. The bulbs can only be plugged into the harness one way and inserted and twisted into the headlight one way. I think it may be a reflection off some of the chrome trim around the grill. Beats the hell out of the stock ones though.

  • Like 1

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

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