Jump to content

Recommended Posts

Posted

I have 50 watt from TRS with the FXR projector. I wouldn't run them before because they were yellow. I don't run them now as they blinding people, but I'd like to be able to use them in Fog.

 

I talked with VLEDs today and I can't put a relay to control one side of the light, so I will be making a color with a reflector to mount on the lights to keep the cut off low and usable. Got to many other things going to do it right away they way I want. I might use the lathe to make a quick set from bar stock and cut half to get started this weekend if I find some time. I want to get to a mill to make a sharper cutoff for the final.

I agree with your opinion of the light spread on your fogs. I'm looking for a traffic friendly, yet effective fog option and I think you're right on track. Could you take a pic of the bulb before you install it to show how you cover the one side? Also, on my gmc there is minimal room behind the bulb and most of these bright led deals have cooling fans on them so clearance is a concern of mine. Any issues with yours??

I have the trs projector and 50 watt hid kit sitting on my work bench but want to do the fogs at the same time... can't tell you how anxious I am to do what gm should have and get the lighting in this thing back on track.

Thanks in advance, good looking set up you have there.

 

2015 Denali 3500 DRW, Michelin ltx, 4x4

Posted

Check out my gallery for LED foglights. I have not road tested yet as it is appart for other customizing.

  • 2 weeks later...
Posted

The problem with HID and LED bulbs in the stock fog housing is the bulb length. The stock 5202 bulb sits deep in the housing which is what give it the great bream spread and brightness. The HID/LED bulbs tend to be longer and sit further towards the lens which changes the beam pattern making it worse.

 

Until someone comes out with a similar bulb to the stock one there will not be much hope for the stock fog housings.

Posted (edited)

The problem with HID and LED bulbs in the stock fog housing is the bulb length. The stock 5202 bulb sits deep in the housing which is what give it the great bream spread and brightness. The HID/LED bulbs tend to be longer and sit further towards the lens which changes the beam pattern making it worse.

 

Until someone comes out with a similar bulb to the stock one there will not be much hope for the stock fog housings.

VLED LMZ bulbs are adjustable in depth. Give them a try. I have a set coming in for my headlights and Crf450r420 has them in the fogs of his Silverado already. Edited by Mike1220
  • Like 1
  • 1 month later...
Posted

VLED LMZ bulbs are adjustable in depth. Give them a try. I have a set coming in for my headlights and Crf450r420 has them in the fogs of his Silverado already.

Do you have an update on how these work?

  • 1 month later...
Posted

I have not changed mine. But I do know that if you try to change a light that has to do with the blinker system, then you will get the hyper blink and then a message on the DIC saying that there is a left/right turn signal error. I'm surprised GM didn't put LEDs there stock. Many other manufactures are already switching to tail light LEDs, but since we are talking about trucks, I think it's just becuase trucks are not necessarily a family or DD vehicle, however it does seem that they are making their way to the category

 

 

Sent from my iPhone using Tapatalk

Hey Mike,

 

I got a set of the Eagle Eye Lights and they have the boxes which I thought would have been some type of correction for the system, but I'm getting a normal blink for the first few seconds then a hyper blink and the message on the DIC with the signal error, so what type of load resistor are you referring to in the post?

Posted

Yours may be defective. Mine worked out of the box with no problems. Just FYI

 

Sent from my phone using some app!

  • 1 month later...
Posted

I searched through this topic and others but couldn't find a definite answer. For the front turn signals / parking lamps on the Silverados, are the sockets standard or CK?

Posted

I think I've read all the comments on changing the stock bulbs for the rear brakes, side lights and front blinkers with LEDs.

I think the rear stop/turn are: 7444 or 7444LL

front turns: 7443 or 7443LL

licence plate: 194

These seem to be available from many sources, but I'm more concerned with the low voltage and getting the

hyper-blink. Is there an LED replacement bulbs that have built in "choke" to stop thjis hyper-blink or will I have

to figure out what to use and where to install this item to stop the hyper-flash?

Does the "LL" in the part number mean anything when using LED replacements? I can't find replacements with

LL suffix?

any assistance would be greatly appreciated...

Posted

Ive went thru but don't think ive seen an answer to my question

 

 

I want to replace my stock halogen bulbs with LEDs, is this possible without any type of conversion/kit. Hoping its a simple plug and play, like changing to another halogen bulb.

 

 

 

Thanks in advance

  • Like 1
Posted

The LL is for "Long Life". Means nothing in the LED department, since all LEDs are long lasting.

 

As for the choke, VLEDs sells a flasher unit for $20, to replace your stock flasher in your fuse box, and stop all hyper blinking. This eliminates the need for load resistors.

 

 

Sent from my iPhone using Tapatalk

  • Like 1
Posted

Thanks Victor for the answers on LL & load resistors... quick follow up question, with the Denali w/ the brake controller option,

would the VLED's flasher unit be necessary? Just not sure with that package, the truck came with a H.D. flasher? Truck DID not

come with the trailer package.. just the brake controller???

thanks again

Posted

Thanks Victor for the answers on LL & load resistors... quick follow up question, with the Denali w/ the brake controller option,

would the VLED's flasher unit be necessary? Just not sure with that package, the truck came with a H.D. flasher? Truck DID not

come with the trailer package.. just the brake controller???

thanks again

Billy, I really do not know. I would guess yes, seeing as the flasher unit is essentially an electromechanical circuit in your fuse box. It's basically a fuse, of sorts (but I may stand corrected as I'm not exactly the brightest when it comes to electrical stuff).

 

Cheers!

 

 

Sent from my iPhone using Tapatalk

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 2,121 Guests (See full list)


  • Latest Articles

  • Posts

    • 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
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...