Control Server Tech Tips

SymVue Control Screens are a powerful and flexible option for system control. This Tech Tip explains how to export a control screen to a T-5 touchscreen, Control Server, and Windows PC.

This example is for a three-zone venue with six inputs. User controls should include microphone level control, background music selection and level control, zone volume control, and an indicator if the emergency system mute is engaged.

In this example, we will only need to create two control screens; one for the T-5 touchscreen and one that can be used for both Control Server and Windows PC. Once both control screens have been populated with controls and designed according to the available space, open the touchscreen control screen.

T-Series Export:

Right click in the background area and select Export to SymVue. Then select Touchscreens and click Next.

If there are more than one control screen intended for this configuration, this Panel Selection dialogue will allow you to select which screens should be included and referenced by this screen. When preferred selections are made (or if no other control screens are included), click Next.

Note: the “Home” control screen of a configuration is the one that is first exported through right-click > Export to SymVue.

Panel Security allows you to set a PIN code for the desired control screens. This PIN will be used for all selected control screens. Control screens in a given configuration may not have varying PINs.

Hardware Connection allows for two options of locating the T-5 touchscreen. Select which is most appropriate for the installation – in the vast majority of cases, Typical is the appropriate selection.

Export Options is the last step. Export to Touchscreens should automatically be checked. The drop down provides options to export this configuration to a specific T-5 or a group of touchscreens.

Note: We strongly suggest selecting “Go Online with Composer site file” to avoid control subscription errors which can be caused by the touchscreen and Composer/DSP not sync’ing parameters.

When ready, click Finish. This will export the configuration to the T-5 and push/update the archive on the DSP and go online.

Control Server / Windows PC Export:

Open the control screen for Control Server and Windows PC. Repeat the steps for T-5 touchscreen, making the appropriate selections for either. 

Once the configuration has been exported to Control Server, open up the Control Server’s WEB GUI and log into the Admin account. 

Double-click on the Control Server or right-click > open in Site View.

Once viewing the Status page, in the top right corner, go to Menu > Management > Applications and select SymVue from the App list. This will expand the available configurations list.

Click the down Arrow (or click and drag) on your control screen – this example “ControlScreen” – and click Save.

Then go to Menu > Management > Users. If you haven’t created a user account for the Control Server, you can do so here. Click on the user that will be accessing the exported configuration.

Click on the down arrow for the configuration that this user will access to place it into the User Allows Configurations and click Save.

This user now has access to this control screen.

Additional note; Configurations, Licenses, and Applications:
A configuration is any number of single control screens grouped/exported together that act as one “set” of pages or screens. You can have any number of available configurations (sets of control screens) loaded into the Control Server. The number of licensesavailable determines how many of those configurations are allowed to be available to users. You can have any number of users with varying access to any number of the available licensed configurations. Every Control Server comes with 5 licenses, but more can be purchased if necessary.

These control screens are used through the SymVue Application, which is the same medium we use for our export to touchscreen or Windows PC. The Event Scheduler and Mixer apps you may see in Control Server or on export are not related to these control screen configurations.

Selecting the Control Server networking mode is an important step in the device configuration process. Each mode may be the ideal choice for a given circumstance.

Control Server Networking Mode: Access Point (AP) Mode

In AP mode the Control Server is acting as its own WiFi Access Point “island.” With the Control Server and Radius connected over the network, configure the Control Server in AP Mode through its web interface. Any device with WiFi capability and a web browser can connect to the Control Server’s WiFi network through its SSID and password – just like any other WiFi network. An exported SymVue for Control Server control screen can be accessed from the smart device by visiting the Control Server’s IP address in a web browser. The Smart Device will not be able to connect directly to the DSP wirelessly.

Choose 1

AP Mode Notes:

• The Control Server and DSP can be connected directly or through a switch.
• The smart device must remain on the Control Server’s WiFi network to continue controlling the system.
• Control Server can allow control for any of our open-architecture DSPs.

Control Server Networking Mode: Client Mode

Choose 2

In this mode the Control Server is acting as an extension to an existing WiFi network. Meaning, the controlling device may connect to the existing network and still be able to control the system. With the Control Server and DSP connected over the network, configure the Control Server in Client Mode through the web interface.

In the Control Server web interface, scan for networks and connect it to the existing WiFi network on site with the SSID and password. Then connect the smart device to the same existing WiFi network. Any device with WiFi capability and a web browser can access an exported SymVue for Control Server control screen by visiting the Control Server’s IP address in a web browser – the IP address given to the Control Server by the existing Router/WAP. The smart device will not be able to connect directly to the DSP wirelessly.

Client Mode Notes:

• The Control Server and DSP can be connected directly or through a switch.
• The Smart Device must remain on the existing WiFi network to continue controlling the system.
• Control Server can allow control for any of our open-architecture DSPs.

This is a general-purpose step-by-step guide for connecting to Symetrix digital signal processors and related hardware with a PC.

