AMX grants to Licensee the non-exclusive right to use the AMX Software in the manner described in this License. The AMX Software
is licensed, not sold. The AMX Software consists of generally available programming and development software, product
documentation, sample applications, tools and utilities, and miscellaneous technical information. Please refer to the README.TXT
file on the compact disc or download for further information regarding the components of the AMX Software. The AMX Software is
subject to restrictions on distribution described in this License Agreement. YOU MAY NOT LICENSE, RENT, OR LEASE THE AMX
SOFTWARE. You may not reverse engineer, decompile, or disassemble the AMX Software.
INTELLECTUAL PROPERTY.
The AMX Software is owned by AMX and is protected by United States copyright laws, patent laws, international treaty provisions,
and/or state of Texas trade secret laws. Licensee may make copies of the AMX Software solely for backup or archival purposes.
Licensee may not copy the written materials accompanying the AMX Software.
TERMINATION. AMX RESERVES THE RIGHT, IN ITS SOLE DISCRETION, TO TERMINATE THIS LICENSE FOR
ANY REASON AND UPON WRITTEN NOTICE TO LICENSEE.
In the event that AMX terminates this License, the Licensee shall return or destroy all originals and copies of the AMX Software to
AMX and certify in writing that all originals and copies have been returned or destroyed.
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 PRE-RELEASE CODE may not
operate correctly and may be substantially modified prior to final release or certain features may not be generally released. AMX is
not obligated to make or support any PRE-RELEASE CODE. ALL PRE-RELEASE CODE IS PROVIDED "AS IS" WITH NO
WARRANTIES.
LIMITED WARRANTY.
AMX warrants that the AMX Software will perform substantially in accordance with the accompanying written materials for a period of
ninety (90) days from the date of receipt. AMX DISCLAIMS ALL OTHER WARRANTIES, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE, WITH REGARD TO THE AMX SOFTWARE. THIS LIMITED WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS.
Any supplements or updates to the AMX SOFTWARE, including without limitation, any (if any) service packs or hot fixes provided to
you after the expiration of the ninety (90) day Limited Warranty period are not covered by any warranty or condition, express, implied
or statutory.
LICENSEE REMEDIES.
AMX's entire liability and your exclusive remedy shall be repair or replacement of the AMX Software that does not meet AMX's
Limited Warranty and which is returned to AMX. This Limited Warranty is void if failure of the AMX Software has resulted from
accident, abuse, or misapplication. Any replacement AMX Software will be warranted for the remainder of the original warranty period
or thirty (30) days, whichever is longer. Outside the United States, these remedies may not available.
NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL AMX BE LIABLE FOR ANY DAMAGES
WHATSOEVER (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS
INTERRUPTION, LOSS OF BUSINESS INFORMATION, OR ANY OTHER PECUNIARY LOSS) ARISING OUT OF THE USE OF OR
INABILITY TO USE THIS AMX SOFTWARE, EVEN IF AMX HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
BECAUSE SOME STATES/COUNTRIES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
U.S. GOVERNMENT RESTRICTED RIGHTS. The AMX Software is provided with RESTRICTED RIGHTS. Use, duplication, or
disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of The Rights in Technical Data and
Computer Software clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (2) of the Commercial Computer Software
Restricted Rights at 48 CFR 52.227-19, as applicable.
This Agreement replaces and supercedes all previous AMX Software License Agreements and is governed by the laws
of the State of Texas, and all disputes will be resolved in the courts in Collin County, Texas, USA. Should you have any
questions concerning this Agreement, or if you desire to contact AMX for any reason, please write: AMX Corporation,
Any XIVA protocol MP3 player can be used by specifying one of the supported XIVA
MP3 players, and physically connecting a different player (since the XIVA protocol is
the same across all devices that use it). In this case the name of the player will be
represented by DXP as the selected make and model MP3 player, as opposed to the
actual make/model of the connected MP3 player.
Receivers
DXP v1.5 supports any audio or video source equipment that uses IR.
User Interfaces
AMX Touch Panels
AMX DMS keypads
AMX SB2 keypads (for volume control only)
Doorphones
Generic
Techlon Instruments
Supported integration!Solutions Applications
i!-Weather
i!-TimeManager
i!-Schedule
4
Design XPress Installer’s Guide
Introduction
Related Documents
This document will not attempt to explain the architecture of the NetLinx software that is
automatically generated by Design XPress. That is left for another document and potentially
another audience. The related documents listed below are all available (as PDF files) on-line at
www.amx.com.
Related Documents
• Design XPress for NetLinx Studio Programmer’s
Guide
• Design XPress for NetLinx User Interface GuideProvides a detailed description of the Design XPress for
• NetLinx Studio Instruction ManualProvides a detailed description of the NetLinx Studio
• NetLinx Programming Language Reference Guide Provides a comprehensive listing of the commands that
AMX University offers several courses that teach basic and advanced NetLinx
programming and system design concepts. Contact AMX University, or refer to the
Training@AMX University page on AMX.COM for details and scheduling information.
Describes using the Design XPress application to design
Design XPress systems.
NetLinx Studio user-interface.
software application.
comprise the NetLinx Programming Language.
One Step at a Time
Design XPress is easiest to install if taken one step at a time. Because of the number of devices,
wiring connections and files, it can quickly become confusing, especially the first time one does an
installation. There are some common sense rules that apply, as in most installations:
Label every wire termination point.
This is critical. The wiring list that Design XPress generates is based on the location where the wire
terminates. For example, it will state that the DMS keypad in the kitchen should connect to port 4
on the microphone hub. Unless the cables are properly labeled it will take a time consuming search-
until-you-find-it approach to discover the proper cable. However, if the cables are labeled as they
are pulled this becomes a very simple exercise.
Don't get ahead of yourself.
Skipping steps in the installation process can cause problems in later steps. This will cost you more
installation time.
Use the auto-generated report file as your installation check list.
Design XPress generates a report file named report.html, which can be opened in any web browser.
It identifies each step in the installation process. Follow the steps in the report and installation
problems will be minimized.
esign XPress Installer’s Guide
5
Introduction
The Design XPress Application
The first step in defining the system is to run the Design XPress application. This Windows® based
wizard should probably be run in the office well in advance of going on-site. With this wizard you
define the locations of all equipment, the number of user interface devices, lighting scenes, audio
source equipment, etc. The Design XPress for NetLinx Studio Programmer’s Guide gives a good
overview of this application.
One note, however, related to the lighting addresses: Lighting addresses consist of a keypad address
and button. The keypad address is the address of the keypad for the lighting system being used, and
must be represented in the format for that lighting system.
Custom Modifications
There are limitations when creating a system using Design XPress. Design XPress systems can be
customized by adding programming to the "custom.axi" file included in the project, or by
modifying the user interfaces created.
For more information on adding custom modifications we recommend that you attend the AMX
programming classes. The course descriptions and schedules for these classes are available on the
AMX web site at www.amx.com.
Adding and Modifying Software
Each time the Design XPress application is run, it will generate the necessary software files. If
changes are made to any existing software file to modify behavior for job-specific items, the next
time Design XPress is run the changes will be overwritten.
One of the files created in the project by Design XPress is
CUSTOM.AXI. This file is provided
because all custom software changes made in this file will never be overwritten by the Design
XPress application. So, for example, if a home theater is added to a Design XPress-created system,
and those changes are made in
CUSTOM.AXI, any changes made down the road via the Design
XPress application will not affect the home theater code when the files are regenerated.
Sooner or later someone will make a change that gets overwritten so it is worth repeating to avoid
the resulting frustration: If you make changes to any file other than
CUSTOM.AXI you are taking it
upon yourself to not use the application for any further updates. Using the application will
overwrite your changes.
In a sense this is one of the nice features of Design XPress. Because all of the software is made
available, an installer who is a strong NetLinx programmer could use the Design XPress
application as a starting point. The resulting files could get most of the job complete. Not a bad
start! The installer could then go in and modify the software to be job specific and complete the job,
never intending to use the application again. Conversely, there will be installers who will use the
application to do almost all of the work relying on the
CUSTOM.AXI file for any small changes that
may be required.
Common Mistakes
The most common mistake made is modifying the software and then using the application to make
changes.
All software changes outside of the special
6
CUSTOM.AXI file will be overwritten.
Design XPress Installer’s Guide
Introduction
Only modify the source code generated by Design XPress if there is a strong desire to alter the
behavior of the code. To add features, new subsystems, etc. make the changes in the custom file to
save yourself the frustration.
Design XPress is not a "simple" NetLinx program. 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.
Another common mistake is forgetting to properly address a device. Unless all devices are
addressed as defined in the report file the system will not work as desired.
esign XPress Installer’s Guide
7
Introduction
8
Design XPress Installer’s Guide
Understanding the Report File
The report file (report.html) automatically generated by Design XPress should be used as a step-by-
step 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
Device Addressing
This section defines the device IDs of all the devices defined by Design XPress. The devices listed
in this section must be set to the given device IDs. If this is not done the system will not behave
properly. This section is divided up by device type: touch panels, DMS keypads, SB2 keypads, door
phones, amplifiers, and miscellaneous. The report will detail which room each device is in and
what its device ID must be set to. For example:
Keypad 1 is located in Kitchen, NetLinx address 10001:1:0
Most devices will need to have their device IDs set using NetLinx Studio. The exceptions to this are
the touch panels.
Understanding the Report File
For G3 panels, device IDs must be set from the setup screen on the panel itself. Make sure when the
device ID is set that the number of devices used on the touch panel is also set. Design XPress uses 4
devices on each touch panel. So, if the touch panel is set to use device ID 128 with 4 devices used,
that panel will actually occupy device IDs 128, 129, 130, and 131.
This does not apply to G4 panels, since their device address is set by the TPD4 file.
Wiring/Connections
This section details the locations where all of the cables will connect. It will define the connections
for all of the AMX equipment as well as the audio source equipment, IR ports, and any other
connection that must be made. Examples:
Touch Panel 1 (Study) is connected to video switcher output 1
Mom's CD is connected to NetLinx using IR port 2, IR pulse time 3/10 second
Tuner is connected to audio switcher input 1
DMS keypad 2 (Dining) connects to Mic Hub 1, PHASTlink Port 2
Mic Hub 1, line out 1 connects to audio switcher mono input 16L
Go through this section of the report one item at a time and perform each connection. Use this
section as a list of connections to make and check them off as you go.
General Information
This section of the report details the user interface file names for each touch panel and DMS
keypad, which files need to be transferred to the master, which group each audio zone is in, the
locations of each device, lighting scene addresses, file names of the generated NetLinx software,
etc.
esign XPress Installer’s Guide
9
Loading...
+ 29 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.