Pixel controllers t...
 
Notifications
Clear all

Pixel controllers to Pi

11 Posts
7 Users
0 Reactions
4,793 Views
Posts: 326
Topic starter
(@jsheehan3)
Honorable Member
Joined: 17 years ago
[#40487]

After my first year with pixels I am not evaluating layout options.

This year all elements were cat 5 home runs back to router/switch co located with Pi.

After thinking about it, I believe I could effectively put a small cheap switch in the first elements enclosure tapping the local power supply for power then daily chain to one or more elements saving some long cat 5 runs.

Not sure if I would save money with the design or suffer performance but figured I'd ask for advice from the blinky flashy pixel gurus.

Sent from my iPhone using Tapatalk


10 Replies
Posts: 145
(@pstube731)
Estimable Member
Joined: 13 years ago

The words that sticks out in your post to me is "daisy chain" because with pixel controllers it's required to have a home run back to a switch or router that is being fed from your Pi. LOR uses the daisy chain wiring, as do renard boards I believe.
If you wanted to save cat5 runs, you could stick a Pi at each controller


Reply
Posts: 1076
 Zeph
(@zeph)
Noble Member
Joined: 15 years ago

I think you are talking about running one cat 5 ethernet cable from your show computer to the first enclosure, with an ethernet switch there feeding the enclosed controller as well as feeding several other controllers in a star configuration of more ethernet cables between the switch and other enclosures. Right? Rather than running every cable from the house to each individual controller.

Sounds fine if so. Only concern that comes to mind is multicast e1.31 if you are using that; I'm not certain if all cheap switches handle that well, but others here have a lot experience in that regard.

(We use Cat-5 for a lot of different things here: ethernet, RS-232/RS-485 Renard/DMX, pixelnet, pixel extenders, power, etc). You only reference one switch, which implies ethernet and the above topology. While that has two cables between your show computer and all but the first enclosure, we usually use "daisy chain" to refer to a longer chain of single in/out nodes, like Renards or DMX).


Reply
Posts: 326
Topic starter
(@jsheehan3)
Honorable Member
Joined: 17 years ago

Zeph - you got my concept. Put one switch close to pi then multiple cat 5 lines from switch out to key places in yard. From there I can branch from another switch to multiple elements

The switch should be agnostic to multicast vs unicast and should act like a low power amplifier to the signal but I will need to test.

As I said not sure about economics vs network topology/wiring simplification benefits just trying to figure out an alternative to a lot of long home runs.

I guess I could look at Komby wireless 1.31 as well.

Sent from my iPhone using Tapatalk


Reply
Posts: 1344
(@mrsmoofy)
Noble Member
Joined: 12 years ago
jsheehan3 wrote:Zeph - you got my concept. Put one switch close to pi then multiple cat 5 lines from switch out to key places in yard. From there I can branch from another switch to multiple elements

The switch should be agnostic to multicast vs unicast and should act like a low power amplifier to the signal but I will need to test.

As I said not sure about economics vs network topology/wiring simplification benefits just trying to figure out an alternative to a lot of long home runs.

I guess I could look at Komby wireless 1.31 as well.

Sent from my iPhone using Tapatalk

This works but like has been said if your using Multicast your switches will need to support Multicast most cheaper stuff does not so it might be easier as far as cat 5 runs you may loose any savings in the costs of the switches you will need.


Reply
Posts: 38
(@rtyfz450s)
Eminent Member
Joined: 11 years ago

