Jump to content

Recommended Posts

Posted

I just finished my install. I purchased the Morimoto Elite HID Silverado kit with 5500K bulbs from Fast Headlights.

 

It only took about 20 minutes to hook everything up for the initial test, then several hours routing wires and choosing where to mount items to make the install look clean.

 

I mounted the passenger side ballast and relay under the plastic cover behind the top of the grill and in front of the radiator. The drivers side ballast was mounted to the metal pillar next to the bulb cover. The install looks really clean, but it will be a real pita when/if I need to replace a component.

 

 

attachicon.gifIMG_3491.JPG

 

Any night time light pictures?

Posted

getting a new truck in a couple weeks and one of the first things I'm going to do is put hid headlights in it. I have hid extra bulbs in my current truck and they are ok but i haven't been outstandingly impressed with them so i am looking to branch out and try something different. I here a lot of buzz about the morimoto headlights and are just wondering if those are still the best ones out there or if anyone has any other recommendations? TIA!!

Posted

getting a new truck in a couple weeks and one of the first things I'm going to do is put hid headlights in it. I have hid extra bulbs in my current truck and they are ok but i haven't been outstandingly impressed with them so i am looking to branch out and try something different. I here a lot of buzz about the morimoto headlights and are just wondering if those are still the best ones out there or if anyone has any other recommendations? TIA!!

 

Can't say as compared to other HID brands, but I did install a set of Morimoto Elite 4300K on my 2014 Sierra over the weekend and have been very happy with the improvement over stock.

 

Has anyone who has done the Morimoto drop-in upgrade had to do some serious readjustment of their lights? After installing I re-aimed my headlights with a 2.5" drop @ approximately 25'. Even with that adjustment it seems like I am spotlighting the trees when I hit high beam and the cutoff is above the road. Truck is a Z71 with stock suspension and 32" tires.

Posted

ok all heres my question i just got my hid kit trying to put it in my 2015 gmc with the projector head light now my prob is when i take the dust cover off and pull the factory plug out and put the hid in there no way for the factory plug to get out threw the 1'' hole i have to drill on the dust cover the rubber grommet that came on the builb has 2 extra holes on it and also came with a 8'' extenchen plug I'm thinking if i just cut the 2 wires on the 8' plug and feed them threw the hold into the housing and thing use butt connectors to splice them back and then plug that into the cap and then into the relay harness has anyone had to do this before so i can put the dust cover back on i tried to upload the pic of what i have but it says its to big

Posted

You shouldn't be cutting anything to install HIDS. This is what my Silverado lights look like after the 1" hole through the dust cover.

 

image.jpg

 

image.jpg

 

 

Your factory plug should stay inside the headlight and your HID bulb goes inside and the wires come out like this.

Posted

That's what I thought but the gromet has 4 holes for wires and only 2 on it I think really they just forgot to put the other 2 wires on the gromet but I would have to cut the 8"" wire feed it threw and reconnect it I wish I could get the pics to load and I could show you better

Posted

getting a new truck in a couple weeks and one of the first things I'm going to do is put hid headlights in it. I have hid extra bulbs in my current truck and they are ok but i haven't been outstandingly impressed with them so i am looking to branch out and try something different. I here a lot of buzz about the morimoto headlights and are just wondering if those are still the best ones out there or if anyone has any other recommendations? TIA!!

If you have plug and play hids now and aren't impressed go with a full on retrofit such as the fxr

 

I first put in the 4300k morimoto elite kit and although it was an upgrade over stock, I did the retrofit a year later. Wished I had done it right off the bat.

 

I would recommend morimoto, have had their kits in my past few trucks and everything has held up good for the most part and any issues have been replaced hassle free

Posted

I just installed the Morimoto 5500k HID kit with 50w ballasts yesterday, and all I can say is WOW! I have tried two different types of LED kits and both were just awful. The Morimoto kit was quite a bit more difficult to install, but worth the effort. I took my time and routed all the wires and mounted the ballasts and igniters so you can't see anything except the two wires coming out of the rear of the driver side light. The quality of the kit is first rate, too. Much better than any OEM setup I've seen.

 

The light output is stunning, and there is a nice sharp cutoff even with the stock projectors. I'm sure the FXR projectors are even better, but this upgrade is still amazing. I may do the retrofit later, but I was limited on time this time around. The 5500 is pretty close to the LED DRL's, but the 4500K would probably a closer match. I wanted the color to match my LED fog lights, and the 5500K is perfect in that respect.

 

Wish I had done this when I bought the truck 2 years ago,,,

  • Like 1
Posted

I just installed the Morimoto 5500k HID kit with 50w ballasts yesterday, and all I can say is WOW! I have tried two different types of LED kits and both were just awful. The Morimoto kit was quite a bit more difficult to install, but worth the effort. I took my time and routed all the wires and mounted the ballasts and igniters so you can't see anything except the two wires coming out of the rear of the driver side light. The quality of the kit is first rate, too. Much better than any OEM setup I've seen.

 

The light output is stunning, and there is a nice sharp cutoff even with the stock projectors. I'm sure the FXR projectors are even better, but this upgrade is still amazing. I may do the retrofit later, but I was limited on time this time around. The 5500 is pretty close to the LED DRL's, but the 4500K would probably a closer match. I wanted the color to match my LED fog lights, and the 5500K is perfect in that respect.

 

Wish I had done this when I bought the truck 2 years ago,,,

 

 

Always good to hear. I am 'patiently' waiting for my FXR/Mori kit to come in....

Posted

Looking to go from stock bulbs to Factory HID. Just an upgrade. What all is involved and is anyone selling their removed stock assy's? 2014 LT Silvy.

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