By Fasteddy Melbourne, Sydney, Brisbane Mini 2011 Click for next Slide

This presentation is a basic introduction to the E1.31 communication standard which also briefly explains the types of the controllers available and how it all goes together. 1.What is E1.31What is E What Is E1.31 used forWhat Is E1.31 used for 3.How Does E1.31 WorkHow Does E1.31 Work 4.Advantages of E1.31Advantages of E What Makes Up a E1.31 NetworkWhat Makes Up a E1.31 Network Single E1.31 Controller Multiple E1.31 Controllers 6.Types of E1.31 ControllersTypes of E1.31 Controllers 7.Topography of E1.31 & DMXTopography of E1.31 & DMX 8.Set Up RecommendationsSet Up Recommendations 9.E1.31 SoftwareE1.31 Software 10.ReferencesReferences

E1.31 is a communication protocol that is based on the DMX protocol standard E1.31 is a protocol for sending DMX512 data over Ethernet It is used to send commands to lighting and effects controllers. It was developed and published in May 2009 by ESTA (Entertainment Services & Technology Association) which in the beginning of 2011 became PLASA (Professional Lighting and Sound Association) E1.31 is expected to become the new standard for transporting DMX over IP (ethernet), replacing other lighting control protocols like Artnet and Shownet Click for next Slide

E1.31 is a network communication protocol used to talk from a computer running sequencing or effects software to a E1.31 supported controller/device for the control of lighting and effects. Click for next Slide

E1.31 uses IP addresses to communicate to controllers which is the same way our computers communicate on the internet. The E1.31 data packet is 542 bytes and is made up of: 512 bytes for channel data (1 channel per byte) 2 bytes for universe ID 1 byte for termination field 27 bytes for network and UDP overhead E1.31 device Show Computer Click for next Slide

E1.31 transmits data packets at around 40+ times per second E1.31 is a one way transmission, it only transmits to the controller. If a packet is lost or corrupted, 25 milliseconds later a new packet is sent to and received by the controller. Due to the human eye not detecting anything less than 60 milliseconds, E1.31 has inbuilt latency Once the data packets are received by the E1.31 controller the data packets are converted into commands for the control of various types of outputs. Standard CAT5 cables are used to communicate to the E1.31 controllers from your network card/RJ45 output from your computer. Click for next Slide

Based on the standard DMX512 protocol It does not require individual dongles for each universe like DMX It uses a common network topology to run and uses the ACN (Architecture for Control Networks) Protocol for communication. Can be easily distributed by using an inexpensive network switch Can allow over channel universes of data to be transmitted over one network (bandwidth and refresh rate considerations must be taken into account) Can be used with a shared internet connection Uses multicast for ease of setup.

Single E1.31 Controller Computer with Network/RJ45 output and E1.31 supported software CAT5 Network CableAn E1.31 Controller Click for next Slide

Multiple E1.31 Controllers Computer with Network/RJ45 output and E1.31 supported software CAT5 Network Cable E1.31 Controller Network Switch Click for next Slide

ECG-DR4ECG-DR4 – protocol bridge - E1.31 to 4 outputs of DMX512 or Renard This controller converts E1.31 data to 4 outputs of DMX and/or Renard. ECG-DMXRen8ECG-DMXRen8 – protocol bridge - E1.31 to 8 outputs of DMX512 or Renard This controller converts E1.31 data to 8 outputs of DMX and/or Renard. ECG-PIXAD8ECG-PIXAD8 – Pixel Controller – 8 outputs of SPI Data control This controller converts E1.31 data to 8 outputs of SPI data and supports 6801, 2801 and 1804 type pixels (to be released soon) Currently there are a few different E1.31 controllers available, with more to come in the near future Click for next Slide

SanDeviceS E680 SanDeviceS E680 – Pixel Controller – 16 outputs of SPI Data Control This controller converts E1.31 data to 16 outputs of SPI data and supports 6801, 2801, 1804 and GE type pixels (This is a DIY controller and requires assembly) Stellascapes E16 Stellascapes E16 – Pixel Controller – 16 outputs of SPI Data Control This controller converts E1.31 data to 16 outputs of SPI data and supports 2801 pixels Stellascapes E2 Stellascapes E2 – Pixel Controller – 2 outputs of SPI Data Control This controller converts E1.31 data to 2 outputs of SPI data and supports 2801 pixels There are also other types of E1.31 controllers under consideration, such as multi channel DC Controllers and servo controllers Click for next Slide

Click on diagram to open Link Click for next Slide This diagram shows the difference between a DMX universe, E1.31 universe and a Hyper DMX universe. Hyper DMX is a non standard communication protocol that was developed for the TP3244 controller running through a ECG-DR4. LOR controllers are able to be incorporated into a DMX universe by using an adaptor cable as shown in the diagram Note: Future availability of the TP3244 is currently unknown

Click for next Slide Use a separate network for E1.31 to reduce any bandwidth sharing with your home network/internet. You can still use E1.31 shared with your home network/internet but you may see performance issues. If sharing your connection with your home network/internet, then use a separate subnet address. Use 100 Mb/s or faster switches and network interface controllers (NIC). 10Mb/s can be used but the number of universes used may need to be considered. Wireless connections can be used, but data packets may be dropped or not arrive in the correct order When using many universes it may be advantageous to use unicast to limit data swamping the E1.31 controllers Note: Unicast is not officially supported by the E1.31 standard

Click for next Slide The community currently uses 3 main software packages for control of E1.31 controllers and devices. LightShow Pro Vixen Madrix Each software package has its advantages and disadvantages. You should download and review each software package before deciding on which suits you most.

Click for next Slide OpenDMX Wiki Plasa Standards DIYC E1.31 Thread ACL E1.31 WIKI Joshua 1 Systems (J1sys) Stellascapes SanDeviceS