frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Open in hackernews

Best practices for long-run LED strip installs (20–50M) to avoid flicker?

17•emmasuntech•4d ago
I’m working on a long-run LED strip installation (think 20–50 meters) and I’m trying to keep brightness and color consistent end-to-end. On typical constant-voltage strips, the far end dims and “white” shifts, and under high load I sometimes see flicker.

So far I’ve tried the usual: higher voltage rails (e.g., 24V), thicker feeder wires, cleaner connectors, and power injection. It helps, but I’m curious what approaches people here consider “best practice” for reliability and serviceability.

Questions:

For long runs, do you prefer distributed power injection vs multiple smaller PSUs vs a higher-voltage backbone + local regulation?

Have you had good results with constant-current strips or per-segment regulation to reduce voltage-drop artifacts?

For addressable strips (WS281x/SPI/DMX), what are your go-to fixes for signal integrity over distance (grounding, buffering, differential, level shifting)?

Any rules of thumb for wire gauge, injection spacing, and PSU headroom that have held up in real installs?

I’m not looking for product recommendations as much as engineering patterns that scale and don’t become a maintenance nightmare. Would love to hear what’s worked (and what didn’t).

Comments

afandian•1h ago
May not be directly applicable but Mike Harrison makes professional LED installations and has a lot of wisdom and insight.

https://m.youtube.com/playlist?list=PL0KZLmPyL6AnkPSs5cGU437...

pelorat•1h ago
Being a home tinkerer that have a few meters of LED strips, I'd use multiple drivers.
jwrallie•1h ago
How about measuring voltage across the strip and modeling the system resistance (per meter)?

You can measure the voltage where you are observing problems to understand your margins.

Your solutions are sound, you just need to throw in some math to optimize them to each application.

123pie123•1h ago
Chances are you'll need to start using different protocols (eg rs-485) to communicate over the long distance to numerous controllers that output the data to the LEDs.
NoiseBert69•1h ago
Slow RS485 or CAN. The differential nature of that system sphysically removes most the the unwanted signals.
sen•1h ago
I’ve done multiple projects that use 20m+ of WS2812s.

I deliver the main power in segments from a single large PSU and run 5v signal (despite being designed for 3.3v signal most will handle 5v fine and works better for longer strips).

Running segments with connectors also makes it easier to swap out failed segments.

15155•47m ago
> 5v signal (despite being designed for 3.3v signal most will handle 5v fine

All WS2812B parts that I am aware of are specified for 5V signal and 5V power, not 3.3V.

Some brands won't even accept 3.3V input signals and require level shifting.

herczegzsolt•1h ago
I've not quiet worked with that long LEDs, but i have experience with 10-20m length indoor installations.

For our standards, we supply the strips with power at both ends and at every 5m in-between. (So an LED is at most 2.5m away from a supply). Your supply needs may vary significantly depending on the type of LED you use, these numbers worked for us on WS2812B 60led/m at 5V rail voltage.

> For long runs, do you prefer distributed power injection vs multiple smaller PSUs vs a higher-voltage backbone + local regulation?

Either should work fine, but when you use multiple PSUs or regularors, you may need to match their output voltage suprisingly precisely to get good results. A pair of thick copper wires is often easier.

> For addressable strips (WS281x/SPI/DMX), what are your go-to fixes for signal integrity over distance (grounding, buffering, differential, level shifting)?

WS28xx has built-in "reclocking" as long as your longest distance between two adjacent leds is <1m, you are absolutely fine. Be aware though that the number of chained LEDs impact your maximum refresh rate, which is an issue for animating. For a 60Hz refresh rate, you can't have more than ~250leds.

SPI is a nightmare over any distance. DMX is great if you respect the standard in terms of cabling and unit loads, but it i'm yet to see a DMX-enabled individually addessable LED strip. A DMX universe would be limited to 170 rgb or 128rgbw leds anyway.

> engineering patterns that scale and don’t become a maintenance nightmare.

Use a projector or a TV instead :-D

Havoc•1h ago
If you’re already doing segments with separate power injection you may as well split it entirely.
piva00•43m ago
This would be my suggestion as well. I helped some art projects running 50-100m of LEDs, we first attempted segmenting and power injecting but it was much easier to just split them all up, and ultimately using a LED controller with many outputs to send data.

I don't think in OP's case a controller such as the Advatek ones would be attractive, they are quite expensive but perhaps some WLED-flashed boards being centrally coordinated could be a last resort given it would increase complexity and potential brittleness to the setup.

formichunter•1h ago
I designed my led system at home in the basement which is not as big but same principle. It all depends on: 1. Distance 2. Type of LED: W, RGB, RGBW, RGBWCCT 3. Brand of LED manufacturer 4. Number of LED per meter aka amperage draw 5. 24v verse 12v

If this is a loop, like a rectangle, you can inject from beginning and end since that is the same point, otherwise, you'll need power injected at some distance. For long distances you'll need to calculate the power loss to figure that out. I used quinled.info site to get all this information and decided upon an RGBW LED setup using 24 volts and injecting at beginning and end of rectangle. This was for 20 meters, fyi, not 50 meters. RGBWCCT was too much amperage draw over distance and this was my first time doing it. Learn how to solder because using the snap-on connectors suck...I am redoing those connectors by soldering b/c two have failed so far.

godelski•1h ago
Have you tried filters?

If you're getting flickers that's probably the best thing to do. This will cut your total power but you'll get a smoother signal. If it is visible then that is relatively low frequency but you might want to play around with it. The easiest thing to test (because you're more likely to have the parts accessible) is a pi-filter and then if that seems to be working you can either stick with that or use a better filter.

