I apologize if not right forum, didn't see a newbie forum listed.
Did my first LOR controller this year and already planning out next years and would like to venture into pixels. Looking at initially doing some arches, some mini trees, and who knows what else.
Currently have 16 channel LOR AC controller and going to add to that for additional LEDs. I also plan to setup an e1.31 network (IT background, so the concepts just conceptually make more sense to me). Using LOR software, but keep hearing about xlights so maybe switch over to that once I get things physically setup.
Anyhow, have become obsessed with reading as much as I can on smart pixels, but all that is doing is leading to more questions.
General questions that will help clear up things for me...
1. I can daisy chain multiple pixel controllers to each other and the first would be connected back to my router/switch via cat5, correct? Each controller also connected to one another with cat5?
2. Is there some rule of thumb how far controllers can be from the pixel strings, etc? Does size of prop play a factor? (ie: want to place controller ~15-20ft away from arches so it is out of sight)
3. What wire is used to make an extended run from pixel to controller if not next to it?
4. Assuming daisy chain, each controller will be assigned a static IP on network and ID in my software? Then I would go ahead and be able to control the occupied channels on each controller from single sequencing software?
5. Assume daisy chain, is there a limit of number of controllers in a line? If so, based on what?
Thanks everyone in advance for your input!
Boy, these are loaded questions. Lot of opinions on the subjects.
1. Yes
2. I have gotten 80 feet, using cat5 cable, with my Falcon F16V3. Others can only push 20-25 feet. Plus, you can use a buffer/line driver out of the controller for a data boost. Falcon makes differential boards and receivers so you can pop out to 250 feet.
3. Cat 5, 18-22AWG 3 conductor of various sorts, thermostat wire, alarm wire, etc......... Lot of different types used by people.
4. Could be DHCP or Static, dependent on your controller and preference. Most choose static.
5. Couldn't say. My F16V3 can control 16,000 pixels, which is more than I will probably ever have. But, folks have used 5-6 and more.
1) Depends on the controller.. Some allow for daisy chains (aka 2 eth ports) and others do not. That said depending on your layout and controllers you could look at just using a raspberry pi and FPP (falcon pi player) to control the other controllers via wifi. This is nice when you have different elements in different spots and don't want to run power/data cables everywhere.
2) Again depends on the controller. Most controllers let you get 15-30ft from the controller to first pixel but millage can vary. (this is only to first pixel.. pixel to pixel max distance usually much shorter; like 10ft) The things you need to really watch is power drop on long runs and data degradation but if you make it to first pixel then the data at least gets refreshed.
3) Some folks like cat5 cable where they combine 2 wires to make a single positive lead and 2 wires to make a negative lead and then use another wire for data. I use 4-wire security camera cable. Pretty cheap and can do decently long runs without to much voltage drop.
4)Depends on how you sequence and what software runs the show. I use xlights and FPP and really neither care about the IPs of the controller. What really matters is which channels each controller uses. My sequencing software does not care what controller runs channels 300-600. I just need to make sure when I setup my controller that I say output two going to my house outline is channels 300-600 and such.
5) Never really daisy chained so not sure.
ccrowder wrote:1) Depends on the controller.. Some allow for daisy chains (aka 2 eth ports) and others do not. That said depending on your layout and controllers you could look at just using a raspberry pi and FPP (falcon pi player) to control the other controllers via wifi. This is nice when you have different elements in different spots and don't want to run power/data cables everywhere.
2) Again depends on the controller. Most controllers let you get 15-30ft from the controller to first pixel but millage can vary. (this is only to first pixel.. pixel to pixel max distance usually much shorter; like 10ft) The things you need to really watch is power drop on long runs and data degradation but if you make it to first pixel then the data at least gets refreshed.
3) Some folks like cat5 cable where they combine 2 wires to make a single positive lead and 2 wires to make a negative lead and then use another wire for data. I use 4-wire security camera cable. Pretty cheap and can do decently long runs without to much voltage drop.
4)Depends on how you sequence and what software runs the show. I use xlights and FPP and really neither care about the IPs of the controller. What really matters is which channels each controller uses. My sequencing software does not care what controller runs channels 300-600. I just need to make sure when I setup my controller that I say output two going to my house outline is channels 300-600 and such.
5) Never really daisy chained so not sure.
#3 - so I just solder (not sure if some connect is available) security wire (for example) to connection at end of pixel strip and use that to connect directly into channel of pixel controller? Depending on controller,could be 15-30ft away.
#4 - If i have controller A connected in line to controller B (controller A connected back to my switch), how can I control the occupied channels on each controller? Meaning, how does the system know which controller/channels, etc?
NEW QUESTION
* Just like using zip cord/vampire plugs for custom power runs for LEDs, do most people make their own Cat5 cables/connectors for runs between controller and switch?
Most folks solder pig tails to their pixels and make extension cords basically with pigtail ends. (such as https://www.aliexpress.com/store/product/10pcs-lot-3-Core-BLACK-Waterproof-pigtail-50cm-long-each-male-and-female-male-connector-s/701799_1495727183.html?spm=2114.12010615.0.0.374ccfcbaDqj6a )
Most controllers have a web interface you can access via their ip where you set what channels it should look for in the e.131 and what outputs it should use those channels for. For my controller it has 16 outputs. So I might have my garage pixels channels 1-264 (88 pixels each using 3 channels; ws2811) for output 1. I then say output 2 is 265-601 for my upper roof.. that sort of thing. Some controllers have an application you use on your computer to find them and set it up but most have gone to embedded web pages you configure on the controller itself via it's IP.