From a network design perspective it is not optimal to daisy chain switches or hubs from your router or "core" switch. The best way of doing this is called a truck port. Switch to switch traffic from core to distribution switches. Each switch gets a trunk. The reason for this is not only bandwidth but multiple hops and broadcast domains. Ethernet does not work like an low voltage amp. You could get into a lot of detail here but basic principle is not to use Ethernet as you would power distribution. You are also creating a system with multiple points of failure that will take out not just one device but multiple devices down the line. Now since you are probably using consumer grade equipment and probably don't want to have your pi in the yard. I would suggest the following. Show network. switch or router near Pi with ports for you house light controllers. Single ethernet connection to yard. (Multiple lines not only waste money they create loops if not trunked they do not "double bandwidth" between switches) Switch in yard with individual Ethernet connection to each end point device. Do not daisy chain through this not only hurts you for multicast but creates issues with packet errors, collision, port saturation,delays which cause packet errors. The delay in packets might be small but think of it this way. You are sending a lot of small amounts of data out to all of your controllers refreshing constantly. If your data gets to the devices out of order ,guess what :your show will start to behave strange and you will be chasing down problems that you think are not related to your Ethernet network because you can ping /see all devices on your network. If you have spare switches laying around tested it out. Use a free program called wire shark. If you have a large amount of devices on your network you will see just how many packets are involved in controlling your lights. If you have not bought hardware I would suggest spending a little extra and getting some equipment with additional features. There is also a lot of used 10/100 products on the market as everything enterprise has gone to gigabit. You can get this stuff cheap.


Reply
Posts: 158
(@emmienlightfan)
Estimable Member
Joined: 11 years ago

This year I connected my Show PC, Pi (Pixel Arch Controller) and Pixlite4 directly to my router, but this year everything was quite close together.

Next year I will have E1.31 stuff spread around more and more controllers than I have ports on my router, so there will be at least 2 switches.
I will use only Gigabit switches and Unicast.

I have done testing with E1.31 on my home network, with stuff going through about 5 switches and I have had no problems.


Reply
Posts: 1076
 Zeph
(@zeph)
Noble Member
Joined: 15 years ago
rtyfz450s wrote:Show network. switch or router near Pi with ports for you house light controllers. Single ethernet connection to yard. (Multiple lines not only waste money they create loops if not trunked they do not "double bandwidth" between switches) Switch in yard with individual Ethernet connection to each end point device.

I think that is the core concept of OP's proposal: using a second switch in the yard and only one ethernet cable from the switch by the show computer to that outdoors switch, rather than running all ethernet cables to the house. So the topology is:


show computer ======= inside switch  ========(long)===========outside switch ========= controller
                                 \===== local controllers               \========= other controllers
                                                                         \======= and more

This is not what one usually considers a "daisy chain" with one in and one out for every node; in fact the outside switch is more like a star configuration. (A real daisy chain IS how Renard and DMX controllers work.)

But it does involve more than one switch in the path, at least for some controllers.

I think rtyfz450s is cautioning against adding yet a third switch (or fourth) in that chain, where the hybrid begins to take on a bit more of the dynamics of a "daisy chain" - many hops.

(Some people DO use something closer to a real "daisy chain" for ethernet with a small switch alongside each display controller, and all the controllers linked one after another. I haven't tried that and do not have an opinion, but rtyfz450s is clearly suggesting avoiding that. EmmienLightFan on the other hand is saying that he has tried 5 switches in a row.)

Again - if you are using multicast, test that your switch handles that correctly (with your controllers). A somewhat intelligent switch sometimes expects somewhat intelligent controllers, in terms of IGMP.


Reply
Posts: 326
Topic starter
(@jsheehan3)
Honorable Member
Joined: 17 years ago

You guys now have the concept I was going for. It saves me some home runs and wire management across the yard. Interesting concept is to put 2 switches from original - one to serve ground/yard elements, then another centrally on the roof to take care of all the eaves. Sounds like EmmienLightFan has tested the additional switch concept.

Sent from my iPhone using Tapatalk


Reply
Posts: 4092
(@skunberg)
Famed Member
Joined: 18 years ago
EmmienLightFan wrote:This year I connected my Show PC, Pi (Pixel Arch Controller) and Pixlite4 directly to my router, but this year everything was quite close together.

Next year I will have E1.31 stuff spread around more and more controllers than I have ports on my router, so there will be at least 2 switches.
I will use only Gigabit switches and Unicast.

I have done testing with E1.31 on my home network, with stuff going through about 5 switches and I have had no problems.

Are those 5 switches daisy chained then?


Reply
Page 1 / 2
Share: