Jump to content

HID Headlight Bulbs / HID Projector Retrofit

MotoMedic
 Share

Recommended Posts

  • Replies 3.4k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

MotoMedic
MotoMedic

**The Sierra & Silverado HID topics have been merged and edited, in an attempt to create one comprehensive HID topic**   This topic will cover HID information, HID headlight bulb upgrades, HID f

MotoMedic
MotoMedic

-----HID FOG LIGHTS-----   Installing HID fog light bulbs in the 2014's has so far been a mixed bag. Some members have installed operated them for months without incident, while others have had thei

FastWS6TA
FastWS6TA

What is your name? I will look you up and reply. You wouldn't believe the amount of emails we get in a day. It is staggering and the best we can do is quickly sift through them looking for the easiest

Posted Images

sobe_zuki Enthusiast

sobe_zuki

Posted
Posted

 

The HD relay plus capcitor kit should solve that. Put the capacitor kit between the stock headlight bulb plug and the relay and make sure the capcitor kit has a good ground.

I do have the relay harness, I bought the Sierra spec kit. The capacitor is in-line before the harness. Like I said, it works perfect at night but not during the day with the lower voltage that the DRL provides. I'll re-check the ground for the capacitor.

440hsp Enthusiast

440hsp

Posted
Posted

I know for mine sobe the Drl's work when I put it in drive. I have an slt with a fxr retro I did.

 

Sent from my SAMSUNG-SM-N910A using Tapatalk

They also come on when I remote start the truck and it's just sitting there.

 

Sent from my SAMSUNG-SM-N910A using Tapatalk

440hsp Enthusiast

440hsp

Posted
Posted

 

The adjuster consists of a ball and socket joint mounted to a gearset that allowed you to adjust it.

 

Take the headlight out and you will find that the adjuster is removable with a quarter turn counter clockwise. You will see the arm with the ball on it. Extend it out fully by turning the adjuster and insert it back into the headlight, feeling it click back into the socket joint. Carefully adjust it in slightly to make room for you to reinstall the adjusted into the headlight housing. Adjust carefully or you will pop it out again, but no lasting damage should have been done

8103ff76e5cc16ac2a1dc0d05cfacce7.jpg

 

OK danger. Here's my problem. I don't know how but half of my teeth on the adjuster is wore smooth off. Now. I'm screwed. Tore the front of my truck apart and can't fix it. Damn

 

Sent from my SAMSUNG-SM-N910A using Tapatalk

oromero830 Enthusiast

oromero830

Posted
Posted

I do have the relay harness, I bought the Sierra spec kit. The capacitor is in-line before the harness. Like I said, it works perfect at night but not during the day with the lower voltage that the DRL provides. I'll re-check the ground for the capacitor.

 

Try flipping the connector from the capacitor link that connects to the OEM input adapter that used to plug into your stock bulb. I drew it out and it's attached. I thought it would be easier to show you what I mean.

post-144000-0-12051100-1439236174_thumb.jpg

post-144000-0-12051100-1439236174_thumb.jpg

post-144000-0-12051100-1439236174_thumb.jpg

post-144000-0-12051100-1439236174_thumb.jpg

Crf450r420 Enthusiast

Crf450r420

Posted
Posted

I just used some glue to hold the nuts and put all 4 bolts in to the brackets. Upgraded the size of the bolt and used all stainless. Also used larger stainless to hold the brackets to the housing, the same when I did it before the fast brackets in post 901.

 

Sent from my SM-N900V using Tapatalk

RobZ71LM7 Enthusiast

RobZ71LM7

Posted
Posted

I just used some glue to hold the nuts and put all 4 bolts in to the brackets. Upgraded the size of the bolt and used all stainless. Also used larger stainless to hold the brackets to the housing, the same when I did it before the fast brackets in post 901.

 

Sent from my SM-N900V using Tapatalk

 

Yup, I used stainless too.

RobZ71LM7 Enthusiast

RobZ71LM7

Posted
Posted

I do have the relay harness, I bought the Sierra spec kit. The capacitor is in-line before the harness. Like I said, it works perfect at night but not during the day with the lower voltage that the DRL provides. I'll re-check the ground for the capacitor.

 

 

Either your capacitor is bad, you have a bad ground, or the harness is backwards. I just tested mine and my DRL's work perfectly with the capacitor as it came. This should be what you have below. Refer to the second picture on swapping pins in the plug if that is indeed the problem.

 

http://www.theretrofitsource.com/components/harnesses/capacitor-relay-harness-link.html#.VckiTKgVhBc

sobe_zuki Enthusiast

sobe_zuki

Posted
Posted

Try flipping the connector from the capacitor link that connects to the OEM input adapter that used to plug into your stock bulb. I drew it out and it's attached. I thought it would be easier to show you what I mean.

This is all I had to do is flip the capacitor harness like you described. It works perfect now. Thanks everyone!

440hsp Enthusiast

440hsp

Posted
Posted (edited)

Ok guys. Got my fxr's adjusted the best I could out here on vacation in Colorado but I noticed one thing. I have the height of my cutoff maxed out and it's not high enough. I had a real issue getting everything stuffed in behind the cap and sealed up correctly. I think the new D2S igniters housings are too big because I had to modify the cap to get them to fit and it is really snug. Went through hell trying to get the igniter on the bulb to twist it on. Now it looks as though the igniter wire is rubbing it too. I just need to raise it up about a foot more to get it where I need it. Dang it. Any suggestions to get the height I'm looking for?

 

Sent from my SAMSUNG-SM-N910A using Tapatalk

Edited by 440hsp
clayc213 Enthusiast

clayc213

Posted
Posted

IMG 4051

 

Im really confused by the wire in the photo. Its coming from the headlight of a morimoto HID kit.

This is the driver's side headlight and there seems to be no problems with the HIDs functioning. Did I do something wrong ?

NitroDatsik Senior Enthusiast

NitroDatsik

Posted
Posted

 

Im really confused by the wire in the photo. Its coming from the headlight of a morimoto HID kit.

This is the driver's side headlight and there seems to be no problems with the HIDs functioning. Did I do something wrong ?

I don't have morimotos but looks like an end that plugs into a ballast or error cancellers

 

2014 Silverado 2WT CC Summit White 4.3L V6

DROPKICK Edition

IG: jorge_dropkick_rangel

Mike1220 Senior Enthusiast

Mike1220

Posted
Posted

 

Im really confused by the wire in the photo. Its coming from the headlight of a morimoto HID kit.

This is the driver's side headlight and there seems to be no problems with the HIDs functioning. Did I do something wrong ?

If everything is working right, don't question it [emoji1]

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
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      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
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      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.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

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