- Solaro Series
- Licensing an unlicensed Xilica Solaro device
- Using the Xilica Solaro FR1/QR1 at 96k sample rate
- Factory resetting Solaro series devices
- Updating XC-SUB Firmware
- Understanding phantom power limitations with Xilica Solaro and Gio products
- Sourcing the original Solaro QR1 external DC power supply
- Understanding the Solaro QR1/QR1-UC fan and temperature readings
- Summing or mixing channels pre-AEC
- Performing a Solaro, Gio or Sonia firmware update
- Compatibility of PoE power delivery devices for Xilica products
- Monitoring and managing Solaro DSP device resource usage
- Loading a pre-designed template to a Xilica Solaro device
- Password Protecting a Solaro DSP
- Dante routes disappear after loading the Xilica design to devices
- Understanding Dante channels and Flows for Xilica hardware
- Loading a Project File design to device(s) and going live with a system
- Exporting system programming from Xilica hardware
- Programming a Xilica system's power-on state
- Enabling Dante audio IO for the Xilica FR1-D and Xilica QR1 DSPs
- Device status indicators for Xilica Gio Bluetooth
- Troubleshoot a boot-cycling/looping Solaro QR1/FR1
- Can I add Dante to an existing FR1?
- Xilica HearClear™ AEC parameters & specifications
- Sonia Series
- Xilica Gio/Sonia support for static Dante IP addressing
- Accessing EASE files for the Sonia C5 Speaker
- Factory resetting the Xilica Sonia Amp
- Daisy-chaining Sonia C5 Speakers
- Sonia Amp Loudspeaker Compatibility
- Sonia Amp Speaker Channel Indicators
- Troubleshooting no audio through Sonia Speakers
- Configuring Sonia Amp's Power Management Feature
- Maximum cable length between Sonia Amp and Sonia C5 loudspeakers
- Sonia Amp Power Output
- Managing and updating Xilica firmware
- Xilica API for third-party control of Solaro, Gio, Sonia, Neutrino & Uno devices
- Gio Series
- Xilica Gio/Sonia support for static Dante IP addressing
- Troubleshooting a USB audio connection to the Xilica USB card (XC-SUB) or Gio USB network endpoint
- Factory resetting Xilica Gio series devices
- Controlling the Xilica Gio series products with a third-party control system
- Programming third-party control of a Xilica system
- Controlling Xilica Gio devices from XTouch or a third-party control system
- Configuring Xilica Gio USB in the Designer software
- Configuring Xilica Gio XLR's Dante networked audio
- Configuring Xilica Gio USB's Dante networked audio
- Configuring Gio Bluetooth's Dante networked audio
- User Interfaces
- Factory resetting the Xilica Lucia push-button rotary encoder
- Handling TCP connection errors between a Xilica controller and a third-party device
- Controlling multiple parameters simultaneously with Xilica XTouch, Lucia or XWP
- Programming the Lucia wall panel controller
- Managing XTouch panel resolution
- Using Lucia’s Advanced Mode
- Xilica XT80 touch panel network adapter capabilities and limitations
- Creating radio-buttons on a Xilica XTouch control panel in Xilica Designer
- Navigating between pages on a Xilica XTouch control panel
- Software Downloads
- Customer Experience
- Download the latest version of Xilica Designer
- Mainboard BIOS firmware instructions and download for Xilica Solaro (FR1/QR1)
- Download the Xilica USB driver for mainboard and recovery firmware updates
- Download Xilica DLP/DCP/DSPX firmware
- Download Xilica Uno template files
- Download X Series (XP, XD, XA) firmware
- Resetting the password for an XSeries device
- Connecting to a Xilica system from a host computer on a different network segment
- Download the XLink software for Xilica DLP/DCP/DSPX devices
- Xilica end-of-life product listing
- Xilica X Series hardware & software management
- The Xilica Rio 1616N loses its Dante static IP address
- Xilica Neutrino, Uno, Rio Dante device names revert to default
- Release Notes for Designer 4.9
- Programming & Configuration
- Download the latest version of Xilica Designer
- Download the Xilica XConsole software for X Series devices
- Download-Project-Backup-File option is missing
- Handling a Dante system fatal error in Xilica Designer
- Gio Bluetooth configurable settings in Xilica Designer
- Creating and managing presets in the Xilica Designer software
- Setting up mute sync between a Xilica Solaro processor and a UC app such as Teams or Zoom
- Activating the Xilica HearClear™ AEC license for a Solaro FR1 or QR1
- Validating or troubleshooting third-party control commands to Xilica's API
- Ethernet networking best practices for Xilica products
- Integrating Aver® PTZ camera control with Xilica Solaro solutions
- Integrating Lumens® PTZ camera control with Xilica Solaro solutions
- Integrating the Shure® MXA920™ microphone with Xilica Solaro solutions
- Integrating the Sennheiser® TeamConnect Ceiling 2™ with Xilica Solaro solutions
- Release notes for Designer 4.8
- Handling a "signal loop" error in the Xilica Designer software
- Handling Network View error messages in the Xilica Designer software
- Download the Xilica API for third-party control of Solaro, Gio, Sonia, Neutrino & Uno devices
- Using multiple Sennheiser TeamConnect Ceiling 2 micophones with the Solaro QR1/QR1-UC
- Determining your host computer's IP address for Designer software communication
- Scheduling presets in a Solaro system for a specific time/date
- Managing, saving, and transferring Designer files (.pjxml & .sxml)
- Loading a pre-designed template to a Xilica Solaro device
- Exporting a blueprint of a system design from Xilica Designer software
- Configuring Xilica Gio XLR in the Designer software
- Configuring Xilica Dante networked audio
- Troubleshooting Dante in the Xilica Designer Software
- Xilica Designer software updates
- Control Panel update is required for continued operation warning
- Partitioning a Xilica Designer Project file
- Loading a Project File design to device(s) and going live with a system
- Handling a "Load Config" error in the Xilica Designer software
- Creating User-defined devices in Xilica Designer's Project View
- Preserving run-time parameter settings when exporting the Project File (.pjxml) from hardware
- Exporting system programming from Xilica hardware
- Exporting third-party control information from the Xilica Designer software
- Using the CueCore2 Lua driver in Xilica Designer for lighting control
- Password protecting a Solaro project file
- Xilica ACC-POE-95W PoE injector power and data specifications
- Lua Engine information and resources for third-party device driver creation in the Xilica Designer platform
- Understanding carriage returns for control of third-party devices from Xilica Designer
- Xilica Room Templates with Follow Me Auto Camera Preset Recall
Handling TCP connection errors between a Xilica controller and a third-party device
Back to User InterfacesIf a third-party device can be controlled by a single controller only (e.g. a native control app, Xilica Designer, or an XTouch controller), the secondary controller was either not mapped properly in the Designer software, or the issue is related to the number of simultaneous TCP connections allowed by the third-party device being controlled.
If your third-party device is controlled using TCP, then it's likely that it can be controlled by one source only. (Check the device's user manual for more information.) Connection to Xilica Designer will count as one connection. So after creating and loading the program it may be necessary to shut down Xilica Designer so that the ultimate end-user controller (e.g., XTouch Panel, XTouch App) is the only TCP connection.
For example, let's use a PJLink projector. If in the controller design, the user places a PJLink power button in the controller design schematic, the controller will automatically setup a TCP connection when the project is loaded.
If Xilica Designer has a PJLink projector in the project, when putting the project ONLINE, Xilica Designer will try to setup a TCP to PJLink projector too. If your third-party device allows only for a single TCP connection and you'd like to control it using an XTouch Control device, go online with the project and then exit the Xilica Designer desktop app. The XTouch Control device should now be able to control the third-party device without conflicts from other possible connections.