Please note that Symetrix only recommends using Windows 10 and above. Other operating systems are not officially supported at this time.

See the bottom of this article for information on unsupported equipment and software.

Step 1 – Install the right software for the device

Symetrix design software is used to connect to Symetrix devices and is available to download, install, and run for free. The required software will depend on the devices that needs to be accessed:

COMPOSER PLATFORM:
Software can be downloaded here under the Composer tab.

• D100
• Radius and Radius NX series
• Prism series
• Edge
• Solus NX (note "NX", original Solus are not supported).
• T-Series touch panels
• W-Series wall remotes
• Control Server
• xControl
• xIO Bluetooth
• xIO XLR
• xIn / xOut 4 and 12
• xIO 4x4
• xIO Stage 4x4

Important: To avoid errors when going online with the hardware, please download the version of Composer that matches the DSP’s firmware revision number as closely as possible. This number can be found by cycling through the system pages on the front LCD panel of the DSP.

FIXED ARCHITECTURE PLATFORMS:

Software for Symetrix’s current Integrator Series (closed-architecture) DSPs can be downloaded here under the Jupiter and Zone Mix tabs. These include:

• Jupiter
• Zone Mix 761

Step 2 – Make sure the PC is on the right network

Once the correct software has been downloaded, the next step is to connect the PC to the device’s control network. If a DSP is Dante-enabled, make sure not to confuse the Dante port for the "control"/"ethernet" port. Configuration of these devices through the Symetrix software is always done through the control port.

By default, Symetrix devices are programmed to resolve an IP address automatically, either from a DHCP server or link-local (169.254.x.x) if there is no DHCP server found. Any devices with a front display will indicate their IP address on the front LCD panel. Some devices (T-Series and W-Series) may not show this information if they have been programmed. Cycling through the system pages on the front display of a Composer-based DSP will also display the subnet mask. If a device has previously been configured with a static IP address, it can be reset to DHCP by briefly pressing the device’s reset button, which is usually recessed in the housing on the back of the device.

Check your PC's network configuration by opening the Windows Command Prompt and entering "ipconfig". The relevant adapter's information will be shown along with any others available.

Important: Ensure that both the IP address scheme and subnet mask of the PC match that of the DSP. If setting the PC to a static IP address, it must be a different/unused IP address on the network. If connected directly to a DSP that has a known static IP address, setting the PC to any available IP address will work. If connected directly to a DSP that does not have a static IP address, the PC does not need to have a static link local IP address.

Step 3 – Locate the Symetrix hardware on the network and Pull

Once the PC is on the correct network, open the appropriate Symetrix software. The next steps will depend on the software being used.

COMPOSER:
Composer platform devices will show their location status via an indicator on the hardware module itself.

• Devices are located when there is a green check-mark in the location status indicator box.
• If this is empty, the device is not located.
• If the check-mark is yellow, the device is located and its outputs may be muted for some reason.

Go to Hardware > System Manager from a blank/new Composer site file to search the network for available hardware.

In the Hardware or Control Network tab (depending on the version of Composer) find the appropriate DSP, highlight it, and select Go Online (Pull from Unit).

Note: ensure Composer is using the correct NIC to search the network.

Confirm the file name and save location for the site file - Desktop is a good location, but anywhere that OneDrive or other cloud services don't access is recommended for later permissions and access reasons.

Confirm the prompt that the site file will be pulled from the unit at the given IP address.

In the large majority of cases, synchronizing the site file on pull is the advisable option. This will pull the current running configuration of all volumes, mutes, routing, etc. - what's running live right now.

On completion, Composer will notify of Online status with both a dialog and the Online status indicator in the left panel.

FIXED ARCHITECTURE PLATFORMS:

Fixed architecture platforms (Jupiter and Zone Mix 761) will use their own software respectively and have a Connection Wizard to complete location and go online.

When initially opening the software and connecting to a device select Existing App File on Device to initiate the Pulling process of location and going online.

Depending on the connection, select either Direct or Indirect.

• Use Direct if connecting the PC directly cabled to the DSP.
• Use Indirect if using a switch or small network of switches.
• Network is the least common choice and is usually meant for larger networks that involve routing/gateway or subnet jumps (unrecommended).

Select the appropriate PC NIC for the connection, if there are multiple available. Wifi should never be used to connect to Symetrix DSPs - always cable to the network or the DSP directly.

Once a network is selected, the software may warn that it may not be able to connect. This is fairly common and can be clicked Yes through to continue.

If the PC/software can see the given DSPs on the network, they will be shown here. Select the appropriate one and click Next.

Finalize the Go Online process and the software will attempt to pull the programming and go live.

Depending on the software, the main GUI will appear and the "Online" indicator will be present.

Troubleshooting

If you have followed the above steps and are having difficulty locating any devices on the network, we have a location troubleshooting guide available here.

If you are able to locate devices, but are receiving warnings from the software about failures to go online:

