User manual AMX DESIGN XPRESS HOME THEATER V1.3 ON SITE INSTALLER GUIDE

[. . . ] instruction manual Design XPress Home Theater version 1. 3 On-Site Installer's Guide So ftw are Software Warranty Agreement PRE-RELEASE CODE. Portions of the AMX Software may, from time to time, as identified in the AMX Software, include PRE-RELEASE CODE and such code may not be at the level of performance, compatibility and functionality of the final code. The PRERELEASE CODE may not operate correctly and may be substantially modified prior to final release or certain features may not be generally released. AMX warrants that the AMX Software will perform substantially in accordance with the accompanying written materials for a period of 30 days from the date of receipt. [. . . ] In some cases the IR file for new equipment may not have been captured or is not available for download from the AMX website. Or perhaps the IR file is available on the web but one or two codes were not captured in the right channels. In these cases it may be necessary for the installer to capture the IR codes or, at least, modify the IR file. When capturing or making changes the installer needs to know in which channel each IR code should reside. If the installer needs to capture an IR remote, or make changes to an IR file, the IR functions must be captured in the correct channels to work properly with DXP-HT. The DXP-HT Wizard lets you map the captured IR codes with a list of supported features. Refer to the DXP-HT Programmer's Guide for details. 10 DXP-HT v1. 3 - On-Site Installer's Guide On-Site Installer's Guide - Overview Common Mistakes The most common mistake made is modifying the software and then using the application to make changes. As mentioned before, all software changes outside of the special CUSTOM. AXI file will be overwritten. Only modify the source code generated by DXP-HT if there is a strong desire to alter the behavior of the code. Because of the scope and number of features designed into the system, the code can be quite daunting to someone looking at it, even an experienced NetLinx programmer. Installers with NetLinx experience should not expect to be able to modify the software the first time they see it. Most of the features are tied into another feature or affect another part of the software. The architecture of the system design and the function of the file being modified should be understood prior to proceeding with changes. Unless all devices are addressed as defined in the report file the system will not work as desired. DXP-HT v1. 3 - On-Site Installer's Guide 11 On-Site Installer's Guide - Overview 12 DXP-HT v1. 3 - On-Site Installer's Guide Understanding the Report File Understanding the Report File Overview The report file (report. html) automatically generated by Design XPress should be used as a step-bystep guide to installing the system. The report is broken down into the following five sections: Installation Instructions Device Addressing Wiring/Connections General Information AMX Recommended Equipment List Installation Instructions This section of the report indicates which files need to be downloaded, and describes device mapping, working with IR files, compile and download operations (via NetLinx Studio), how to FTP externally, and how to reboot the NetLinx master. Address each device as specified in the Device Addressing section of this report. Using an FTP program, FTP all . TXT files and . HTML files in the project directory to the root directory on the NetLinx Master. Device Addressing This section defines the device IDs of all the devices defined by DXP-HT. The devices listed in this section must be set to the given device IDs. This section is divided up by device type: touch panels and miscellaneous. Most devices will need to have their device IDs set using NetLinx Studio. Their device IDs must be set from the setup screen on the panel itself. [. . . ] Access the Device Addressing dialog by either one of these two methods: Right-click on any system device listed in the OnLine Tree tab of the Workspace and select Device Addressing (from the pop-up list). Enter both the Current and New Device address values for the target NetLinx device. Be sure to enter the new corrected device ID (as specified in the report file) in the Change To Device field. Make sure the Change To Device check box is selected and the Change To System check box is not selected. [. . . ]