• Date
    craigblackley
  • Date
  • Replies 4 replies
  • Subscribers 139 subscribers
  • Views 5049 views
  • Users 0 members are here
Options
Related

Elements sharing a network

Due to a semi-knowledgable client, who designed his own system, but missed a few details, I have a problem to solve.

1 building with 2 theatres- dediucated Lighting network wiring all going to a patch bay, plugging into 1 switch.

1 Sensor 3 rack for Venue #1,  1 Drd Rack ( with PAradigm ) for Venue #2

1 Element console in each venue- the catch is that Element doesn't support multiple consoles on the same  network

We want:

- Element #1 to talk only to the Semsor rack, and network ports in Venue #1Element

-Element #2 to talk only to the Drd rack, and network ports in Venue #2

So my options appear to be ( but I'm not sure what is best ):

1) Set IP addresses so that Venue #1 devices and venue #2 devicesare in different ranges

2) Setup VLans on the switch

3) Install a 2nd switch

Any advice ?

Small side detail- the DMX B out from the Drd rack is going to DMX A in on the Sensor- so Paradigm button stations can control everything

Thanks

Craig Blackley

J.A. Frost Ltd.

 

Parents

  • The key question is whether there's any reason why they might want to allow control from one venue to another.  If the answer to that is "no" then your best bet is to either use separate physical switches or create isolated VLANs on the existing switch (both approaches are functionally equivalent).  That way no one has to worry about remembering what IP address range belongs to which space and all that.  This will also simplify things if they ever add Gateways to the system--especially if they're shared between spaces.

    Two Element consoles can't work together to control a system, but you can have two of them on the same network if, for some reason, they do want to share control between spaces.  It's just like how you can have a Paradigm processor and a console both transmitting sACN on the same network.  The receiving devices take whatever is at the highest priority, or do an HTP merge for devices at the same priority.  The problem with this arrangement is that there's no way to prevent someone from patching and controlling circuits in the space they're not supposed to be in.

Reply

  • The key question is whether there's any reason why they might want to allow control from one venue to another.  If the answer to that is "no" then your best bet is to either use separate physical switches or create isolated VLANs on the existing switch (both approaches are functionally equivalent).  That way no one has to worry about remembering what IP address range belongs to which space and all that.  This will also simplify things if they ever add Gateways to the system--especially if they're shared between spaces.

    Two Element consoles can't work together to control a system, but you can have two of them on the same network if, for some reason, they do want to share control between spaces.  It's just like how you can have a Paradigm processor and a console both transmitting sACN on the same network.  The receiving devices take whatever is at the highest priority, or do an HTP merge for devices at the same priority.  The problem with this arrangement is that there's no way to prevent someone from patching and controlling circuits in the space they're not supposed to be in.

Children
No Data

www.etcconnect.com