![background image](http://html1.mh-extra.com/html/amx/epica-dgx-32/epica-dgx-32_instruction-manual_2938448116.webp)
Appendix B – Managing Configuration Files
110
Epica DGX 32 Instruction Manual
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 provided on the
AMX AutoPatch CD
shipped with each system.
Configuration file modifications include basic tasks, such as creating local presets and setting the control
panel password.
An Epica DGX 32 Distribution Matrix is configured either conventionally or automatically.
Conventional Configuration
An Epica DGX 32 system is conventionally configured when an .xcl configuration file (created in
XNConnect) is downloaded to the CPU before shipment (applies to some Epica DGX 32 systems).
When a system is conventionally configured, the .xcl file can be accessed for modification in one of two
ways: either use XNConnect to discover the .xcl file on the CPU or use XNConnect to open a copy of the
.xcl file. The .xcl file copy is provided on the
AMX AutoPatch CD
(MyXCL folder). In either case, after
the configuration is modified in XNConnect, it is loaded back onto the CPU (replacing the original file).
Automatic Configuration
An Epica DGX 32 system is automatically configured when the system generates its own configuration
based on the installed hardware (applies to most Epica DGX 32 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 an .xcl file does not exist for the system. Use XNConnect 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, it is loaded back onto the CPU
(replacing the automatically constructed configuration). If necessary, the automatically constructed
configuration can be restored (see page 119).
FIG. 49
Example of discovery information for conventionally configured .xcl file
FIG. 50
Example of discovery information for automatically constructed configuration
Discovery shows file name
for conventionally configured
.xcl configuration
When discovered, an automatically
constructed configuration does not
show a file name
Summary of Contents for Epica DGX 32
Page 6: ...Contents iv Epica DGX 32 Instruction Manual ...
Page 12: ...Notices 6 Epica DGX 32 Instruction Manual ...
Page 50: ...Installation and Setup 44 Epica DGX 32 Instruction Manual ...
Page 56: ...Epica DGX 32 SC Optical Boards 50 Epica DGX 32 Instruction Manual ...
Page 60: ...Epica DGX 32 DVI Boards 54 Epica DGX 32 Instruction Manual ...
Page 98: ...NXB AP 1000 Interface Initial Setup by Network Admin 92 Epica DGX 32 Instruction Manual ...
Page 102: ...NXB AP 1000 Interface Controlling the Epica DGX 32 96 Epica DGX 32 Instruction Manual ...
Page 108: ...NXB AP 1000 Interface Additional Info for Network Admin 102 Epica DGX 32 Instruction Manual ...
Page 114: ...Appendix A EDID Programmer 108 Epica DGX 32 Instruction Manual ...
Page 126: ...Appendix B Managing Configuration Files 120 Epica DGX 32 Instruction Manual ...