Jump to content

Recommended Posts

Posted

Installed my 50W Morimoto kit tonight and it looks great. But now I have awful reception for some of the weaker FM stations in the area. Come in clearly when the HIDs are off but just static with them on.

 

Any suggestions? Maybe I need to route the power lead for the wiring harness differently?

 

 

Sent from my iPhone using Tapatalk

Although the reception sucks it doesn't change with HID lights off, on, or on DRL. I would check your ground. Just run a wire from the battery to you grounds as a quick test.
Posted

So I sanded the grounds and checked them with a ground wire with out an improvement. Still lose some of the weaker, non-HD FM stations with the HIDs on.

 

Also moved the power wire in case that was the cause.

 

Any ideas?

 

 

Sent from my iPhone using Tapatalk

Posted

So I sanded the grounds and checked them with a ground wire with out an improvement. Still lose some of the weaker, non-HD FM stations with the HIDs on.

 

Also moved the power wire in case that was the cause.

 

Any ideas?

 

 

Sent from my iPhone using Tapatalk

That was all I could think of, I have the same kit. Maybe someone more experienced has had this issue.
Posted

I tried to install my HID kit using a Relay and DRL module and faiked. Couldn't get them to come on properly. I know both bulbs work. Any suggestions ?

Posted (edited)

Somewhere you have a reversed polarity.


I tried to install my HID kit using a Relay and DRL module and faiked. Couldn't get them to come on properly. I know both bulbs work. Any suggestions ?

 

Sorry, I should have quoted you so you got an email. check polarity

Edited by spurshot
  • Like 1
Posted

So I know it's a bit off topic, but for those who had trouble with HID'S in the fogs, did you end up going with an LED bulb? I want the bulb to match, and hopefully also be used as an actual fog lamp. I'm looking at the $60 set from VLED and also a cheaper bulb with 5 chip on board leds from DDM

 

Sent while in 'Murica...

Posted (edited)

So I know it's a bit off topic, but for those who had trouble with HID'S in the fogs, did you end up going with an LED bulb? I want the bulb to match, and hopefully also be used as an actual fog lamp. I'm looking at the $60 set from VLED and also a cheaper bulb with 5 chip on board leds from DDM

 

Sent while in 'Murica...

I personally changed to off road pods so I could have more light if needed. But if I would've kept my stock fog lights (by this I just mean the housings) then I would've put in a real high powered bulb. Like one from Oracle or VLEDs. It would've costed around $100-$200 but then again, switching to off road pods costed me around $350-$400 when it was all said and done.

 

I would try these if you want to keep the stock fog light housings. They should give off an actually useful amount of light!

 

http://www.vleds.com/shop-bulb-numbers/lmz-ho-17.html

Edited by Mike1220
Posted (edited)

So I know it's a bit off topic, but for those who had trouble with HID'S in the fogs, did you end up going with an LED bulb? I want the bulb to match, and hopefully also be used as an actual fog lamp. I'm looking at the $60 set from VLED and also a cheaper bulb with 5 chip on board leds from DDM

 

Sent while in 'Murica...

 

Wait for the Rigid Dually DOT/SAE approved fog light http://www.rigidindustries.com/led-lighting/50481

Capture_zpsb7120cb0.jpg

 

 

... Or think about retrofitting these. The factory fogs with high output bulbs won't come close to the performance of these, in terms of useful, controlled light for actual foggy conditions, that won't blind oncoming traffic or you because of light scatter reflecting off the fog and back at you. Notice these have a sharp top cutoff and foreground limiting beam (prevents lighting the road directly in front of the vehicle, which reflects back at the driver), resulting in a narrow horizontal strip of light

 

morimoto_xb_led_type_s_fog_lights_1_.jpg

 

DSC_2692Medium_zps39672e8c.jpg

 

DSC_2693Medium_zps9a4d1bc4.jpg

Edited by spurshot
Posted

 

Wait for the Rigid Dually DOT/SAE approved fog light http://www.rigidindustries.com/led-lighting/50481

Capture_zpsb7120cb0.jpg

 

 

... Or think about retrofitting these. The factory fogs with high output bulbs won't come close to the performance of these, in terms of useful, controlled light that won't blind oncoming traffic.

 

morimoto_xb_led_type_s_fog_lights_1_.jpg

 

DSC_2692Medium_zps39672e8c.jpg

 

DSC_2693Medium_zps9a4d1bc4.jpg

