Instruction manual

Appendix B – Managing Configuration Files
176
Instruction Manual – Enova DGX 8/16/32 Digital Media Switchers
XNConnect Overview
Caution: Unless you need to reload the .xcl configuration file or modify your system’s configuration
from the original specifications, you will not need to use XNConnect. We recommend making a copy
of the current file every time the file is modified.
XNConnect can be used to modify a system’s configuration information which contains routing and
control information. XNConnect is available at www.amx.com. Configuration file modifications include
basic tasks, such as creating local presets and setting the Control Panel password.
Most Enova DGX Switchers are configured automatically based on the hardware in the system; on
occasion custom systems are conventionally created per the user’s request.
Automatic Configuration
The configuration file for an Enova DGX Switcher is automatically generated based on its installed
hardware (applies to most Enova DGX single-enclosure systems). The configuration is constructed
internally with a standard virtual matrix (see previous page) by the CPU upon initial boot up of the
system.
When a system is automatically configured, the configuration information can be accessed for
modification in only one way since a configuration (.xcl) file does not exist for the system. XNConnect
can be used to discover the configuration information from the CPU. The discovered configuration
information can then be saved as an .xcl file. After the configuration is modified in XNConnect, the file
information is loaded back onto the CPU (replacing the automatically constructed configuration). If
necessary, the automatically constructed configuration can be restored (see page 185).
Conventional Configuration
When an .xcl configuration file is created and saved in XNConnect and then downloaded to the
switcher’s CPU before shipment, the file is considered to be conventionally configured (applies to some
custom Enova DGX systems).
When a system comes with a conventionally configured .xcl file, the file can be accessed for
modification in one of two ways. The first way (recommended) is to use XNConnect to discover the
.xcl file on the CPU. The second way is to request a copy of the conventional (.xcl) file from technical
support and then use XNConnect to open it. In either case, after the configuration has been modified in
XNConnect, the modified .xcl file can be loaded onto the CPU (replacing the original, conventionally
configured .xcl file).
FIG. 97 Example of discovery information for automatically constructed configuration
FIG. 98 Example of discovery information for conventionally configured .xcl file
When discovered, an automatically
constructed configuration does not
show a file name until after it has
been saved in XNConnect
Discovery shows file name
for conventionally configured
.xcl file