Jump to content

LED Conversion, Lasfit or others?

Bigfoot98
 Share

Recommended Posts

Bigfoot98 Enthusiast

Bigfoot98

Posted
Posted

I searched the forum a bit and found that most people were going with lasfit a while back, is that still the case?

I saw a few others going with Amazon specials or oxilam as well.

What holds up the best with no hyperflash?

I was going to use Sylvania but they say that newer vehicles need to add a load kit to not hyperflash which I'm not interested in doing, plug and play only with a quality bulb is what I'm after.

Tedk Enthusiast

Tedk

Posted
Posted

I went with Lasfit on my last two Silverados for my reverse and plate lights. No issues at all and they are bright. 

Transient Senior Enthusiast

Transient

Posted
Posted

This is the first vehicle I've ever done this with and I've been very happy about going with lasfit.  Only situation I've had an issue with was one where I had read it would be an issue in the first place.  I was in heavy traffic, left turn lane to get onto the freeway.  On ramp was metered, and all 3 lanes were backed up.  It took 4 light cycles to get through the back and onto the freeway on ramp.  I had a police officer behind me, so I made sure to have my left turn signal the entire time.  After the 3rd light cycle by turn signal went into hyperflash mode.  I keep it on, though.  I got onto the freeway, down the HOV lane, other freeway, etc.  Next time I had to make a left turn, in that same trip, my left signal was back to normal flashing mode.  The resistor built into the light just needed to cool down a moment.  There doesn't appear to be any damage, and it has worked perfectly fine since.

 

I would recommend Lasfit to anybody.  And, I found them on Amazon. 

davidr83 Enthusiast

davidr83

Posted
Posted
23 hours ago, Bigfoot98 said:

I searched the forum a bit and found that most people were going with lasfit a while back, is that still the case?

I saw a few others going with Amazon specials or oxilam as well.

What holds up the best with no hyperflash?

I was going to use Sylvania but they say that newer vehicles need to add a load kit to not hyperflash which I'm not interested in doing, plug and play only with a quality bulb is what I'm after.

What model/trim do you have? I ask because I went with lasfit on my 2020 elevation and I replaced the license plate and reverse lights with no issue, but when I did the front and rear blinkers, I had hyper flash even though the lights were advertised as being hyper flash free. Wasn't the case and I had to figure out a solution. (WAMS to the rescue there)

 

Then I traded into a 2021 RST and used the same lights on this truck, minus the rear blinker bulbs and had no hyper flash from the bulbs. The stock rear blinkers are LED already on the RST.

 

Just something to be aware of.

Bigfoot98 Enthusiast

Bigfoot98

Posted
  • Author
Posted
21 minutes ago, dram1983361 said:

What model/trim do you have? I ask because I went with lasfit on my 2020 elevation and I replaced the license plate and reverse lights with no issue, but when I did the front and rear blinkers, I had hyper flash even though the lights were advertised as being hyper flash free. Wasn't the case and I had to figure out a solution. (WAMS to the rescue there)

 

Then I traded into a 2021 RST and used the same lights on this truck, minus the rear blinker bulbs and had no hyper flash from the bulbs. The stock rear blinkers are LED already on the RST.

 

Just something to be aware of.

It's a '20 RST

I went ahead and ordered the whole package.

Winchester3003 New Member

Winchester3003

Posted
Posted

2020 Silverado Double Cab Custom, replaced my halogen bulbs for LED's. I am used to HIDs from previous vehicles, but these LEDs were much less of a hassle ( no fuses or relays to worry about ) Amazon.com : BEAMTECH. I am still using my dust cover with these on, I did check on the covers as well as the bulb after installation to make sure nothing went wrong and see how they are holding up. One year later best upgrade so far. 

 

A trick that helped me and something to keep in mind: remove the rubber seal from the halogen bulb ( mine was a redish ~ orange ) and install the rubber seal onto the new LED bulb ( my LED bulb came with a blue rubber seal so I removed it to install the halogen seal ) regardless of who you end up going with, check for water leaks but this should make your install much much smoother.

RSVolcom Enthusiast

RSVolcom

Posted
Posted (edited)

Installed Lasfit back in April.  No issues to date.

 

Turn Signal Lights: (Featured in video): https://www.lasfit.com/products/lasfit-7440-7441-w21w-led-turn-signal-lights-canbus-error-free?rq=na_led-bulbs~mk_chevrolet~md_silverado-1500~yr_2020~zq_all-trims~dz_front-turn-signal-light-for-other-trims&afmc=1tz&utm_campaign=1tz&utm_source=leaddyno&utm_medium=affiliate

 

Reverse Lights: https://www.lasfit.com/collections/led-whole-package-for-chevrolet-silverado/products/2019-2020-chevrolet-silverado-custom-fit-led-headlight-low-beam-h11-w-dust-cover?afmc=1tz&utm_campaign=1tz&utm_source=leaddyno&utm_medium=affiliate&variant=32291466969172

 

This was the hardest one to complete.  Small area to work with and if you have big hands it's a pain.  Stepped away from it for a day and with a calm head, I was able to get them both completed.

License Plate Lights: https://www.lasfit.com/products/2x-lasfit-t10-192-194-168-158-led-interior-light-bulb-error-free-1-year-warranty?rq=na_led-bulbs~mk_chevrolet~md_silverado-1500~yr_2019~zq_all-trims&variant=31351454826580

 

Edited by RSVolcom
  • 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
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts

  • Member Statistics

    342,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined

  • Who's Online   3 Members, 0 Anonymous, 1,554 Guests (See full list)

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