I would do the retrofit if I had a sierra with round housings. I have the rectangular silverado housings so would need something similar in size to retrofit

 

Sent while in 'Murica...

Posted

If you check out the "LED Fog lights and Bulbs" thread, you should find some Silverado setups with 2 of the D series lights in each of the fog light positions.

  • 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

    • I hope to high heaven this is wrong. My Chevy farm trucks frame is lasting way longer than a newer Nissan Titan XD I got for a steal, and it only pulls trailers. A decade younger and it's frame is already way rustier than the waxed Chevy I drive across longs and ditches. Also, hasn't Ford been having tones of troubles with rusted frames? 
    • Batteries don’t always show signs of a few years ago my vehicle started fine in the morning and took me to work. After work the battery was completely dead and I needed a jump. No, I didn’t leave anything on and the battery was only a couple months old. It was replaced under warranty. 
    • AFM is confirmed in the Corvette engine, so I'm assuming the higher volume trucks will get it as well
    • If his battery was that bad I would think it would have been showing signs before this that were ignored. Stinks that it happened the way it did in rush hour traffic, but this seems like a pretty fringe scenario. I don't mind it that bad and never turn it off. The only slight annoyance for me is the slight delay between brake to gas, but I have gotten used to it and figure if it can save a little gas why not.
    • That is a good correction. I think “severity” was probably the wrong word for what I meant. What I really mean is closer to event priority, relevance, and actionability — not “this code is severe” or “replace this part.” I agree that a truck can have a lot of trivial or historical communication codes, and if the product starts pushing alerts for every stored or low-value event, people will ignore it very quickly. So the alert logic would need to be filtered. For example, I would not want a random old communication code to generate a push notification by itself. A useful alert would probably need to be based on things like: - new vs historical - active vs stored - repeated vs one-time - duration of the event - whether it happened near the driver-marked symptom - whether it happened together with voltage drop, reset, bus-off, misfire, oil-pressure change, etc. - whether the same pattern repeats under similar conditions So instead of saying “severity,” maybe the product should organize events by affected system and priority. For example: Misfire event: Show misfire counts / roughness first, then fuel trims, RPM/load, DFM/AFM state if available, coolant/oil temp, voltage, and related DTCs. Oil-pressure event: Show oil pressure first, but only in context — RPM, load, oil temperature, coolant temperature, DFM/AFM state if available, voltage, and baseline comparison. Communication event: Show which module/network/message dropped, whether voltage dropped, whether the recorder reset, whether it was active or historical, and whether it repeated. Voltage/reset event: Show battery voltage, crank/wake/sleep state, module reset, communication dropouts, and what came back online first. That also solves the display-order problem you mentioned. The main report should not always show the same fixed list first. It should show the system that appears abnormal first, and then the supporting values for that system. I also agree that the truck already has an oil pressure gauge and MIL. The point would not be to duplicate those. The value would be in showing what else was happening before and after the warning or symptom. For example, if the MIL comes on for a misfire, the truck already told the driver there is a problem. The useful part would be: - which cylinder or bank looked abnormal first - whether it happened after an AFM/DFM transition - whether fuel trims were already moving - whether oil pressure or voltage changed at the same time - whether the same pattern happened previously without a MIL On the OBD port point, I think you may be right for a consumer-facing version. OBD is much easier for the average owner: - easier install - easier removal - inside the cabin - easier phone connection - easier data download - easier to include a pass-through port for another scanner OBD is also the right place for DTCs, freeze frame, VIN, calibration information, Mode 6, and normal scan-tool parameters. The reason I was looking at ECM-side recording is that some events may be gone by the time someone plugs in a scanner, and some powertrain-side network evidence may not be available the same way through the DLC. But I agree that if an OBD-based version can capture enough useful evidence for most owners, that is probably the cleaner consumer product. Maybe the split is: - OBD/DLC version for most consumers - ECM-side version only if it proves it adds evidence that the OBD version cannot get - shop/pro version if deeper powertrain-side event evidence is actually useful So I would not want to force the inline approach if the OBD workflow solves most of the real-world problem. Your last point is probably the key product requirement: the report should be specific to the system showing the abnormality. Not “here are 50 parameters.” More like: “Misfire-related event detected. Here are the misfire/fuel/DFM/context values.” or “Oil-pressure-related event detected. Here is oil pressure compared with RPM/load/temp/baseline.” or “Communication event detected. Here is what dropped, when, and whether voltage/reset happened first.” That is a much better way to think about the report.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...