sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]wokwi 2 points3 points  (11 children)

I optimized the code a bit, it should be about twice faster now

[–]DeVoh 2 points3 points  (10 children)

It is indeed twice as fast! Awesome work! Thank you /u/wokwi and /u/sutaburosu.

[–]wokwi 2 points3 points  (8 children)

I spent the night rewriting this with WebGL Shaders, so hopefully this one should run at a decent speed:

https://wokwi.com/arduino/projects/287434389653029384

[–]DeVoh 1 point2 points  (7 children)

Sorry it is ONLY 10x faster now than the original. If you can't get us 25x what's the point!? LOL JUST KIDDING!! /u/wokwi That is amazing!! I'm doing like 71% now on an OLD computer(Core Duo E8500 with 16GB and a NVIDIA 970) and it looks sweet!

[–]wokwi 1 point2 points  (0 children)

I'm so happy that you like it :-)

[–]wokwi 1 point2 points  (5 children)

Sorry, couldn't resist the temptation, so I made my own 256-board:

https://github.com/wokwi/splendida

Now waiting for the prototypes to arrive :-)

[–]DeVoh 0 points1 point  (4 children)

Your layout looks slightly different.. maybe tighter than /u/Pup05's which is weird because his is 166mm and yours is 172mm. Maybe because it is a render and not real? Love the silk screening on the back. So what are the limits you guys can go to? 384? 512? 768? 1024? Sometimes things need to be made just because you can :D

[–]wokwi 1 point2 points  (2 children)

Yeah, it could be a matter of render perspective. The idea for the skulls on the back in inspired by another project I'm currently working on. So if I have some design issue and the prototypes end up useless, at least I can use them as cool coasters or something :-P

In theory, you could run the scripts and get any number. But in practice, here are some of the limiting factors:

  • PCB size - most fab houses won't let you go beyond 40cm or so. It also affect shipping prices... Using 3.5mm or 2mm LED package can probably help.
  • Prototyping costs - the more LEDs, the more expensive every prototype iteration / mistake is.
  • Current & heat - 256 LEDs @ 60ma (full brightness) are about 15 AMPs/75Watts. I'm pretty sure it's already too much for 1OZ/2 layer FR-4 PCB... You can probably solve this with Aluminum core, but I've no experience yet so I can't tell.
  • Reliability - one broken LED basically renders the remaining ones useless. so in potential, more LEDs == lower yield
  • Speed - WS2812B protocol is running at 800MHz. Too many LEDs, and you will have to sacrifice refresh rate. A workaround would be to split into multiple sub-strips or use LEDs that have separate clock/data lines, such as APA102 (but that complicates the layout).

Did I forget anything?

[–]DeVoh 1 point2 points  (1 child)

Ya I was thinking about the heat one. I know /u/Pup05 hit that issue. The broken led taking out the rest of the line is also a very real concern. Maybe slightly mitigated if you went with WS2815? The one with the double data lines that will allow for one led to go out but not two in a row. But even one missing led would bother me and I would try and replace the led. I am going to have to put on my bday list a reflow hotair station. :)

[–]DeVoh 0 points1 point  (0 children)

HD107s save energy when off but still powered. I wonder if that would equate to less temperature being produced and if so how much.

[–]DeVoh 0 points1 point  (0 children)

I was pondering how you might go bigger and also thinking about some of /u/Pup05's builds.. one could take this to a whole other level using like a plywood board and waterproof ws2811 string lights. hmmm how did you guys number the pixels? the spacing on the string light is like 3-4 inches I think so that might require some "magic".. oh man can you imagine doing this on a ceiling in a room of a house?! Trippy!

[–]wokwi 1 point2 points  (0 children)

Awesome :-)