frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Start all of your commands with a comma (2009)

https://rhodesmill.org/brandon/2009/commands-with-comma/
211•theblazehen•2d ago•64 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
686•klaussilveira•15h ago•204 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
960•xnx•20h ago•553 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
127•matheusalmeida•2d ago•35 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
65•videotopia•4d ago•4 comments

Jeffrey Snover: "Welcome to the Room"

https://www.jsnover.com/blog/2026/02/01/welcome-to-the-room/
30•kaonwarb•3d ago•26 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
45•jesperordrup•5h ago•23 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
236•isitcontent•15h ago•26 comments

ga68, the GNU Algol 68 Compiler – FOSDEM 2026 [video]

https://fosdem.org/2026/schedule/event/PEXRTN-ga68-intro/
8•matt_d•3d ago•2 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
230•dmpetrov•15h ago•122 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
334•vecti•17h ago•147 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
27•speckx•3d ago•17 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
500•todsacerdoti•23h ago•244 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
384•ostacke•21h ago•97 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
296•eljojo•18h ago•187 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
360•aktau•21h ago•183 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
421•lstoll•21h ago•281 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
67•kmm•5d ago•10 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
95•quibono•4d ago•22 comments

Was Benoit Mandelbrot a hedgehog or a fox?

https://arxiv.org/abs/2602.01122
21•bikenaga•3d ago•11 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
33•romes•4d ago•3 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
262•i5heu•18h ago•212 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
38•gmays•10h ago•13 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1074•cdrnsf•1d ago•460 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
61•gfortaine•13h ago•27 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
294•surprisetalk•3d ago•46 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
153•vmatsiiako•20h ago•72 comments

The AI boom is causing shortages everywhere else

https://www.washingtonpost.com/technology/2026/02/07/ai-spending-economy-shortages/
14•1vuio0pswjnm7•1h ago•1 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
159•SerCe•11h ago•148 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
74•phreda4•14h ago•14 comments
Open in hackernews

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

20•emmasuntech•1mo 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•1mo 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•1mo ago
Being a home tinkerer that have a few meters of LED strips, I'd use multiple drivers.
jwrallie•1mo 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•1mo 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•1mo ago
Slow RS485 or CAN. The differential nature of that system sphysically removes most the the unwanted signals.
sen•1mo 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•1mo 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•1mo 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•1mo ago
If you’re already doing segments with separate power injection you may as well split it entirely.
piva00•1mo 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•1mo 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•1mo 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•1mo 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•1mo 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.

windexh8er•1mo ago
Edge injection works extremely well, but still has distance limitations. You're not going past 20m per segment of power with something like WS2811s. There's no way to do 50m without power injection within the segment, even with 24v strips. That is unless they're not RGB or low density.
amluto•1mo 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•1mo ago
https://learn.adafruit.com/1500-neopixel-led-curtain-with-ra...
lumencache•1mo ago
Distributed power injection and "CC" strips. The CC chips in the segments provide constant current to the segments allowing the voltage drop along the strip. If you inject to infrequently, the drop will be high and the chips in the feed end will dissipate a lot of heat, so it's likely you will be servicing those ends. Feed more frequently and you'll avoid this. WS281x usually have seperate shift registers inside, so they usually have no signal degradation--theoretically. In practice, recommended you segments feed those signals, but can be much longer depends on the number of nodes and the size of your controller frame buffer.
windexh8er•1mo ago
There's many guides out there for exactly this, but this one from QuinLED is probably the best [0].

You can't really avoid power injection downstream. I'm not sure if you're using 24v LEDs based on your ask (you said rails). But even with 24v strips at 20m you'll need 4A edge injection with 720 LED/m. This is literally one of the most simplistic approaches without being under powered.

[0] https://quinled.info/the-ultimate-led-strip-power-injection-...

zuccs•1mo ago
Did you learn nothing: https://news.ycombinator.com/item?id=46390875 ?
Tracy978•1mo ago
I've worked on several 20-50m long LED strip projects (including CV + addressable). The issues you described—"brighter at the beginning, dimmer at the end, white turning yellow, flickering under heavy load"—are basically problems with power distribution, connections, and signal links. Below is my long-term, stable approach (leaning towards an "engineering model," prioritizing maintainability over minimal cabling):

1) Power Topology: Separate "voltage transmission" and "load power supply" into layers.

I generally don't gamble on a single-ended path. A more reliable approach is: zoned power supply (every 5-10m section) + star/tree topology, with clear fuse/open circuit protection for each section, allowing for quick fault location.

If site conditions permit, I prefer a higher voltage backbone (e.g., 24V/48V) + zoned step-down/regulation: lower backbone current, lower line loss, localized voltage regulation/power supply at zoned ends, and more intuitive maintenance.

Regarding the choice between "multiple small PSUs vs. one large PSU," I prefer multiple small PSUs (or a large PSU with multi-branch protection). The core reason is: fault isolation and maintenance without affecting the overall system. However, this requires a unified grounding strategy to avoid signal/noise issues caused by ground loops.

2) Constant current/segmented adjustment: can significantly improve "brightness and color consistency," but don't treat it as a panacea.

Constant current/segmented adjustment can indeed reduce visual problems such as "darkening at the end and white drift," especially in scenarios where linear consistency is desired.

However, it cannot replace fundamental aspects: PSU margin, zoned protection, wire gauge, connection reliability, and heat dissipation. Many "flickering" issues are actually transient problems caused by PSU triggering protection/voltage sag/increased connector resistance.

3) Addressable Signal Integrity: Design "data" as a communication link.

SPI/WS281x Class: My commonly used combination is:

Keep data lines as short as possible (controller close to the first segment).

Add buffering/reshaping if necessary (re-drive every segment).

Use differential transmission (RS-485, etc.) for long-distance traces and then convert back at the end.

Use a unified ground (single-point grounding/partitioned grounding strategy must be clearly defined), and avoid bundling data lines too close to high-current harnesses.

By the way, this article focuses on the differences and selection of DMX vs SPI:https://suntechlite.com/dmx-led-strip-vs-spi-led-strip/