Networking Requirements for Eos v3.3.0+
Eos v3.3.0+ Networking Requirements
Systems in every discipline and at every level are getting more complicated. Eos and many of the show control and integrated tools users want now communicate on a network, and having a network which is designed for the real-time delivery of data, with aversion to risk and zero-to-little downtime, is a fundamental part of deploying successful lighting control systems. As such, we have done extensive research and development to provide comprehensive network requirements for Eos Family systems at multiple scales. These requirements document layouts and configurations for networks which support the types of communication utilized by Eos and common industry protocols like sACN. The goal is to provide users, specifiers, IT professionals, and other interested parties information on how to successfully deploy a network to support the work of a real-time lighting control system.
If users have systems that are installed and working, and they are only upgrading to Eos v3.3 and not changing the way they use their network, there is no need to replace it. But these requirements should be consulted if they will begin using new-to-them network-heavy features like Expansion Processing or show control, if they are designing a new system to be installed either on a new production or in a permanent venue, or if their current network is nearing due for a renovation. It is also known that networks have near-infinite configurations, and our documentation covers layouts and configurations which best serve the goal of near-real-time data transmission for lighting control protocols in a closed system. While other layouts or configurations may function, if there are issues, our support staff may request that users change or simplify the network so they can properly troubleshoot our products. If there are questions about best practices for networks, reference the Eos v3.3 manual and documentation.