• Disable Windows Defender Firewall and any third-party antivirus/firewall programs that may be blocking network traffic.
• Double check that the device firmware versions for all devices in the site file match the version of Composer being used (the first two numbers are most important).
• Power cycle both the PC and the device(s).
• If the device is connected to the PC through a network switch, try connecting directly instead.
• If a (Composer) device cannot be located and is not currently needed in the site file, right click it and select ‘Disable Unit’, then Push online (this will cut audio for the duration of the Push).
• If a specific error code is being presented, please contact Technical Support at support@symetrix.co.

UNSUPPORTED EQUIPMENT

As of January 2024, Symetrix no longer supports the Designer platform, nor any equipment/software released before the Composer platform. This includes, but is not limited to: 

Designer platform: 

• 8x8 DSP 
• BreakIn & BreakOut 12 
• CobraLink 
• Control I/O 
• Express series 
• Solus series (not NX) 
• ARC-2, ARC-SW4, ARC-K1, ARC-SWK, ARC-Mic/XLR (Note these units do not have "e" at the end while current ARC remotes do.) 

Legacy platforms: 

• 200 series 
• 300 series 
• 400 series 
• 500 series 
• 600 series 
• Lucid 
• AirTools 
• Deuce 
• AutoMix Matrix
• Zone Mix 760
• Zone Mix 780

Please contact Technical Support for an archived copy of the Designer software. Other resources may be found online via search engine, message board, or others. We also have a couple of authorized third-party service centers familiar with our legacy equipment and may be able to provide further assistance. Please reach out to:  

Condor Electronics    
10007 Aurora Ave N    
Seattle WA 98133    
Phone: 206-633-5190    
Email: info@condor-electronics.com  

Advanced Musical Electronics    
8665 Venice Blvd.    
West Los Angeles, CA 90034    
Phone: 310-559-3157    
E-mail: mail@advancedmusical.com  

Any resources, materials, costs, or support for discontinued Symetrix equipment are set solely by these service centers and are not dictated by Symetrix. Symetrix highly recommends upgrading installations with unsupported our outdated equipment to current technology. Please talk to your Regional Sales Manager or Dealer, or locate one through our website per your region here.

This article contains information and guidelines related to controlling Symetrix and third-party products using IP, Dante, serial, and other technologies.

IP Control Network Guidelines

• The maximum number of connected IP devices is 128. This includes DSPs, W Series, and T Series controllers.
• Up to six TCP sessions can be active at one time.
  • If a seventh TCP/IP connection is initiated, the least recently used session will be automatically closed. Control systems should avoid closing and re-opening TCP connections if possible.  Keeping a single TCP session open to send multiple commands through will result in much better performance than opening and closing a session for each command.
• To control Symetrix DSPs with Ethernet:
  • Command strings are sent as the payload of a UDP/IP or a TCP packet. The following rules should be observed in sending commands:
    • Commands should be sent to UDP or TCP port number 48631 to the unit’s IP address. The IP address may be found using the Connection Wizard or on some units’ front panel displays.
    • Commands should be formatted exactly as defined in the Composer help file and include a carriage return that terminates the command.
    • Command strings may or may not include a zero-termination character.
    • Commands should not be broken up across multiple packets.
    • If high-reliability communications are required, responses to commands should be analyzed for success.

Control of Third-Party Devices via the Dante Control Network

Supported Third-Party Dante Device Limitations

• The number of Dante devices (except Shure – see below) that can be located by or referenced by (switch input and LED output use) from a single DSP unit is limited to 24.
• The number of Shure devices that can be located by or referenced by (switch input and LED output use) a single DSP unit is limited to 4.

Control Methods

TCP/UDP/HTTP Control

Third-party devices that are controlled by TCP or UDP strings or binary code can be controlled from a Symetrix DSP either by using a Network String Module available in the Composer toolkit or by the use of an Intelligent module. If bidirectional communications or control using HTTP is needed, then an Intelligent module is required.

IR Control

Symetrix has tested and verified that the Global Cache IP2IP/IP2IR and their other IR interfaces work with Symetrix products. Communicate using binary Mode to Global Cache units. Text does not work.

Serial Control

Radius and Edge have a single serial port. If using a DSP without a serial port or if additional serial ports are needed, use an xControl or Global Cache IP2LS/IP2SL-P/WF2SL.

Contact Closure or Voltage Control

Included natively in Symetrix DSPs. If more connections are needed than provided with the DSP add xControl Control Expanders. In addition to analog/logic control inputs/logic outputs, the xControl also adds two additional serial ports.

Control Server

The Wi-Fi access point built into the Control Server only passes data to the Symetrix control network. It cannot be used to access another network.

ARC Controls

Power Limitations

The total number of ARCs that can be daisy-chained and fed power from an ARC port may be limited depending on ARC type and cable distances. An ARC-PSe Rack Mount Power Supply may be used to accommodate a larger number of ARC Wall Panels.