Setting up Ethernet networks is becoming more and more a part of the stage lighting field as Ethernet based lighting equipment grows in popularity. This tech note attempts to provide some guidance for users encountering Ethernet as they expand and develop their Jands lighting systems.
Note these guidelines are applicable for the recommended case of an isolated network where Vista is the only controlling device. Particular requirements of systems including Wygaliser or other network intensive devices are not within the scope of this document, nor are networks that are shared with other non-lighting devices such as desktop computers, servers, printers, or a digital audio system.
Modern Ethernet networks use a ‘Star’ topology based around Ethernet ‘Routers’ or ‘Switches’, like that shown in Figure 1. If more ports are necessary the ‘Extended Star’ topology in Figure 2 is employed. Good quality name-brand unmanaged Ethernet switches generally provide more than adequate performance for most lighting systems, while their simplified no-configuration setup means they can be incorporated easily with little or no training.
Unmanaged switches do not include DHCP server functionality, so if they’re used all Ethernet devices must be configured with static IPs.
Ethernet routers can be used instead of switches if DHCP and/or WiFi is required, however over and above these features routers generally provide no benefit over switches of the same quality. If routers are used, the Internet connection port on the router should not be used. Additionally some routers include an ‘AP Isolation’ facility to isolate the LAN outputs – if available this feature must be disabled.
Only one DHCP server should ever be active in a system.
Ideally all switches will be 100Mbit or preferably Gigabit Ethernet, however if there are differences in performance between switches then the highest performance switch should be used for the main star point. Connect the main console and tracking backup directly to this switch. If an extended star network is planned, i.e. with 2 or more tiers, place the second level switches at a point physically close to the centre of the devices that will connect to it, and connect it directly to the switch at the main star point. Limit the network to 3 tiers.
There should be only ever single connections between Ethernet devices unless the literature for a device clearly states multiple connections are allowed. Equipment of this type is rare, however, and in general networks should never contain loops.
All network devices must have an IP address, and that address must be unique within the network. The actual assigned IP Address has no bearing on performance, nor changes the stature of that device in any way, so long as it is valid and unique in the network. IP addresses can be assigned to each device manually, or automatically from DHCP server – use of a DHCP server will ensure all addresses are unique and eliminate the need to keep records.
It is recommended that IP addresses be setup within one of the following ‘Private’ ranges:
Use a value for x between 0 and 255; it must be the same for all devices. Use a value for y between 1 and 254; it must be different for all devices. For example set the IP addresses in a network as follows:
Main console 192.168.10.1
Tracking backup console 192.168.10.2
Artnet box #1 192.168.10.10
Artnet box #2 192.168.10.11
Pathport Device 192.168.10.15
Media Server 192.168.10.20
Set the subnet mask on all machines to 255.255.255.0. If any machine has a default gateway field, set it to the same IP as the main console.
WiFi can provide a handy ability to control the lighting from the stage during the focus, however it can also provide easy access for a hacker to take control. It’s recommended that as an absolute minimum:
Additionally, where higher security is required:
Turn off the WiFi access point when it’s not needed.