Jump to content

HID Headlight Bulbs / HID Projector Retrofit

MotoMedic
 Share

Recommended Posts

Fireguy63 Enthusiast

Fireguy63

Posted
Posted
Thanks, I'll have to check that tonight. I did disconnect the MAF sensor when removing the air box for install, and then turned ignition to run when testing the lights with the MAF still unhooked.

 

I got a few emails from OnStar saying that the lights weren't functioning (when I was testing and metering them) and another stating engine/transmission issue.

[/quote

 

Disconnecting the air sensor from the tube is what does it from what my mechanic friend told me that's what caused mine had nothing to do with the lights that's y it reset after a day or 2 it sensed everything was good

  • 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

iwannaseeatnight Enthusiast

iwannaseeatnight

Posted
Posted

Went out at lunch and disconnected the battery for about 30min then reconnected. Light's off and remote start works again. Hope to be in the clear.

 

Thanks guys!

  • Like 1
SouthPawCO Enthusiast

SouthPawCO

Posted
Posted

So I installed my FX-Rs and Morimoto Elite HD kit (35W, 5500K) and XB fogs this weekend. On initial wiring, I lost track of a couple connectors from the relay (in a rush) and hooked the Cap directly to the ballast on the passenger side. When I turned them on, no light on the driver's side. After metering and finding no power to the driver's side ballast, I went through checking connections and discovered my mistake. I changed it to Cap>Relay>Ballasts and bingo, both lights on.

 

I am kind of having a similar issue with my kit. I will double check to see how I have it wired but I have the cap right before the ballast and the 12v works fine but the DRL mode flickers and cuts in and out. I have to turn them off during the day and the relays are buzzing. Any idea on what that might be? I will take pictures of how I have it wired tonight.

iwannaseeatnight Enthusiast

iwannaseeatnight

Posted
Posted

 

I am kind of having a similar issue with my kit. I will double check to see how I have it wired but I have the cap right before the ballast and the 12v works fine but the DRL mode flickers and cuts in and out. I have to turn them off during the day and the relays are buzzing. Any idea on what that might be? I will take pictures of how I have it wired tonight.

I had messed up on mine the first time by going OEM Input> Cap> Ballast, which eliminated my driver's side light.

 

Not sure what kit/harness you are using, but for the Morimoto Elite HD Harness it should be OEM Input> Cap> Relays> Ballasts.

 

I don't have the DRL thru HIDs, so I don't know anything about them.

j3st3r Enthusiast

j3st3r

Posted
Posted (edited)

 

I am kind of having a similar issue with my kit. I will double check to see how I have it wired but I have the cap right before the ballast and the 12v works fine but the DRL mode flickers and cuts in and out. I have to turn them off during the day and the relays are buzzing. Any idea on what that might be? I will take pictures of how I have it wired tonight.

As I wannaseeatnight said. The capacitor should be before the relay. Not the ballast. Edited by j3st3r
SouthPawCO Enthusiast

SouthPawCO

Posted
Posted (edited)

I had messed up on mine the first time by going OEM Input> Cap> Ballast, which eliminated my driver's side light.

 

Not sure what kit/harness you are using, but for the Morimoto Elite HD Harness it should be OEM Input> Cap> Relays> Ballasts.

 

I don't have the DRL thru HIDs, so I don't know anything about them.

 

 

I will try that tonight after work. That does make sense to have it between the relay and ballast since the ballast is getting power from the relays. Hopefully it fixes it. I have the morimoto kit on my Silverado. I believe I have it between the OEM input and ballast but I will double check tonight or tomorrow.

Edited by SouthPawCO
j3st3r Enthusiast

j3st3r

Posted
Posted

 

I will try that tonight after work. That does make sense to have it between the relay and ballast since the ballast is getting power from the relays. Hopefully it fixes it. I have the morimoto kit on my Silverado. I believe I have it between the OEM input and ballast but I will double check tonight or tomorrow.

You should have the capacitor hooked directly to the oem plug, then the relay hooks to the capacitor, then the ballast to the relay, and then ballast to hid. The reason your relay is buzzing is because the truck uses pwm (I believe that's what it is called) to run the drl at a lower voltage so the buzzing you're hearing is the relay being turned off and on in rapid succession. That's why they are flickering. The capacitor supplies a steady voltage to the relay to elimate that.

SouthPawCO Enthusiast

SouthPawCO

Posted
Posted

You should have the capacitor hooked directly to the oem plug, then the relay hooks to the capacitor, then the ballast to the relay, and then ballast to hid. The reason your relay is buzzing is because the truck uses pwm (I believe that's what it is called) to run the drl at a lower voltage so the buzzing you're hearing is the relay being turned off and on in rapid succession. That's why they are flickering. The capacitor supplies a steady voltage to the relay to elimate that.

 

If I have it plugged that way, where do you ground it? Are you saying it has to sit inside the headlight housing?

j3st3r Enthusiast

j3st3r

Posted
Posted

 

If I have it plugged that way, where do you ground it? Are you saying it has to sit inside the headlight housing?

The capacitor doesn't have to. Mine doesn't. My relay is grounded to the cross bar that is above the air filter box.

SouthPawCO Enthusiast

SouthPawCO

Posted
Posted (edited)

The capacitor doesn't have to. Mine doesn't. My relay is grounded to the cross bar that is above the air filter box.

 

I have the morimoto kit. I thought the OEM plug went to the cap but the plugs do not match. Plus the cap has a separate ground wire coming off of it.

 

https://www.theretrofitsource.com/capacitor-link.html

Edited by SouthPawCO
j3st3r Enthusiast

j3st3r

Posted
Posted

 

I have the morimoto kit. I thought the OEM plug went to the cap but the plugs do not match. Plus the cap has a separate ground wire coming off of it.

 

https://www.theretrofitsource.com/capacitor-link.html

Not sure why the plugs do not match. They should since TRS builds that kit specifically for the Silverado. You may want to give them a call. As far as grounding it, you should still be able to ground it to that cross member. Just make sure you get the paint off the surfaces so it makes a clean ground. I went the cheap route and bought opt 7 HIDs. My capacitor doesn't have a ground wire.

SouthPawCO Enthusiast

SouthPawCO

Posted
Posted

Not sure why the plugs do not match. They should since TRS builds that kit specifically for the Silverado. You may want to give them a call. As far as grounding it, you should still be able to ground it to that cross member. Just make sure you get the paint off the surfaces so it makes a clean ground. I went the cheap route and bought opt 7 HIDs. My capacitor doesn't have a ground wire.

 

Well the kit fastheadlights sends is a mopar kit. I will try what wantosee has done and hopefully that takes care of my problem.

Fireguy63 Enthusiast

Fireguy63

Posted
Posted

Depending on the kit the plug will need to be flip the truck uses reverse power so if it's positive on the ballets gonto nagitive on truck only kit I have found that you don't have to do this is with the DDM kit I have with the canbuss ballets

j3st3r Enthusiast

j3st3r

Posted
Posted

Depending on the kit the plug will need to be flip the truck uses reverse power so if it's positive on the ballets gonto nagitive on truck only kit I have found that you don't have to do this is with the DDM kit I have with the canbuss ballets

That is correct, but he said the plug didn't fit. Not that it wouldn't power them.

j3st3r Enthusiast

j3st3r

Posted
Posted (edited)

 

Well the kit fastheadlights sends is a mopar kit. I will try what wantosee has done and hopefully that takes care of my problem.

The mopar relay is what TRS uses as well. It works for both mopar and Silverado and I assume Sierra. I wanttoseeatnight has a Sierra I assume since he said his hid isn't used for the drl. Edited by j3st3r

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