This document outlines the setup and configuration of a wireless network for ETC Eos Family Consoles to be used with iRFR or aRFR (WiFi Remotes) applications. It provides detailed instructions for integrating wireless equipment into existing or new lighting networks, preparing the console, and configuring the remote applications.

Function Description

The primary function of this setup is to enable wireless control of Eos Family Consoles using iRFR or aRFR applications on mobile devices (Android or iOS). These applications act as remote interfaces, allowing users to control lighting parameters and execute commands from various locations within a venue. The system relies on a dedicated wireless network to ensure reliable communication between the mobile devices and the console, specifically for lighting data. The document emphasizes the importance of an isolated network for lighting data to prevent interference and ensure show-critical information like sACN, EDMX, or ArtNet data is transmitted without interruption.

The core components of the wireless network typically include a wireless router or an access point. A wireless router functions as a local network operator, managing both wired and wireless connections and routing data between the local network and a wider area network (WAN). An access point, on the other hand, acts as a bridge, translating between wired and wireless devices, effectively placing all connected devices on the same network. The choice between a router and an access point depends on the existing network infrastructure and specific requirements.

The console itself plays a crucial role by providing the necessary network ports and, in some configurations, acting as a DHCP server to assign IP addresses to other devices on the network. The iRFR/aRFR applications on the mobile devices connect to this wireless network and communicate with the console using its IP address.

Usage Features

The setup guide provides several usage features, primarily focused on flexibility and reliability in network configuration:

Topology Options: The document offers various topology recommendations based on the existing system.
- Existing Network with a Router: This setup involves connecting the router's WAN port to a core switch in the lighting system. A small unmanaged switch is recommended between the console, wall port, and router to prevent the router from becoming a single point of failure for critical lighting data.
- Existing Network with an Access Point: Similar to the router setup, the access point connects to the core switch. Again, a small unmanaged 5-port switch is suggested if a direct switch port is unavailable, ensuring the access point is not in-line with show-critical data.
- Single Console with Dual Network Ports on an Existing Network: Newer Eos Family Consoles with dual network ports can dedicate one port for WiFi remote traffic, separating it from the main lighting network. This setup requires the DHCP service to be enabled on the second network port, with the router's WAN port or access point connected directly to the console. This is ideal for single-console systems or when only one WiFi remote is needed.
- Single Console with a Router or Access Point (No Existing Network): For systems that do not transmit lighting levels over the network, the router's WAN port or access point can be connected directly to the console after enabling the console's DHCP service.
Console Configuration: The guide details how to prepare the Eos Family Console for wireless remote operation:
- Finding the Console's IP Address: Instructions are provided for locating the IP address on different Eos software versions (v3.2.0 and greater, v3.1.5 and lower) by navigating through the console's display or browser to the Device Settings and Network tab.
- DHCP Service: It explains that one console or a Net3 Conductor appliance should be configured to act as a DHCP server, handing out IP addresses to other devices. Net3 Conductor is preferred, and for multiple consoles without a Net3 Conductor, the Primary console should be chosen.
- Enabling WiFi Remotes/Mobile Apps: The document outlines the steps to enable remote connections on the console. For Eos v3.2.0 and greater, users need to navigate to {Setup} -> {System Settings} -> {Mobile Apps} and enable {Allow App Connections}. For Eos v3.0.0 to 3.1.5, it's {Setup} -> {System Settings} -> {Remotes} and enable {Allow Remotes}. For older versions (v2.9.3 and lower), it's {Setup} -> {Device Settings} -> {Config} and enable {Visible to Remotes}.
- Configuring Network Port(s): For Eos v3.2.0 and lower, users must ensure that "Mobile Apps" is checked on the network port(s) connected to the wireless router or access point by navigating to {Displays} or {Browser} -> {Exit} -> {Settings} -> {Network Tab}.
Access Point/Router Configuration: Recommendations for configuring the wireless hardware include:
- Keeping the router's DHCP server enabled for local ports and wireless devices.
- Setting the WAN port to listen for a DHCP address (receive internet address automatically).
- Temporarily turning off wireless security features (like passphrases) during initial setup to simplify the process and remove variables. These can be re-enabled later.
- Disabling settings like "Broadcast Storm Detection" or "Block Multicast."
Connecting Wireless Devices: Simple steps are provided for connecting Android and iOS devices to the newly configured wireless network, similar to connecting to any other WiFi network, including entering a passphrase if enabled.
Configuring iRFR/aRFR Application:
- Opening the iRFR or aRFR app (sometimes listed as Mobile RFR).
- Verifying that the "Full Version" of the app is being used via the "about" tab. Preview versions will connect but lack live console control.
- Adding a new console connection by pressing the {+} icon in the "Connections" section.
- Entering a {Display Name} for the device.
- Inputting the console's IP address under {IP Address}.
- Selecting a {User ID} (Custom, Auto, or Console) to define how the app functions with user numbers.
- Hitting {Update} to save the connection.
- A successful connection is indicated by white text and a gold highlight.

Maintenance Features

The document includes a "Troubleshooting" section that serves as a maintenance feature, helping users diagnose and resolve common connection issues:

Console Display: If the console is shown with a WIFI symbol with a line through it, users should:
- Verify the console's IP address was entered correctly in the app.
- Confirm the mobile device is connected to the correct wireless network.
- Ensure the console, access point, or router are properly connected and powered on.
- Check the console's network port for activity lights, which indicate an active connection.

These troubleshooting steps guide users through verifying network settings and physical connections, which are crucial for maintaining a stable wireless control system. The emphasis on an isolated network for lighting data also contributes to long-term system stability and reduces the need for frequent troubleshooting related to network congestion or interference. The recommendation to temporarily disable wireless security during setup and re-enable it later is also a practical maintenance tip for initial configuration.

ETC EOS Series - Page 13

Table of Contents

Related product manuals