CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
Software License and Warranty Agreement
LICENSE GRANT.
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. This license does not grant Licensee the right to create derivative works of the AMX Software. 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.
LICENSEE MAY NOT SUBLICENSE, RENT, OR LEASE THE AMX SOFTWARE. Licensee 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 LICENSEE SPECIFIC LEGAL RIGHTS. Any supplements or updates to the AMX
SOFTWARE, including without limitation, any (if any) service packs or hot fixes provided to Licensee 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 Licensee's 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 LICENSEE.
SOFTWARE AND OTHER MATERIALS FROM AMX.COM MAY BE SUBJECT TO EXPORT CONTROL.
The United States Export Control laws prohibit the export of certain technical data and software to certain territories. No software from this Site
may be downloaded or exported (i) into (or to a national or resident of) Cuba, Iraq, Libya, North Korea, Iran, Syria, or any other country to
which the United States has embargoed goods; or (ii) anyone on the United States Treasury Department's list of Specially Designated Nationals or the U.S. Commerce Department's Table of Deny Orders. AMX does not authorize the downloading or exporting of any software or technical data from this site to any jurisdiction prohibited by the United States Export Laws.
This Agreement replaces and supersedes 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. For any questions concerning this Agreement, or to contact AMX
for any reason, please write: AMX, 3000 Research Drive, Richardson, TX 75082.
Appendix F: The InConcert Resource Center .................................................225
InConcert Resource Center - Partner List.............................................................. 225
InConcert Resource Center - Search Devices ........................................................ 225
InConcert Resource Center - Search Remote Controls.......................................... 226
InConcert Resource Center - Search New Releases .............................................. 226
InConcert Resource Center - Voting / Request ..................................................... 227
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
ix
Table of Contents
x
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
V
VisualArchitect v1.1 Overview
Visual Architect (VA) by AMX is the first product of its kind that allows you to design a fully functional
single-master NetLinx control system, complete with customizable touch panel graphics and macro
support, without having to write even a single line of code.
For experienced NetLinx programmers and system designers, VA can serve as a powerful tool, greatly
reducing the amount of time required to design and complete single-master NetLinx systems. The Touch
Panel Template support in VA makes it easy to create attractive touch panel page designs, and the
CodeBuilder feature helps to define macros with ease and speed.
Go to www.amx.com/va to view and download the latest VA-specific marketing, training and technical
material. Also, take a few moments to familiarize yourself with the elements of the VA Workspace, and
the elements of the help file. When you're ready to begin, select an option under Start a New Project, on
the Welcome To Visual Architect window:
Basic System Assistant
System Design Library
New Empty System
Refer to the Getting Started topic for details.
VisualArchitect v1.1 Overview
Supported Windows Platforms and PC Requirements
Supported Operating Systems:
Windows XP® Professional (service pack 2 or greater)
Windows 2000® (service pack 3 or greater)
You must have Power User (or Administrator) rights to install and run all required
System files.
Supported System Languages:
English (US)
French
Spanish
German
Russian
PC Requirements/Recommendations:
Pentium 750MHZ processor (minimum requirement); 1.5Gh or faster recommended.
150 MB of free disk space (minimum requirement); 300 MB or more recommended.
256 MB of installed memory (RAM), 512MB or more recommended.
Minimum (VGA) screen resolution of 800x600.
Windows-compatible mouse (or other pointing device).
If the mouse wheel on your Microsoft® IntelliMouse® doesn't work with VA, try
downloading the latest IntelliMouse drivers from Microsoft.
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
1
VisualArchitect v1.1 Overview
The VisualArchitect Workspace
Take a few moments to familiarize yourself with the elements of the VA Workspace (FIG. 1), and the
elements of the VA online help file.
FIG. 1 The VisualArchitect Workspace
Welcome Screen
When you launch VisualArchitect, the Welcome Screen is displayed. The Welcome Screen is divided
into three main sections, each containing a set of shortcuts:
The Welcome screen is also displayed any time there is not a Project open.
Start a New Project
This section contains two shortcuts relating to creating a new VA project:
Basic System Assistant: Click to access the Basic System Assistant dialog. Use the Basic
System Assistant to quickly specify a Central Controller, Touch Panel and up to two Keypads.
This option is the same as selecting File > New > Basic System Assistant.
System Design Library: System Design Library files (SDLs) represent pre-configured VA
Project/Systems designed to accommodate various installation types. SDLs are available for
Dealers to download from www.amx.com (in the Markets section).Select a SDL that most
closely meets the needs of your customer, keeping in mind that you will have the ability to
customize the solution later by adding different devices and options.
New Empty System: Click to open a new System tab, with a NI-3000 Central Controller. This
is the default Central Controller for new VA projects, and it can be switched to a different
2
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
VisualArchitect v1.1 Overview
V
Central Controller at any time. This option is the same as selecting File > New > New Empty
System (or the New Empty System button on the Standard Toolbar).
Open a Recent Project
This section contains a list of recently opened VA Projects, for quick access. Click on any project in the
list to open it.
Browse for a project: Click to open the Open VisualArchitect Project dialog, where you can
locate and select projects that are not listed in the recent projects list.
Managers
This sections contains shortcuts to the two managers used by VA:
Device Database Manager: Click to access the Device Database Manager dialog, where you
can specify the location of the device database that you want to use for your VA project(s).
The Device Database is essentially a collection of Cafe Duet module files (*.JAR). Each JAR
file represents a controlled device that can be added to the project as a third-party device, via
the Devices tab of the Toolbox.
By default, the Device Database is installed to the same directory as VA, but you may
need to change the location if you create your own device database(s).
If you add new JAR files to the Device Database, you'll have to update the database via
the Update button in the Device Database Manager.
Touch Panel Template Manager: Click to access the Touch Panel Template Manager dialog,
where you can preview, load and install ready-made templates that can be applied to the
Touch Panels in your project.
System Tree
There are two main elements of the System Tree window (FIG. 2):
FIG. 2 System Tree window
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
3
VisualArchitect v1.1 Overview
Device List
The upper portion of the window is the Device List, indicating the devices that are currently in your
system, separated into two categories:
Control Equipment - This represents AMX equipment, including Central Controllers,
Devices - This represents third-party (non-AMX, controlled) equipment.
FIG. 3 Un-check the checkbox next to any device to remove its element from the Touch Panel UI diagram
Expansion, Networking, Touch Panels and Keypad devices).
Beyond providing a visual summary of the devices in your system, the System Tree also
provides shortcuts to many device-oriented functions of VA, via the System Tree context
menu. Right-click on any device in the Device Tree to access this menu.
If you are in a Navigation diagram (Touch Panel UI tabs), the Controlled third-party
device list has an additional feature: Un-check the checkbox next to any device in the list
to remove its element from the Touch Panel UI diagram (FIG. 3). This does not remove
the device from the system, just temporarily removes it from the diagram.
System Tree context menu
The System Tree context menu provides shortcuts to many device-oriented functions of VA.
Right-click on any device in the Device Tree to access this menu:
• Connection ManagerOpens the Connection Manager dialog, where you can view/edit
• CodeBuilderOpens the Code Builder dialog, where you can add scheduled
• DeleteRemoves the selected device from the system.
• IR CaptureOpens the Capture IR Codes dialog, where you can assign IR codes
• Control String DefinitionOpens the Control Strings Definition dialog, where you can assign
• Sort AlphabeticallySorts the devices in the Device Tree alphabetically. This is the
• Sort by CategoryClick to sort the devices in the Device Tree by category.
connection settings for the selected device.
events and other custom programming to your system (all without
writing any actual NetLinx code).
to IR-controlled system devices.
control strings to Serial-controlled system devices.
default setting.
AMX Device categories include:
Central Controllers
Expansion devices
Networking devices
Touch Panels
Keypads
The Devices category represents third-party (non-AMX) controlled
devices in the system.
4
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
VisualArchitect v1.1 Overview
V
Properties Window
The lower portion of the System Tree is the Properties Window (FIG. 4). The Properties Window
provides detailed information for any device or navigation element selected in the Diagram Area.
FIG. 4 Properties Window
The Properties Window is context sensitive:
When a Device Element is selected in the System diagram, it provides detailed information
for that device.
When a Template Element is selected in a Navigation diagram, it provides information
relative to the selected element.
When a Keypad button is selected in a Keypad diagram, it provides information relative to
the selected button.
If a Keypad is selected in the System Diagram, the Properties window represents the
device-level properties for that keypad only, but if the Keypad's UI tab is opened, the
Properties window indicates button-level properties (in addition to device-level
properties).
The rows displayed this table will vary depending on the nature of the selected device or element.
Diagram Area
The Diagram Area is the large area in the middle of the application window, where you will view
representations of every device in your system, as well as all device connections and Navigation layouts
for User-Interface (UI) devices.
Note that the example above indicates several tabs across the top of the Diagram Area window:
System Tab - The System tab displays the System Diagram which gives a visual
representation of the devices in the system and their connections to each other and to the
Central Controller. When you start a new system, the program automatically adds a NI-3000
NetLinx Central Controller. At this point, only the System tab is represented. Since every
system must have a single NetLinx Central Controller, there will always be a single System
tab. Use the System tab to add and remove devices from the system, and establish connections
between the devices.
UI Tab(s) - A separate UI tab is added for each User-Interface device added to the system.
Use these tabs to design the navigation layout for each of the UI devices.
For each Touch Panel in the system, there is a Touch Panel UI tab, which displays
the Touch Panel UI Diagram for each panel.
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
5
VisualArchitect v1.1 Overview
FIG. 5 Diagram Area
For each Keypad in the system, there is a Keypad UI tab, which displays the
Keypad Diagram for each keypad.
The navigation that is established here will be reflected in the resulting Touch Panel and Keypad
templates generated by VA.
System Tab (System Diagram)
The System diagram is the graphic representation of the various devices in the control system, and their
connection to the NetLinx Central Controller. The System diagram is displayed in the System tab
(FIG. 6).
FIG. 6 System Tab (With Example System Diagram)
Devices
Each device is represented in the System diagram by a Device Element. To add devices to the system,
simply select each device in the Toolbox, and drag-and-drop into the System diagram.
Refer to the Adding Devices to the System section on page 49 for details.
6
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
VisualArchitect v1.1 Overview
V
Device Connections
Each device must be connected to the NetLinx Central Controller, either directly or via an intermediate
Networking or Expansion device, as indicated by the connection lines.
Refer to the Connecting Devices section on page 61 for details.
Right-click anywhere within the System diagram to access the System Diagram
context menu.
UI Tabs
There are two types of User-Interface (UI) tabs displayed in the Diagram Area, depending on the type of
UI devices present in the System diagram:
Touch Panel UI tabs - For every Touch Panel in the System diagram, there is a separate
Touch Panel UI tab with a Touch Panel UI diagram for that panel.
Keypad UI tabs - For every Keypad in the System diagram, there is a separate Keypad UI tab
with a Keypad diagram for that keypad.
The UI tabs provide a graphical representation of how the user will navigate the UI to access devices in
the system.
Touch Panel UI Diagram
For every Touch Panel added to the system, a separate Touch Panel UI tab is added to the Diagram Area.
Each Touch Panel UI tab consists of a Touch Panel UI Diagram - the graphic representation of the
elements in the touch panel GUI, and their navigation layout (FIG. 7).
FIG. 7 Touch Panel UI diagram
This is where you can add and connect UI Elements to establish a flow from one area of the UI
to another.
The selected element’s properties are displayed in the Properties window.
Refer to the Defining Touch Panel Navigation section on page 101 for details.
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
7
VisualArchitect v1.1 Overview
Keypad UI Diagram
For every Keypad added to the system, a separate Keypad UI tab is added to the Diagram Area. Each
Keypad UI tab consists of a Keypad UI Diagram - the graphic representation of the button layout on the
selected keypad (FIG. 8).
FIG. 8 Keypad diagram
The button layout for each keypad is based on the type of keypad selected:
For Keypads that do not feature an LCD display, the UI consists channel codes assigned to each button
on the keypad that allow the end-user to select devices to control, and trigger various control functions
on each device.
For Keypads that do feature an LCD display, the UI also includes items displayed on the LCD display.
These include the Mio Modero Elite SL, Elite DL and Attache.
Click on any button on the Keypad diagram to select it for editing. You can add, edit and view
The selected button's properties are displayed in the Properties window
Refer to the Defining Keypad UI Navigation section on page 122 for details.
button layout, menu actions, button label text and assign channel codes on each button.
Remote UI Diagram
For every Remote added to the system, a separate Remote UI tab is added to the Diagram Area. Each
Remote UI tab consists of a Remote UI Diagram - the graphic representation of the button layout on the
selected remote. An example Remote UI diagram is shown below (FIG. 9).
Click on any button on the Remote UI diagram to select it for editing. The selected button's properties
are displayed in the Properties window.
FIG. 9 Remote UI diagram
Refer to the Defining Remote Control Button Properties section on page 129 for details.
8
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
VisualArchitect v1.1 Overview
V
Toolbox
The Toolbox in VA is dual-purpose:
If you are in the System tab of the Diagram Area, the Toolbox provides thumbnail images of
the devices that you can add to your system. In this scenario, use the Toolbox to select AMX
hardware and third-party devices to add to the system.
Refer to the Adding Devices to the System section on page 49 for details.
If you are in a UI tab of the Diagram Area, the toolbox provides access to all elements
available within the template selected for this touch panel. In this scenario, use the Toolbox to
select template elements to incorporate in your panel navigation layout.
Refer to the Defining Touch Panel Navigation section on page 101 for details.
Toolbox - System Devices
If you are in the System tab of the Diagram Area, the Toolbox provides thumbnail images of the devices
that you can add to your system (FIG. 10). In this scenario, use the Toolbox to select AMX hardware and
third-party devices to add to the system. The Toolbox provides thumbnail images of the devices that you
can add to your system for easy identification.
FIG. 10 Toolbox - System Devices
Click on the tabs to view the different categories of devices.
AMX Device categories include: Central Controllers, Expansion devices, Networking devices, Touch
Panels, Keypads. The Devices category represents third-party (non-AMX) controlled devices in the
system.
To view details on any AMX device, simply mouse-over the thumbnail.
To view a listing of third-party devices that can be added to the system, click on the Devices
tab.
Right-click on any device thumbnail to access the Toolbox System Devices context menu.
To add a device to the system, simply click and drag it into the System tab of the Diagram
Area.
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
9
VisualArchitect v1.1 Overview
Select View > Toolbox to access the Toolbox sub-menu, where you can select to hide and
Right-click on any device thumbnail to access the Toolbox System Devices context menu.
By default, all available device types are shown. De-select any item in the Toolbox sub-menu to prevent
that device type from being displayed in the Toolbox.
VA uses a device database to populate the list of module-supported devices
(displayed in the Devices tab of the Toolbox). The device database is installed as part
of the VA installation routine. However, the device database can be updated via
options in the Device Database Manager dialog. In order for a device to be available
for inclusion in your projects, it must be represented in the device database.
There are several devices indicated in the database when VA is installed, and there are many more that
can be downloaded from the InConcert Resource Center (on www.amx.com) and added to the database.
Toolbox - Touch Panel Navigation
If you are in a Touch Panel UI tab of the Diagram Area, the toolbox provides access to all elements
available within the Template selected for this touch panel. In this scenario, use the Toolbox to select
template elements to incorporate in your panel navigation layout (FIG. 11).
show the AMX hardware and third-party device types that can be added to the system.
10
FIG. 11 Toolbox - Touch Panel Navigation
You must select a template for the panel (via the Template option in the Device Properties
window) to populate the tabs in the Toolbox with template elements.
You must install at least one template (via the Touch Panel Template Manager dialog) to have
a template available to apply to your panel(s).
To add a template element from the Toolbox to a Navigation diagram, simply click and drag it
into a Touch Panel UI tab of the Diagram Area.
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
VisualArchitect v1.1 Overview
V
Select View > Toolbox to access the Toolbox sub-menu, where you can select to hide and
show the various types of template elements that can be used in the panel Touch Panel UI
diagram.
Right-click on any template element to access the Toolbox User Interface context menu.
By default, all available elements are shown. De-select any item in the Toolbox sub-menu to prevent that
element type from being displayed in the Toolbox.
Toolbox - Devices tab
The Devices tab of the Toolbox displays a listing of all device types supported by VisualArchitect
(FIG. 12).
FIG. 12 Toolbox - Devices tab
Each device type is represented with a separate folder.
Click the plus sign next to any Device Type folder to display a listing of supported
Manufacturers for that device type.
Click the plus sign next to any Manufacturer folder to further expand the view to show the
supported Devices for the selected Manufacturer and device type.
Once you have located the desired device, you can click and drag it onto the System tab of the Diagram
Area.
If the device you want to add is not included in the Devices tab, you can use the
DDDP Device and/or the User-Defined Device options to add it to your system.
Refer to the Adding Devices To The Device Database section on page 25 for details.
Status Bar
The Status Bar displays application status and tooltips when the mouse moves over toolbar buttons.
The icons on the right side indicate standard keyboard settings: Caps Lock (CAP), Num Lock
(NUM) and Scroll Lock (SCRL).
The Status Bar display can be toggled via the Status Bar option in the View menu.
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
11
VisualArchitect v1.1 Overview
Related Software Applications
CAFE DUET
Cafe Duet™ is an extension of the powerful NetLinx language for programming AMX Control Systems.
Duet expands the capabilities of existing NetLinx systems using the Java programming language.
Cafe Duet version 1.8 or higher is required to create or edit Duet modules for use with
Cafe Duet (FG3002-20) is available for purchase from www.amx.com.
ContentDatabaseEditor
VisualArchitect provides access to a separate AMX software program called ContentDatabaseEditor
(CDE), that allows you to create and manage Media and Presets databases for use in your VA (and nonVA) projects. Since CDE is also available as a stand-alone application, it has its own help file. Select File
> ContentDatabaseEditor to launch the program, and select Help > Content Database Editor Help
(within CDE) to launch its help file.
CDE is packaged as a integrated utility with VisualArchitect.
To launch CDE from VisualArchitect, select File > Content Database Editor.
Refer to the CDE online help file and Instruction Manual for instructions on creating and
VisualArchitect.
managing Database Files and the Media Library.
KeypadBuilder
KeypadBuilder version 2.1 or higher is required to edit keypad projects generated by VisualArchitect.
Using KeypadBuilder you can:
Assign button arrangements - bridge buttons and assign blanks.
Conduct file Transfers - deliver KeypadBuilder files to devices and NetLinx masters.
KeypadBuilder is available for free download from www.amx.com.
Refer to the KeypadBuilder online help and Instruction Manual for instructions.
FileTransfer 2
FileTransfer 2, version 1.2 build 60 or higher is required for system file transfer support in
VisualArchitect (automatically installed with VA).
The FileTransfer 2 application is available for free download from www.amx.com).
Refer to the FileTransfer 2 online help file and Instruction Manual for instructions on
transferring system files.
G4 PanelPreview
12
G4 PanelPreview is a separate application that allows you to preview fully functional G4 panel files on
your PC, without the need for an actual touch panel. G4 PanelPreview allows you to:
Open any version TPDesign4 panel file.
Simulate push and release of buttons, including multi-state and bar graph buttons via the
mouse and keyboard on your PC.
Simulate the actions of external panel buttons.
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
VisualArchitect v1.1 Overview
V
Simulate computer control and view dynamic images on computers equipped with Ethernet
connectivity.
To launch G4 PanelPreview from VisualArchitect, select the Open project in G4 Panel
Preview option in the Generate TPDesign4 Project dialog.
Refer to the G4 PanelPreview online help file and Instruction Manual for instructions.
IREdit
IREdit version 1.3 or higher is required to receive AMX IR Database updates containing IR control
metadata.
The IREdit application provides the ability to edit IR hand control files (.IRL, .IRV, or IR information
contained within a .IRN database file) for use on Axcess and NetLinx platforms.
You may rename and/or rearrange functions within a hand control, or combine functions from
various hand control files into a single file.
An *.IRN database file is created when you create a new user database within IREdit.
IRN files must be exported from IREdit as IR Library (*.IRL) files in order to be used
by VA.
IREdit is available for free download from www.amx.com.
Refer to the IREdit online help and Instruction Manual for instructions.
NetLinx Studio
NetLinx Studio version 2.4, build 129 or higher, is required to open APW (NetLinx Studio workspace)
files generated by VisualArchitect.
NetLinx Studio is a full featured Integrated Development Environment (IDE) for NetLinx and Axcess
Control Systems.
NetLinx Studio is available for free download from www.amx.com.
Refer to the NetLinx Studio online help and Instruction Manual for instructions.
TPDesign4
TPDesign4 version 2.6 or higher is required to create or edit VisualArchitect touch panel templates, or to
edit touch panel projects generated by VisualArchitect.
TPDesign4 is a touch panel design program designed to assist you in creating a state-of-the-art touch
panel interface for AMX's G4 Level touch panels (including the Modero line and the NXP-TPI/4 Touch
Panel Interface). Use TPDesign4 to create Project Files (*.TP4) containing all of the information
required to define a user-interface to be utilized on a G4 touch panel. This includes Pages, Popup Pages
and associated navigation/page-flip information, as well as buttons (including function code
information), and all image and sound-related files that are used in the design (including dynamic images
and video feeds).
TPDesign4 is available for free download from www.amx.com.
Refer to the TPDesign4 online help and Instruction Manual for instructions.
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
13
VisualArchitect v1.1 Overview
14
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
V
Getting Started
Overview
There are several possible approaches to starting a new VA project:
Use the Basic System Assistant option to specify the NetLinx Central Controller (if different
than the default NI-3000), one Touch Panel (including a Touch Panel Template, Color Scheme
and Font choice), up to two Keypads, and a Remote Controller.
The System Design Library option allows you to select a System Design Library (SDL) file to
open and edit.
System Design Library (*.VAP) files provide several templates for pre-configured
systems of various types (e.g. Auditoriums, Conference Rooms, Boardrooms etc.), to
use as is or as a short-cut to designing several common types of control systems.
The New Empty System option creates a system with no devices other than a NI-3000 Central
Controller.
Start with the Central Controller selection - right click on any Central Controller in the
Toolbox, and select New System Using: from the context menu.
The basic steps involved in creating a system in VA are:
1. Creating a New VA Project/System
2. Adding Devices to the System
3. Setting Device Properties
4. Defining Device Macros (via CodeBuilder)
5. Connecting Devices in the System Diagram
6. Defining the Navigation for UI Devices
7. Saving the Project
8. Generating and Transferring System Files
Getting Started
The VA Device Database
VA uses a Device Database to populate the list of supported third-party devices (displayed in the Devices
tab of the Toolbox). The Device Database is installed as part of the VA installation. This provides
support for several popular devices. However, at some point you will probably want to update the Device
Database to include the particular devices that you want to work with. The Device Database can be
updated via options in the Device Database Manager dialog.
Touch Panel Templates
VA utilizes Touch Panel Templates to greatly simplify the process of designing user-interfaces for the
touch panel(s) in your system. While VA comes with at least one template installed and ready for
selection, additional templates can be installed via options in the Touch Panel Template Manager dialog.
Once installed, templates are available to be applied to touch panels in any VA project.
isualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
15
Getting Started
Using The Basic System Assistant Option
One of the main options presented on the Welcome Screen for starting a new project is the Basic System
Assistant option.
The Basic System Assistant helps you get started designing a new system by allowing you to define
several key pieces of equipment as a first step. You can always add, remove or replace devices later, but
the Basic System Assistant can help you get started.
1. Select File > New > Basic System Assistant (or select Basic System Assistant in the Welcome
Screen) to access the Basic System Assistant dialog. Use the options in this dialog to enter general
project information and specify a NetLinx Central Controller and User-Interface devices.
2. Fill in the Project Information (System name, Dealer, Designer and Comments). The only required
input here is the System name.
3. Use the fields in the lower half of the dialog to select the following system devices:
Every system must have a Central Controller and at least one User-Interface device
(Touch Panel, Keypad or Remote).
NetLinx Controller - Every system must have one (and only one) NetLinx Central Controller.
By default, the NI-3000 is selected. Click on the down-arrow to select from a drop-down list
of all supported NetLinx Central Controllers. Alternatively, click on the Browse button to
open the Select Control Device dialog, where you can browse and select from product photos
of the Controllers.
Touch Panel - Click on the down-arrow to select from a drop-down list of all supported Touch
Panels. Alternatively, click on the Browse button to open the Select Control Device dialog,
where you can browse and select from product photos of the Touch Panels. When you select a
Touch Panel, the Resolution and Template fields are enabled.
Resolution - This option is only enabled if a Touch Panel has been selected, and the
Resolution choices available depend on the type of Touch Panel picked. Most panels only
support one resolution setting, which is automatically set when the Touch Panel is
selected. Click the down arrow to select a resolution setting from the drop-down menu.
Template - This option is only enabled if a Touch Panel has been selected, and if there is
at least one template installed that matches that panel's Resolution setting. Click the
down arrow to select a Touch Panel Template from the drop-down menu. Click the
Browse button (...) to the right of the drop-down menu to browse thumbnails of
compatible templates in the Select Touch Panel Template dialog.
Keypad A, B - Click on the down-arrow to select from a drop-down list of all supported
Keypads. Alternatively, click on the Browse button to open the Select Control Device dialog,
where you can browse and select from product photos of the Keypads. The Basic System
Assistant dialog allows you to select up to two Keypads for inclusion in your system.
Remote - Click on the down-arrow to select from a drop-down list of all supported Remotes.
Alternatively, click on the Browse button to open the Select Control Device dialog, where you
can browse and select from product photos of the Remotes.
4. Click OK to close the Basic System Assistant dialog.
5. If VA detects that there are any support devices required for the devices selected so far (like a WAP
or Ethernet Switch for example), you will be prompted to pick a device from that device category.
Select a device from each Device Selection dialog that is presented, and click OK to proceed.
16
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
Getting Started
V
6. Once all required support devices have been selected, the System Diagram is displayed, indicating
all of the devices you selected.
7. Right-click on each device (except the Central Controller) and select Connect from the context
menu to establish connections between all devices.
At this point, you can add more devices and accessories, set device properties, define macros and UIs to
complete the project.
Using System Design Library Files
System Design Library files (SDLs) represent pre-configured VA Project/Systems designed to
accommodate various installation types.
SDLs are available for Dealers to download from www.amx.com (in the Markets section).
Select a SDL that most closely meets the needs of your customer, keeping in mind that you will have the
ability to customize the solution later by adding different devices and options.
When you download System Design Library (*.VAP) files, they must be placed in the following
directory to be utilized by VA:
C:\Program Files\AMX Control Disc\System Design Library (If you don't already have this directory,
you'll need to create it).
Once you have loaded at least one SDL in the System Design Library directory, you can select it via the
System Design Library dialog:
1. Select System Design Library from the File > New sub-menu, or on the Welcome Screen to open
the dialog.
2. Fill in the Project Information (System name, Dealer, Designer and Comments). The only required
input here is the System name.
3. Click on the down-arrow to select from a drop-down list of all SDLs currently loaded in the System
Design Library directory.
4. Click OK to close the System Design Library dialog.
At this point, you can add more devices and accessories, set device properties, define macros and UIs to
complete the project.
isualArchitect v1.1
Refer to the SYSTEM DESIGN LIBRARY Dealer Manual for Presentation Facilities
(see "AMX System Design Library Dealer Manual" in the help TOC) for detailed
instructions on using System Design Library resources to plan, design, generate and
install a VA system. The SYSTEM DESIGN LIBRARY Dealer Manual uses
"Presentation Facilities" as the example system type.
Using the New Empty System Option
Select New Empty System on the Welcome Screen to start a new system, with no devices other than the
(default) NI-3000 NetLinx Central Controller.
Alternatively, you can select Empty System from the File Menu, or click the toolbar button.
If you start with the New Empty System option, you should visit the Project Properties
dialog to enter basic project information for this system.
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
17
Getting Started
Opening VA Project Files
Select File > Open (or click the toolbar button) to open an existing VA Project file (*.VAP), via the Open
VisualArchitect Project dialog.
18
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
VisualArchitect v1.1
Loading...
+ 212 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.