antonkochubey•41m ago
If you supply ground from one end, and +24V (or whatever) from the other end, brightness will be equal throughout the strip :)

But it would also be a good idea to measure voltage drop when it's powered on, and compensate accordingly, if your PSU allows for it.

eemil•18m ago
What a brilliant, simple solution. This way each segment in the LED strip has an equally long current path, and should have identical voltage/brightness.

---

That being said, 20-50m is a really long run even with 24V LEDs. Even using this trick, you'll run into significant voltage drop and heat in the LED strip's copper traces since they're only so thick. There's a reason why manufacturers specify a maximum length. I would check the datasheet and split the strip into multiple segments depending on this value. Maybe there are some LED strips designed for this use-case, with an even higher voltage and/or thicker traces.

amluto•39m ago
What safety and regulatory requirements do you need to meet?

If you need NEC class 2, both Lutron and ERP make UL listed 24V class 2 supplies. You can calculate what length you can drive at 4A (96W) and drive that much. The Lutron one dims and the ERP does not, but you can chain an eldoLED or other “dimmer” between the ERP supply and the strip with excellent results. There is no perceptible flicker with either of these, and IIRC both Lutron and eldoLED even claim IEEE1789 compliance. (At least the Lutron one does leave sort of perceptible spots when dimmed when you saccade perpendicular to it, and you need to go to rather high frequency to avoid this. Of course, this is a nonissue at 100% duty cycle.). I have used both of these with strips from different power supplies butted up to each other with no perceptible brightness mismatch.

48V strips are a thing.

If you don’t need NEC class 2, you could try a much larger DC supply. You might consider circuit breakers to protect individual segments and wires. DIN-rail thermal-magnetic breakers rated for more than 24VDC are cheap, but they will buzz horribly if you apply PWM to them.

You’d be on your own in regard to regulation, but I bet most “120V driverless” strips work just fine at 120 times sqrt(2) DC volts, and they won’t flicker. You will get more than the design output and more heat, but no flicker. Test first and take appropriate care for safety.

Don’t use “driverless” strips with sine wave input. The 120Hz flicker is horrible.

Some LED strips contain internal constant current limiters that will give a roughly constant output across a (small) range of voltages. This may help.

yair99dd•11m ago
https://learn.adafruit.com/1500-neopixel-led-curtain-with-ra...

What an unprocessed photo looks like

https://maurycyz.com/misc/raw_photo/
1746•zdw•14h ago•286 comments

Kidnapped by Deutsche Bahn

https://www.theocharis.dev/blog/kidnapped-by-deutsche-bahn/
160•JeremyTheo•1h ago•152 comments

CIA Star Gate Project: An Overview (1993) [pdf]

https://www.cia.gov/readingroom/docs/CIA-RDP96-00789R002800180001-2.pdf
28•dvrp•10h ago•17 comments

