Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About bwinter

  • Rank
    New Forum User

Profile Information

  • Occupation

More About Me

  • Favorite Decorating Holiday?
  1. Thanks Steven--glad to know this concept works!
  2. Now that I think about it more, I think a *snowflake* is water-VAPOR that's crystalized around a nucleation point (a lengthy process as the flake develops in the atmosphere). *Sleet* is a water-DROPLET that's frozen to ice. Anything that comes out of a hose would be a water droplet (even if it's a mister--it's just a smaller droplet/smaller sleet-pellet). That's why you can tell when a ski-slope has used artificial "snow"--it's grainy (because it's sleet). I doubt "SNOW-machine" (in the proper sense) is even an accurate term. I think they're really just SLEET-machines. But yeah, play a
  3. Interesting--I'll have to research this further--definitely the type of info I was hoping to get! I had anticipated that I'm probably going the e131 route, but haven't spec'ed out any specific controllers yet.
  4. As I said earlier: 30 vs 150 channels--PER ELEMENT, and I've already stated that I want may want multiple of these elements. Any I'm only limiting myself in that I can't do a swirl (on a secondary accent piece--no big deal). I already have plans for more advanced elements--every single LED in a show doesn't need to be independently controlled. My question wasn't whether or not I SHOULD do this, from a design-perspective. It was whether or not I COULD do this from a technical-perspective.
  5. I would question if you would actually be making *snow* or would it be *sleet*? My understanding is that the formation of a snowflake (that light, airy, fluffy thing you want), is a rather complicated process of crystallization of water around a nucleation point (that takes a significant amount of time, as the flake falls/floats through the atmosphere). This is something that ski slopes try to deal with, as their "artificial snow" is often very icy/grainy (I.e., "sleet"). Just my speculation, though...
  6. So Ron, if I went with the dumb RGB route you suggested, each "ring" would have to be wired together as one strand? Given the spacing between each LED, especially in the outer rings, I would need to splice each LED to get the required distance separation?
  7. Honestly, I'm quite okay that my stars could only do bursts, and not spins. I guarantee I wouldn't be disappointed that I can't do spins.
  8. As far as "why" I would want to, there are numerous variation on this element I can think of. One logistical reason, though, is the number of channels required. My configuration would require 30 channels (10 LEDs/arm X 3). Wiring my element in the normal "series" configuration would require 150 channels (10 LEDs/arm X 5 arms X 3). Sure, I would lose a bit of functionality (couldn't do spins and control each arm independently), but that's okay--these are just secondary accent pieces (and I may want many of these elements). So economy-of-scale is a factor. And secondary, I'm just wondering wh
  9. Ron--if your element is connected in the way I'm describing, how can you do "spins"? A "spin" (basted on my limited understanding) would require that each arm be controlled independently. I don't think my description/configuration would allow that. I agree with the "burst" though, as each ring (inner, outter, 2nd, 3rd, etc.) can be controlled as a group.
  10. Thanks Jim--so do you think the concern is with "driving" the data, or driving the power to each arm? Or say, for example, I wanted to take my "5-pointed star" configuration, and fold it into a "mini-tree" configuration, adding several more arms. How many arms could I add, before running into problems? I would think it's trivial/easy (but important) to POWER each arm independently. So it would seem to me, the main concern is with "driving" the data down multiple arms "in parallel" (I don't even know what the correct term is to describe that).
  11. So no practical experience here, just been looking over wiring schematics and trying to understand how to configure elements. I do have a question on whether or not this configuration below would work: Say I built a simple 5-pointed star. Each "arm" of the star is a simple straight line of 10 RGB smart LEDs, radiating outward from the center (5 arms, 10 LEDs/arm). Say I connected all 5 arms/strands together in the center of the star, and then this center pointed were connected a controller. Would I be able to control the 1st LED (node) on EACH arm together (as channel 1-3), and the 2nd
  12. That's great CriagB--exactly what I was looking for! Pictures are definitely worth a thousand words!
  13. Great advice. I though all controllers had to be daisy-chained? If so, why would you home-run all CAT-5 to a single (central) location?
  14. I guess what I'm asking for, is if anyone actually has a good schematic of his/her specific house. I see tons of videos showing the final product, but I think it could be helpful to see the schematic, to learn how it all comes together. I did study the "typical setups" on the link above, but it's hard to get a sense of what a physical layout would look like. For example, you may have some controllers in the attic, some in the garage, and some in the yard. All daisy-chained, I guess? Single power cable to each controller? What features are daisy-chained (if any), vs what elements are go dire
  15. If you were building a new home, what are some of the "pre-wiring" elements that you would incorporate for these types of projects? What beyond a electrical outlet in the eves?
  • Create New...