Feynman's Hughes Lectures: 950 pages of notes

https://thehugheslectures.info/the-lectures/
40•gnubison•2h ago•6 comments

Show HN: Z80-μLM, a 'Conversational AI' That Fits in 40KB

https://github.com/HarryR/z80ai
248•quesomaster9000•7h ago•66 comments

Kubernetes egress control with squid proxy

https://interlaye.red/kubernetes_002degress_002dsquid.html
17•fsmunoz•1h ago•8 comments

You can make up HTML tags

https://maurycyz.com/misc/make-up-tags/
331•todsacerdoti•10h ago•122 comments

Huge Binaries

https://fzakaria.com/2025/12/28/huge-binaries
92•todsacerdoti•7h ago•31 comments

Developing a Beautiful and Performant Block Editor in Qt C++ and QML

https://rubymamistvalove.com/block-editor
78•michaelsbradley•2d ago•22 comments

My First Meshtastic Network

https://rickcarlino.com/notes/electronics/my-first-meshtastic-network.html
80•rickcarlino•8h ago•25 comments

Unity's Mono problem: Why your C# code runs slower than it should

https://marekfiser.com/blog/mono-vs-dot-net-in-unity/
214•iliketrains•15h ago•114 comments

As AI gobbles up chips, prices for devices may rise

https://www.npr.org/2025/12/28/nx-s1-5656190/ai-chips-memory-prices-ram
203•geox•14h ago•304 comments

Market design can feed the poor

https://worksinprogress.co/issue/how-market-design-can-feed-the-poor/
10•ortegaygasset•2h ago•2 comments

Show HN: See what readers who loved your favorite book/author also loved to read

https://shepherd.com/bboy/2025
5•bwb•1h ago•1 comments

Software engineers should be a little bit cynical

https://www.seangoedecke.com/a-little-bit-cynical/
221•zdw•15h ago•153 comments

Staying ahead of censors in 2025

https://forum.torproject.org/t/staying-ahead-of-censors-in-2025-what-weve-learned-from-fighting-c...
173•ggeorgovassilis•7h ago•161 comments

Researchers discover molecular difference in autistic brains

https://medicine.yale.edu/news-article/molecular-difference-in-autistic-brains/
150•amichail•15h ago•81 comments

Asking Gemini 3 to generate Brainfuck code results in an infinite loop

https://teodordyakov.github.io/brainfuck-agi/
58•TeodorDyakov•3h ago•61 comments

MongoBleed Explained Simply

https://bigdata.2minutestreaming.com/p/mongobleed-explained-simply
206•todsacerdoti•16h ago•90 comments

PySDR: A Guide to SDR and DSP Using Python

https://pysdr.org/content/intro.html
189•kklisura•17h ago•10 comments

You can't design software you don't work on

https://www.seangoedecke.com/you-cant-design-software-you-dont-work-on/
16•saikatsg•5h ago•2 comments

Show HN: My not-for-profit search engine with no ads, no AI, & all DDG bangs

https://nilch.org
105•UnmappedStack•8h ago•53 comments

Spherical Cow

https://lib.rs/crates/spherical-cow
107•Natfan•14h ago•16 comments

Formally Verifying Peephole Optimisations in Lean

https://l-m.dev/cs/formally-verifying-peephole-optimisations-in-lean/
15•l-mdev•6d ago•5 comments

Fast GPU Interconnect over Radio

https://spectrum.ieee.org/rf-over-fiber
37•montroser•9h ago•6 comments

Koine

https://github.com/pattern-zones-co/koine
14•handfuloflight•3d ago•3 comments

Mouse: Computer Programming Language (2006)

http://mouse.davidgsimpson.com/
19•gappy•2d ago•4 comments

Line scan camera image processing

https://daniel.lawrence.lu/blog/2025-09-21-line-scan-camera-image-processing/
52•vasco•4d ago•3 comments

UK accounting body to halt remote exams amid AI cheating

https://www.theguardian.com/business/2025/dec/29/uk-accounting-remote-exams-ai-cheating-acca
4•beardyw•21m ago•1 comments

Slaughtering Competition Problems with Quantifier Elimination (2021)

https://grossack.site/2021/12/22/qe-competition.html
63•todsacerdoti•14h ago•0 comments