Operation/Reference Guide VisualArchitect v1.1 System Design Software Document ID: 033-004-2972 Last Revised: 8/30/2006 CONFIDENTIAL AND PROPRIETARY.
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.
Table of Contents Table of Contents VisualArchitect v1.1 Overview ............................................................................1 Supported Windows Platforms and PC Requirements .............................................. 1 The VisualArchitect Workspace................................................................................. 2 Welcome Screen ....................................................................................................... 2 Start a New Project ................
Table of Contents Using The Basic System Assistant Option ............................................................... 16 Using System Design Library Files .......................................................................... 17 Using the New Empty System Option .................................................................... 17 Opening VA Project Files........................................................................................ 18 Creating a New VA Project .........................
Table of Contents Device Database - Default Search Paths ................................................................. 45 Refreshing The Device Database ............................................................................ 45 Rebuilding The Device Database ............................................................................ 45 Updating the Device Database ............................................................................... 46 Device Database Search Paths Manager Dialog .......
Table of Contents Connecting Devices - Touch Panels ............................................................................... 65 Connecting Devices - Keypads ...................................................................................... 65 Connecting Devices - Remotes ...................................................................................... 65 Connecting Devices - Third-Party Devices .....................................................................
Table of Contents Step 3: Change the System Number via the System Menu ........................................... 88 Step 4: Reboot the Master via the System Menu.......................................................... 88 Modero Touchpanels Device Addressing................................................................ 88 Mio Modero Keypad Device Addressing ................................................................ 89 Defining Control Strings ...................................................
Table of Contents Connecting UI Elements - Features ............................................................................. 113 Connecting UI Elements - Placeholders ....................................................................... 113 Connecting UI Elements - Device Elements................................................................. 114 Removing UI Element Connections ............................................................................. 114 Setting UI Element Properties ........
Table of Contents Viewing And Editing Project Properties ............................................................... 133 Saving The Project ................................................................................................ 134 Exporting Diagram Images ................................................................................... 134 Printing The Diagrams ..........................................................................................
Table of Contents Overview .............................................................................................................. 157 Custom Codes....................................................................................................... 157 IR Template Channel Layout: Amplifier ................................................................ 157 IR Template Channel Layout: Camera ..................................................................
Table of Contents Supported NetLinx Central Controllers....................................................................... 203 Supported AMX Keypads............................................................................................ 203 Supported AMX Touch Panels .................................................................................... 203 Supported Expansion Devices.....................................................................................
Table of Contents x CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
VisualArchitect v1.1 Overview 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.
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.
VisualArchitect v1.1 Overview 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.
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, Expansion, Networking, Touch Panels and Keypad devices). Devices - This represents third-party (non-AMX, controlled) equipment.
VisualArchitect v1.1 Overview 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.
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.
VisualArchitect v1.1 Overview 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.
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.
VisualArchitect v1.1 Overview 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.
VisualArchitect v1.1 Overview Select View > Toolbox to access the Toolbox sub-menu, where you can select to hide and show the AMX hardware and third-party device types that can be added to the system. 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.
VisualArchitect v1.1 Overview 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.
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 VisualArchitect. Cafe Duet (FG3002-20) is available for purchase from www.amx.com.
VisualArchitect v1.1 Overview 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.
VisualArchitect v1.1 Overview 14 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Getting Started 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 (*.
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.
Getting Started 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.
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.
Creating a New VA Project Creating a New VA Project Overview The first time you launch VA, you are presented with the Welcome Screen. At the top of the Welcome Screen are options for creating a new NetLinx control system: 1. Click Basic System Assistant (FIG. 13). Use the Basic System Assistant to specify a NetLinx Central Controller (if different than the default NI-3000), one Touch Panel (including a Touch Panel Template, Color Scheme and Font choice), and up to two Keypads. FIG.
Creating a New VA Project and install additional VA template (*.VAT) files from amx.com, via option in the Touch Panel Template Manager dialog. c. By default, the Keypad A and Keypad B are both set to [None]. To add up to two Mio Modero keypads to the system, click on the down-arrow and select from the list of supported AMX Keypads. 6. Click OK to close this dialog.
Creating a New VA Project FIG. 14 Expanding The Port View Use the Auto-Connect feature to let VA make the system connections for you as the devices are dropped into the System diagram. When adding video touch panels (including any of the wired Modero panels), VA (v1.1 or higher) automatically adds the appropriate NXA-AVB Breakout box to the System diagram at the time that the panel is added. Also, note that included accessories cannot be removed from the system. 4.
Creating a New VA Project Setting Device Properties When a device is selected in the System diagram, detailed information for that device is displayed in the Properties window (FIG. 15). Many of these properties are editable, and some require input. FIG. 15 Device Properties window The Properties Window is context sensitive: the rows displayed this table will vary depending on the nature of the selected device.
Creating a New VA Project (***********************************************************) (* DATA TYPE DEFINITIONS GO BELOW *) (***********************************************************) DEFINE_TYPE (***********************************************************) (* VARIABLE DEFINITIONS GO BELOW *) (***********************************************************) DEFINE_VARIABLE (***********************************************************) (* FUNCTION DEFINITIONS GO BELOW *) (****************************
Creating a New VA Project 24 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Working With the Device Database Working With the Device Database Device Database - Overview 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. 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.
Working With the Device Database Download a VA-compatible IRL file for the device from the InConcert Resource Center on www.amx.com, and save the IRL file to a directory included in the Search Paths for the Device Database. See Adding InConcert IR Devices to the Device Database for details. You can also add IRN files that were captured previously using the IREdit application. See Adding IRN Files to the Database for details.
Working With the Device Database Manually Adding IR Devices To The Device Database To manually add an IR-controlled device to the Device Database, so that it appears in the Device tab of the Toolbox: 1. Select File > IR Capture and Management to open the IR Capture and Management dialog. 2. Enter the Device Information for the Device that you are adding. 3. Select the IR Functions that you want to capture. 4. Review and edit the IR properties as required for this device. 5.
Working With the Device Database Adding IRN Files To The Database IR Database (*.IRN) files are created in the IREdit software application. They must first be exported from IREdit as *IRL (IR Library) files in order to be used by VA. Modules and IRLs/IRN files stored on media such as CDs cannot be added to the Device Database. Exporting IRN Files from IREdit as IRL Files: 1. In IREdit, select the user-defined database to be exported from the Navigator window. 2. Select File Menu> Export IR File(s)...
Working With the Device Database Capturing IR Codes VA helps you to capture IR codes for any devices that you want to include in your system that are not already module-supported. All devices listed by name in the Devices tab of the Toolbox are modulesupported. Module-supported devices have their basic IR codes captured within the module, so there is no need to capture their IR codes. Once you have captured a device's IR codes, they are added to the VA database as an IR Capture (*.
Working With the Device Database FIG. 16 IR Capture And Management Dialog - Device Information window Manufacturer - Enter the device manufacturer's name. Model - Enter the device's model name and/or number. Hand Control Model - Enter the model name and/or number of the remote controller associated with this device. Device Type - Select the Device Type that best describes this device from the drop-down menu.
Working With the Device Database Functions/Properties window: Click the Function tab to view the functions defined in the selected IR Template and select which ones to include in the capture operation (FIG. 18). FIG. 18 IR Capture And Management Dialog - Function tab Click the Properties tab to view and edit device-level IR Properties for the selected device type. The IR properties listed here will vary depending on the device type selection, and represent the default settings for that device type (FIG.
Working With the Device Database Stop Bits = 1 Flow Control = None These are the same as the default settings on most PCs for COM ports. If you know that either the IRIS or the COM port that you are using has been configured to use different settings, they must be set to match each other in order for the IRIS to communicate properly with the PC. 4. The "READY" and "VERIFY" LEDs on the front panel of the IRIS should illuminate and the display should indicate "01", indicating that it is ready for use.
Working With the Device Database FIG. 20 Select The IR Functions That You Want To Capture Use the Select All Functions, Clear Function Selection and Invert Function Selection options to streamline the process. Check the Advanced Functions directory for hand controller functions that are represented on the controller, but not included in the Main Functions directory. 2. Click the Commit button to save your changes. The next step is to specify IR Properties for this device.
Working With the Device Database FIG. 21 R Code Capture and Management dialog - Properties tab of the Properties window The IR properties listed here will vary depending on the device type selection, and represent the default settings for that device type. In most cases, these default settings should suffice, but in some cases you may need to edit some IR properties.
Working With the Device Database IR Carrier String: This option indicates whether or not to use IR Carrier signals. The default setting is False (do not use IR Carriers). Carrier signals are sometimes used in IR-transmissions to bookend signals, to add accuracy. Pulse Interval: This option defines the length of time between IR signals, measured in .10second increments. Pulse Time: This option defines the length of time that the IR signal is emitted, also measured in .10-second increments.
Working With the Device Database For best results, place the remote control's IR emitter as close as possible to the IR window on the IRIS. a. Press and hold the button on the remote - the SIGNAL (red) LED on the IRIS should flicker to indicate that is receiving a signal. b. Don't release the button on the remote until the READY (green) turns off (approximately 3 seconds). When the READY LED turns off, the IRIS is ready to verify the signal (by repeating the button press). c.
Working With the Device Database Troubleshooting - IR Capture Problem: Possible Solutions: The ER/E1 message appears in the LED display on the IRIS, and it doesn't seem to capture codes. • Verify that the IRIS is connected to the COM port selected in the IR Capture Options dialog (default = COM1). • Verify that the COM port settings on your PC (for the relevant COM port) match those on the IRIS.
Working With the Device Database c. Click the Browse (...) button next to the new search path to open the Browse For Folder dialog. Select the directory that the new IRL file was saved to, and click OK. d. Click Update to update the Device Database to include the new files (as well as any other device files saved in the same directory). e. Once the database update is complete, click the Close button to exit the Device Database Manager dialog.
Working With the Device Database FIG. 23 New Control Strings Definition dialog - Properties window c. Review the Packet Format and Connection properties, and edit as required: To change any of these properties to a setting other than the default, click inside the Value column for any item to select from a drop-down menu of values supported for each property (FIG. 24). FIG. 24 Click Inside The Value Column To Open The Drop-down Menu 4. The Functions window (FIG.
Working With the Device Database FIG. 26 Control String Assignments window Alternatively, you can select a function and click the Add Function button to add it to the Control String Assignments window. The Control String Assignments window displays the Custom Control Definitions that have been created for this CSD file in a two-column table: The Function column indicates the name of each Function. Some Functions support variable parameters, as indicated by a editable field within the Function column.
Working With the Device Database 7. Assuming all required information is present, the Save As dialog prompts you to specify a filename for this CSD file, and a target directory. Click Save to save the file, and close the Save As and Control Strings Definition dialogs. 8. Update the Device Database to include the new CSD file: The Device Database cannot be changed while a VA Project is open. Save and close your project before proceeding. a.
Working With the Device Database Adding Module-Supported Devices To The Device Database 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. Searching For Duet Module (*.
Working With the Device Database Downloading Duet Module (*.JAR) Files Non-IR controlled (Ethernet, Modem, Serial and TCP/IP) devices can use Duet Module (*.JAR) files for support in VA. VA requires Duet Module v1.7 or higher module (*JAR) files to support third-party (controlled) devices. Duet module files for many popular devices are available for download (as ZIP files) from the InConcert Resource Center at www.amx.com: 1. Search for the device that you want to include in your VA projects. 2.
Working With the Device Database This file allows you to open and edit the system files in NetLinx Studio, and is not transferred to any system devices. *.AXS file - This is the Master Source Code File (and possibly other source code files associated with the System). This file must be transferred to the Central Controller. *.TP4 file - The TPDesign4 project file defines the Touch Panel UI (panel pages, buttons and navigation). This file must be transferred to the Touch Panel. *.
Working With the Device Database b. In the Search Paths window, verify that the folder(s) that you unzipped the new files to are represented in the list. If the new files are in a folder that is not listed, press the Add Search Path button, to add a new entry to the list, then click the Browse button (...) to select the folder that the files are in (in the Browse For folder dialog). c. Click OK to close the Browse For Folder dialog. d. Click Update in the Device Database Manager dialog.
Working With the Device Database Updating the Device Database When you "Update" the device database, VA updates the search paths indicated in the Search Paths window of the Device Database Manager dialog and refreshes the device database. The Device Database must be updated any time that new devices and/or Search Paths have been added. To update the device database: 1. Select Managers > Device Database Manager to access the Device Database Manager dialog. 2.
Working With the Device Database To re-order the Search Paths Select an item in the Search Paths list, and use the up/down arrow buttons to move it up and down in the list. Adding MSRP Values For Third-party Devices VA allows you to add MSRP values for third-party devices, by manually editing the "MSRP.CSV" file that VA uses to provide MSRP values for AMX equipment. To add MSRP values for third-party devices: 1. Open the "MSRP.csv" file.
Working With the Device Database 5. Restart VA to see the MSRP (and Dealer Part Number, if one was included) in the Properties window for that device. Note that you must select the device in the System Diagram in order to view its properties (FIG. 31). FIG. 31 Properties window 48 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Adding Devices to the System Adding Devices to the System Overview The first step in developing a new VA project is to define the devices in the system. This includes selecting the devices that you want in the system and adding them to the System diagram, establishing device connections, and configuring device properties. 1. In the Toolbox, click on a device tab to display the supported devices of that type available to choose from. 2.
Adding Devices to the System Devices/Modules With Multiple Connection Types: Devices that support more than one connection type are listed up to three times in the device tree - there is a separate listing for each connection type supported by that device. For example, if a device in the database has a module that supports IP, Serial and IR connectivity, then that device will be listed three times in the device tree. Each connection type is indicated by a different icon.
Adding Devices to the System If you start a new system via the File > New > Empty System option, the program automatically adds a NI-3000 NetLinx Central Controller. All other devices are added to the system simply by dragging them from the Toolbox into the Diagram Area. You can change the Central Controller type later via the Edit > Replace option.
Adding Devices to the System Selecting AMX User-Interface Devices Once you have selected a NetLinx Central Controller, it is a good time to specify one or more AMX User-Interface devices. User-Interface Devices include AMX Touch Panels and AMX Keypads. Every VA project/system requires at least one AMX User-Interface device. If you started your project with the Basic System Assistant, you can select one Touch Panel and up to two Keypads in the Basic System Assistant dialog.
Adding Devices to the System You can reactivate this prompt at any time via the Help > Reset Message Boxes option. You are not allowed to delete the Central Controller. You can change the Central Controller's type via the Replace option. Replacing The Central Controller VA requires that there is always one NetLinx Central Controller in each system. Since you are not allowed to delete the Central Controller, you must use Replace to use a different type: 1.
Adding Devices to the System FIG. 35 Device Connections Will Be Lost For Missing Ports Also note that when you replace the Central Controller, device properties relative to connection type may be lost.
Adding Devices to the System Alternatively, you can use the Replace Device option in the Toolbox System Devices context menu: 1. Select the device in the System Diagram that you want to replace. 2. Select the device that you want to replace it with, in the Toolbox. 3. Select Edit > Replace (or select Replace Device from the Toolbox System Devices context menu). This option is only enabled if the devices are of the same device type and compatible for replacement.
Adding Devices to the System Dynamic Device Discovery Protocol (DDDP) NetLinx Masters equipped with firmware build 320 or higher support Dynamic Device Discovery, via the Dynamic Device Detector (DDD). The Dynamic Device Detector (DDD) monitors the system for newly connected devices. New devices can be detected via either an external discovery protocol manager, Multicast reception of a Dynamic Device Beacon, or via the receipt of a beacon response on an application specified list of serial devices.
Adding Devices to the System Working With DDDP Devices Every device category in the Devices tab of the Toolbox contains a listing for "DDDP Device". DDDP stands for Dynamic Device Discovery Protocol. DDDP devices are automatically detected by the NetLinx Master when they are connected and powered-up. By default, DDDP Devices always connect to the NetLinx Master via Ethernet 10/100T connection, as indicated in the Connection Type field of the Device Properties window.
Adding Devices to the System 3. In the Configure Binding Options section of this page, click in the checkboxes to enable the following options (FIG. 39): FIG. 39 Configure Binding Options Enable Auto Bind This selection allows an end-user to toggle the state of the automatic binding for DDDP devices (On/Off). When auto-binding is enabled, the Master automatically attempts to connect any newly discovered device with an associated application device (defined in the running NetLinx application).
Adding Devices to the System Error Message: DynamicDeviceDetector.retrieveUrlJar: missing filename in URL response DynamicDeviceDetector.retrieveDriverDependencies: failed to retrieve dependencydevicesdkrt.jar This message indicates that the following requires system file is missing from the Master: "devicesdkrt.jar" Error Message: DynamicDeviceDetector.retrieveUrlJar: missing filename in URL response DynamicDeviceDetector.retrieveDriverDependencies: failed to retrieve dependencysnapirouter.
Adding Devices to the System Alternatively, click the Change Quantity button to access the Quantity dialog. 3. Type the number of the selected accessory to include with the selected parent device in the Enter Quantity field and click OK. 4. The number you entered is indicated in the Additional column for that accessory. The Included column indicates wether this accessory is included with the selected device.
Connecting Devices Connecting Devices Connecting Devices In The System Diagram Each Device Element in the System diagram has at least one Connection Node. Connection nodes represent ports on the actual device, and are used to establish connections between devices and other system devices as well as the NetLinx Central Controller. Device connections are established by creating lines from one element's Output connection node to another element's Input connection node.
Connecting Devices Connect the input node on each device to an output of the same type on the other device. For example, if you add a RS-232 device, you will connect that device's input node to a RS-232 output node on the NetLinx Controller. As you drag the cursor, a line indicates the connection. The cursor will change to indicate which nodes are not permitted for the type of connection you are attempting. 3. Release the mouse button to complete the connection.
Connecting Devices Using Auto-Connect Select Edit > Auto-Connect (or click the toolbar button) to enable the Auto-Connect feature. When Auto-Connect is enabled, any time you drag-and-drop a device onto the system diagram, VA automatically draws a connection between the device and an available port on the Central Controller (or intermediate device required for the device to connect to the Controller, such as a Networking or Expansion device). By default, this option is enabled.
Connecting Devices Connecting Devices - Expansion Devices Expansion devices provide additional ports to NetLinx Central Controllers. Expansion devices include ICSNet and ICSHub servers/cards, NetLinx Cardframes and Control Cards, IR sensors and Power Controllers (FIG. 43). FIG. 43 Connecting Devices - Expansion Devices Connecting Devices - Networking Devices If your system includes touch panels and/or networked control equipment, you will need to include one more Networking device to your system.
Connecting Devices Connecting Devices - Touch Panels Every system must have at least one AMX User-Interface device: Touch Panel, Keypad or Remote (FIG. 45). FIG. 45 Connecting Devices - Touch Panels Some Touch Panels do not connect directly to the NetLinx Controller: MVP (wireless) panels require a Wireless Access Point (e.g. NXA-WAP200G) between the panel and the Controller. Ethernet 10/100T panels require a Network Switch between the panel and the Controller.
Connecting Devices FIG. 47 Connecting Devices - Remotes VA requires that each remote has it's own receiver. Connecting Devices - Third-Party Devices There are two possible approaches to adding third-party (controlled) devices to the system: Adding Module-Supported Devices: These devices are supported by Duet Modules that are packaged with VA that provide device and control information. These can connect to t6he Central Controller either directly or through an appropriate expansion device.
Connecting Devices FIG. 49 Show DDDP Devices VisualArchitect does not provide support for login information on IP devices that require a login. If you have an IP device that requires a login, the device must be added to the Custom .AXI file after system file generation, but prior to file transfer. This is a process that requires NetLinx programming experience and is not recommended for the novice VA user. Use the Connection Manager to define the physical connections on controlled third-party devices.
Connecting Devices In terms of connections, there are two basic variations for MAX servers: Those that have audio outputs (L/R analog stereo and Digital) - including the MMS-01S, -02S and -02SB (FIG. 50). FIG. 50 Connecting Devices - MAX MMS-01S, -02S and -02SB Those that do not - including the MMS-04S, -12S, -900, and HT-04 and HT-12 (FIG. 51). FIG. 51 Connecting Devices - MAX MMS-04S, -12S, -900, and HT-04 and HT-12 However, all MAX Servers feature 2 Ethernet ports and at least 1 USB connection.
Connecting Devices The MAX-AVM connects to the MAX Server via the A/V OUT Ethernet port (named "VLAN" in the MAX Server device elements). Each MAX Server supports up to 25 AVM modules. It is required that a GB Ethernet Switch is used between the MAX Server and the AVMs (FIG. 53). FIG. 53 Connecting Devices - MAX-AVM MAX-AVP Audio-Video Player Like the MAX-AVM modules, MAX-AVP's connect to the MAX Server via the A/V OUT Ethernet port (named "VLAN" in the MAX Server device elements).
Connecting Devices You will need to consult the manufacturer's documentation (or the device itself) to know exactly what connectors exist on each device. Sticking with the DVD Player example, let's assume that you have added a DVD Player with the following physical connectors (FIG. 56): FIG. 56 DVD Player - physical connectors Use the Connection Manager dialog to define each of these connectors in the Connection Manager dialog (FIG. 57): FIG.
Connecting Devices Defining Physical Connectors For System Devices Consult the device manufacturer's documentation (or the device itself) for device specifications and details on connections. Use the Connection Manager dialog to define the physical connectors that exist on system devices: 1. Select a device in the System diagram that you want to define the connectors for. 2.
Connecting Devices Once each connector has been added in the Connection Manager dialog, the Device Element in the System diagram will specifically indicate these connectors, as shown in the DVD Player example below (FIG. 62): FIG.
Setting Device Properties Setting Device Properties Overview When a device is selected in the System diagram, detailed information for that device is displayed in the Properties window (FIG. 63). Many of these properties are editable, and some require input. FIG. 63 Properties window The Properties Window is context sensitive: the rows displayed this table will vary depending on the nature of the selected device.
Setting Device Properties Device Properties by Device Type DEVICE PROPERTIES - CENTRAL CONTROLLERS The following parameters are required for NetLinx Central Controllers, and are set via fields in the Device Properties window. These fields are displayed if a Central Controller is selected in the System diagram. Name - This is the (default) system name for the selected device. Click inside this row to edit the element name; note that the device Name cannot contain any Unicode characters.
Setting Device Properties If you are trying to connect to a master controller that is behind a firewall, you may have to disable this option (set to False). Most firewalls will not allow ping requests to pass through for security reasons. Requires Authentication - Click inside this field to access the drop-down menu and specify whether this Central Controller has been configured to require authentication (select True or False). By default, this field is set to False (no authentication required).
Setting Device Properties Device Properties - Networking Devices The following parameters are required for Networking Devices, and are set via fields in the Device Properties window. These fields are displayed if a Networking device is selected in the System diagram. Name - This is the (default) system name for the selected device. Click inside this row to edit the element name; note that the device Name cannot contain any Unicode characters.
Setting Device Properties Device Properties - Keypads The following parameters are required for AMX Keypads, and are set via fields in the Device Properties window. These fields are only displayed if a Keypad is selected in the System diagram. Name - This is the (default) system name for the selected device. Click inside this row to edit the element name; note that the device Name cannot contain any Unicode characters.
Setting Device Properties Button Name - The button name is for use within VA only, and is intended to assist in developing unique descriptive names. This is not the text that will be engraved on the button (see Engraving - Text below). Engraving Text - Enter the text that you want to have engraved on the selected button in this text field. To enter text, click inside the text field and type directly into the field. Alternatively, click on the browse button (...
Setting Device Properties Category - This is the category of devices that the selected device belongs to (read-only). Manufacturer - This field indicates the name of this device's manufacturer (read-only). Model Number - This is the manufacturer's model name/number for the device (read-only). Connection Type - Click inside this row to enable the Connection Type sub-menu, where you can select any of the connection types supported by this device.
Setting Device Properties Device Number Ranges - By Device Type VA strictly enforces the following device number ranges (entered in the Device Number field in the Device Properties window): Device Number Ranges - By Device Type • Device Type Allowed Device Number Range • AXLink General 1-255 • AXLink UI 128-255 • NetLinx Card Frames 301-3060 - start at frame number 25. First Slot = (frame # * 12) + 1 • ICSNet NetLinx devices (NXI, NXM-COM2, NXM-IRS4, etc.
Setting Device Properties These device properties include communication parameters, and the communication parameters displayed depend on the selected device's control type. Each device's control type is also indicated in the Device Element (in the System diagram). Communication Parameters - Ethernet Connections The following parameters are required for Ethernet connections, and are set via fields in the Device Properties window.
Setting Device Properties COM Port - Select an available COM (communications) port to use for communication with this device. The COM ports available to choose from will depend on the number of COM ports present on the selected device (default = COM1). Baud Rate -Select a baud rate for communications with this device. For most devices the choices range from 75 to 128,000 Bps (default = 38400). Data Bits - Select the number of data bits used for encoding characters.
Setting Device Properties Communication Parameters - TCP/IP Connections The following parameters are required for TCP/IP connections, and are set via fields in the Device Properties window: These fields are only displayed if TCP/IP is selected as the Connection Type for the device. Host Name - Enter a Host Name for this Central Controller in this field (example = " NetLinx"). Port Number - By default, the Port Number is 1319. In most situations, the Port Number should not be changed.
Setting Device Properties Ethernet 802.11b - (also referred to as "802.11 High Rate" or "Wi-Fi") -- an extension to 802.11 that applies to wireless LANs and provides 11 Mbps transmission (with a fallback to 5.5, 2 and 1 Mbps) in the 2.4 GHz band. 802.11b uses only DSSS, and allows wireless functionality comparable to Ethernet. DSSS = Direct Sequence Spread Spectrum.
Setting Device Properties Device Addressing Master Addressing Via Terminal-Telnet To configure NetLinx Master's network address, using telnet or terminal: Although these procedures are written for a Terminal connection, a user can also connect to a Master via a Telnet connection. Do this by going to Start > Run, enter CMD within the Run dialog's Open field and click OK. Then from within the CMD command prompt use the IP Address info to type > telnet XXX.XXX.XXX.XXX .
Setting Device Properties Enter Host Name: NetLinx 3. When prompted to enter an IP Type, the entry defaults to DHCP but you can assign either a DHCP or Static IP Address to the target Master. To Assign a DHCP Address 1. Enter IP type. Type D for DHCP or S for Static IP and then Enter: DHCP If you press the setting remains defaulted to pull a DHCP Address from the DHCP Server. 2. Enter IP type. Type D for DHCP or S for Static IP and then Enter: DHCP 3.
Setting Device Properties NetLinx Device Addressing Via The Master's UI Step 1: Accessing the Master's UI and configuring the NetLinx Device Once the Master's IP Address has been set through either a Terminal or Telnet session: 1. Launch your web browser. 2. Enter the IP Address of the target Master (ex: http://198.198.99.99) into the web browser's Address field. 3. Press the Enter key on your keyboard to begin the communication process between the target Master and your computer.
Setting Device Properties 7. Click Update to save any changes. If your changes are successfully updated to the Master, the following message appears. "Network Settings updated. Device must be rebooted for the setting to take effect". 8. Return to the System menu by clicking on the purple System icon (within the Online Tree), click the Reboot button, and then allow the Master a short time to reboot itself. 9. Click on the Refresh macro from the browser's menu bar.
Setting Device Properties Mio Modero Keypad Device Addressing 1. If connected, disconnect the power supply. 2. Locate the 8-position Device DIP switch on the rear panel. 3. Set the DIP switch according to the switch values shown below: Switch 1 2 3 4 5 6 7 8 Value 1 2 4 8 16 32 64 128 The device number is set by the total value of DIP switch positions that are ON.
Setting Device Properties 90 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Defining Control Strings Defining Control Strings Control Strings - Syntax Rules Use the Control Strings Definitions dialog to write custom control strings for non-IR controlled devices. The syntax rules for Control Strings in VA are as follows: VA (v1.0) supports ASCII text only for control strings when typing into the String Value text fields for each Function.
Defining Control Strings FIG. 66 Value Column FIG. 67 Functions window Double-click on any function in this list to add it to the Control String Assignments window. Alternatively, you can select a function and click the Add Function button to add it to the Control String Assignments window. The Control String Assignments window displays the Custom Control Definitions that have been created for this CSD file in a two-column table (FIG. 68): FIG.
Defining Control Strings The Value column contains text fields that allow you to enter the control string definition for each Function. If a function has been duplicated in the Control String Assignments window, it is flagged with a red (!) icon. Each function should only appear in the string assignment list once. 5. Type the custom control string that you want to assign to each function in the Control Strings Assignments window, in the Value field.
Defining Control Strings 94 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Defining Device Macros Defining Device Macros Overview Use the options in the CodeBuilder dialog to define macros for buttons associated with third-party (controlled) devices in your system. A macro is a series of commands and procedures that are carried out in response to a single button event. Macros are typically used in control systems to allow the enduser to trigger several events from a single touch panel button.
Defining Device Macros FIG. 71 Codebuilder Dialog - User Interface Buttons Window Event Window The Event window displays the steps currently in the active macro (FIG. 72). FIG. 72 Codebuilder Dialog - Event Window Since at least one handler must be used with each button event, there is always at least one tab in the Event window: Push Event (default), Release Event or Hold Event. By default, a Push handler is used with every button event, as indicated by the Push Event tab in the Event window.
Defining Device Macros Codebuilder Toolbar FIG. 74 Codebuilder Toolbar The CodeBuilder dialog toolbar contains shortcuts to the following functions: CodeBuilder dialog toolbar Button Command - Description Button Event Options Opens the Button Events Options dialog, where you can specify which device handler(s) to use for the selected button event. Cut Selected Step Cuts the selected step to clipboard memory. Copy Selected Step Copies the selected step to clipboard memory.
Defining Device Macros Codebuilder Dialog - View Menu Push Button Event - Select to display Push Button Events in the Event window (default = enabled). Release Button Event - Select to display Release Button Events in the Event window (default = disabled). Hold Button Event - Select to display Hold Button Events in the Event window (default = disabled).
Defining Device Macros to each event handler type associated with the selected UI button. Select the tab that represents the button event handler that you want add macro steps to. 6. Click and drag macro elements from the General, Functions and Status tabs into the Event window, in the order that you want the steps to occur. Double-click on an element in the General, Function or Status tabs to add it to the bottom of the macro steps in the Event window.
Defining Device Macros FIG. 77 Event window - Status tab When you select a macro step in the Event window, it is highlighted in red (FIG. 78). FIG. 78 Selected Macro Step By default, the Function and Status tabs allow access to all devices in the system, to allow you to create macros that involve multiple devices. Use the Filter Functions and Filter Status options (FIG. 79) to filter the Functions and Status tabs to show only the currently selected device. Filter Functions Filter Status FIG.
Defining the Navigation for UI Devices Defining the Navigation for UI Devices Overview User-Interface (UI) devices are the AMX devices in the system that the end-user will interact with to control the other equipment in the system. UI devices can be either AMX Touch Panels or AMX Mio Modero Keypads. In either case, once you have added at least one UI device to the system, you'll need to define the navigation for each UI device.
Defining the Navigation for UI Devices The basics of defining the Touch Panel UI include: 1. Adding UI Elements to the UI diagram - drag-and-drop UI Elements from the Toolbox onto the diagram. 2. Connect the UI Elements - draw connection lines to establish the flow between the pages and UI Elements. Touch Panel UI Diagram For every Touch Panel added to the system, a separate Touch Panel UI tab is added to the Diagram Area.
Defining the Navigation for UI Devices 2. Select the desired UI element and drag-and-drop it into the UI diagram. Each element in the UI diagram is represented by a UI Element. Mode Selection Elements - Select a Mode Selection element with the number of modes that you want to define. Mode Selection elements can define from 2 to 9 mode selections. Navigation Elements - Select a Navigation element with the number of devices that you want to allow access to.
Defining the Navigation for UI Devices FIG. 82 Replace Icon If the elements are not compatible for replacement, the cursor icon indicates that replacement is not allowed (FIG. 83). FIG. 83 Replace Not Allowed Icon Alternatively, you can use the Replace Element option in the Toolbox User Interfaces context menu: 1. Select the element in the Touch Panel UI Diagram that you want to replace. 2. Select the element that you want to replace it with, in the Toolbox. 3.
Defining the Navigation for UI Devices Many templates support multiple Color Schemes. Click in the Color Schemes field in the Properties window to view and select from the color schemes available for the selected template. Installing Touch Panel Templates In order to select a touch template to use with the panels in your system, you must first install at least one template via the Touch Panel Template Manager dialog. 1.
Defining the Navigation for UI Devices This menu only lists installed templates that support the panel's resolution setting. Not all templates support every possible screen resolution, but many templates do support multiple resolutions. 5. Click OK to close the dialog and apply the selected settings. Selecting A Touch Panel Template - Via Device Properties VA utilizes Touch Panel Template (*.VAT) files to greatly simplify the process of designing userinterfaces for the touch panel(s) in your system.
Defining the Navigation for UI Devices 4. The program will prompt you to verify this action before the template is permanently uninstalled (click OK to proceed). Color Schemes Many Touch Panel Templates support multiple Color Schemes. Color Schemes add flexibility to your panel UI's visual design by using different palettes to create variations on the template design. An example set of color schemes is shown below (FIG. 86): FIG.
Defining the Navigation for UI Devices Changing The Color Scheme On A Touch Panel Template Use the Color Schemes dialog to preview and select from the Color Schemes available for the selected template: 1. Select a Touch Panel in the system diagram to populate the Device Properties Window for that panel. 2. Select and apply a Touch Panel Template, if you haven't already done so. 3.
Defining the Navigation for UI Devices Click Save to save the preview image as a *.PNG file. This selection invokes the Save Preview Image dialog, where you can specify a filename and target directory for the saved PNG file. By default, the image is named according to the device that the Navigation Element is associated with, and the default target directory is the directory that you have saved your VA project to. Click To Clipboard to save the preview image to the clipboard.
Defining the Navigation for UI Devices FIG. 89 Connection Nodes - Touch Panel UI Diagram The ENTER nodes (on the right side of the Template Element) connect to other UI elements in the UI. Connect each controlled device indicated in the Touch Panel UI diagram to the ENTER nodes. As UI elements are connected, each UI element name is indicated on the connecting element (FIG. 90): FIG.
Defining the Navigation for UI Devices FIG. 92 Provide A Path Back To The Start Device You can create this path back to the Start Page from more than one Mode Selection or Navigation element. Depending on the overall layout of the UI, you might consider creating a path back to the Home Page (FIG. 93). FIG. 93 Provide A Path Back To The Start Device For practical reasons, every Touch Panel UI must provide at least one path back to the Start Device element (Home Page).
Defining the Navigation for UI Devices These are only a few basic examples, and modes can be used to accomplish any combination of these and more, depending on your job requirements. Be sure to use one of the exit nodes on the Mode and Navigation elements to connect back to the Start Device. This will provide the end-user with a button that brings them back to the Start page (FIG. 95). FIG.
Defining the Navigation for UI Devices FIG. 98 Each Mode Providing Access A Separate Navigation Element Be sure to use one of the exit nodes on the Mode and Navigation elements to connect back to the Start Device. This will provide the end-user with a button that brings them back to the Start page (FIG. 99). FIG.
Defining the Navigation for UI Devices Connecting UI Elements - Device Elements Device Elements in the Touch Panel UI diagram represent the device-specific pages in the Touch Panel UI. Device Elements provide access to the controlled functions of each device in the system (FIG. 101). FIG. 101 Device Element Removing UI Element Connections To remove a UI Element connection: 1. Select an element in the UI diagram and right-click to open the Touch Panel UI Diagram context menu. 2.
Defining the Navigation for UI Devices UI Element Properties - Start Device Element When the Start device (touch panel) is selected in a Touch Panel UI diagram, the Properties window is populated with Start Device Navigation properties. Name - This is the (default) system name for the selected UI element - it only appears on the UI diagram (it is not displayed on the generated Touch Panel page).
Defining the Navigation for UI Devices Device Port Number - This field displays this element's default device port number assignment (on the touch panel). Click inside this field to change this assignment. Items - This list indicates the items (devices) that are represented on this template element. When controlled devices are connected to the nodes on this element, the default device names (Manufacturer and Model Number) are added to the Item slots for easy identification.
Defining the Navigation for UI Devices Typically, the View Name is used to enter Unicode text for display on the panel, or to leave the system name of a device to as the default 'Manufacturer Model Number' (e.g., 'Marantz DV9500) while displaying a different name on the panel (e.g., 'DVD'). Comments - Click inside this row to add any developer's comments regarding this Template element. Category - This field displays the category (type) of the selected UI element - in this case, Features (read-only).
Defining the Navigation for UI Devices View Name - This field allows you to specify a View Name for this element. The View Name is displayed on the panel page that this element represents. Click inside this row to enter a View Name, which may contain Unicode characters. When you add a View Name to an element, the View Name is indicated in parenthesis beneath the Name on this element (in the Touch Panel UI diagram).
Defining the Navigation for UI Devices Customizing Touch Panel UI Pages Use the options in the Customize UI Pages dialog to edit the Touch Panel pages for controlled (thirdparty) devices in the system. To access this dialog, select a device element in a Touch Panel UI diagram, and select Touch Panel > Customize UI Pages (or click the toolbar button). Visual Architect automatically deletes any buttons for functions that are not supported by the selected device (e.g.
Defining the Navigation for UI Devices 3. Click and drag the button to position it as desired. 4. To change the text displayed on the new button, right-click on the button and select Edit Element Text from the context menu (or click the toolbar button). Type the text that you want to display on this button in the Enter Text dialog. Deleting User-Interface Elements From The Touch Panel Page VA generates default touch panel pages for each third-party (controlled) device in the system.
Defining the Navigation for UI Devices Customize UI Pages Dialog With a Template Device Element (for a third-party device) selected in a touch panel Navigation diagram, select Touch Panel > Customize UI Pages (or click the toolbar button) to access the Customize UI Pages dialog, where you edit the touch panel page for the selected controlled device. Alternatively, right-click on a Template Device Element and select Customize UI Pages from the context menu. This dialog contains its own Toolbar (FIG.
Defining the Navigation for UI Devices Generating The TPDesign4 Project (*.TP4) File 1. With a touch panel selected in the System diagram, select Touch Panel > Generate TPDesign4 Project (or click the toolbar button). This selection opens the Generate TPDesign4 Project dialog, where you can edit the name and target directory for the resulting TP4 project file. By default, the TP4 file is named as follows: VA Project Name - Touch Panel Name.TP4 2.
Defining the Navigation for UI Devices FIG. 107 Mio Modero Elite - S, SL, D and DL Keypads To define the UI for Keypads, use the Button Properties fields in the Device Properties Window to assign a Button Name, specify the Text to be engraved, and view the Channel Code assigned to each button: 1. Click on a button in the Keypad UI diagram. This action displays the properties for the selected button in the Device Properties window.
Defining the Navigation for UI Devices 5. Specify the size of the text from the Engraving Scale drop-down menu. Click inside the text field to enable Up and Down arrows to allow scaling the selected button text up or down, in.10% increments (default = 1.0, or 100%). Keypad UI Tabs For every Keypad added to the system, a separate Keypad UI tab is added to the Diagram Area. For Keypads that do not feature an LCD display, the UI consists channel codes assigned to each button.
Defining the Navigation for UI Devices Menu Actions only apply to Keypads equipped with an LCD display. The labels displays are toggled via options in the Keypad Menu (Show Button Numbers, Show Menu Actions, Show Button Name). Keypad Buttons Keypads rely on pushbuttons to allow the end-user to control system devices. Click on any button on the Keypad UI diagram to select it for editing, via the button properties in the Properties window (FIG. 110). FIG.
Defining the Navigation for UI Devices Engraving Text - Enter the text that you want to have engraved on the selected button in this text field. To enter text, click inside the text field and type directly into the field. Alternatively, click on the browse button (...) to access the Enter Text dialog - enter the button text and click OK to save. There is a maximum of 10 characters per button.
Defining the Navigation for UI Devices 2. Identify the two buttons that you want to combine, and click the button on the left. 3. This action applies the button information from the selected button and assigns it to the button directly to the right of it, thus treating two buttons as one. The combined buttons are also indicated in the Keypad image in the UI tab (FIG. 111). FIG. 111 Combined Buttons Indicated In The Keypad UI Tab Combining buttons adds double buttons to your custom engraving order.
Defining the Navigation for UI Devices For each device listed in the Main Menu, there is a device-specific Sub Menu that provides specific controls for the selected device. Sub menus also typically provide a way for the enduser to return from the sub-menu to the Main Menu. Adding Devices To The Main Menu To control a device via a Keypad, you must first add each device that you want to control to the Main Menu on the LCD Display Menu: 1.
Defining the Navigation for UI Devices Repeat this process to add all of the events that you want to control from this keypad. Consider using separators to drop a horizontal line between events on the Sub Menu, to separate functions or sets of functions: To add a separator, click on [Add Menu Item] in the Sub Menu window (of the Keypad Fixed Menu Editor dialog). 1. Click Add to open the Add Sub Menu Item dialog. 2.
Defining the Navigation for UI Devices The AMX Icons2 font provides various control-oriented icons that can be engraved on the buttons. Click here for a character map for AMX Icon 2. The VA Engraving module supports the fonts included in the supported OS (System) languages. You must have the language loaded on you OS and then use Arial Unicode MS to render the text on the button. Supported System Languages: English (US) French Spanish German Russian 5.
Defining the Navigation for UI Devices FIG. 113 Remote Button Properties Window Remote Button Properties When you select a button in a Remote UI diagram, the following additional Remote Button Properties fields appear in the Properties window: Button Name - The button name is for use within VA only, and is intended to assist in developing unique descriptive names. This is not the text that will be engraved on the button (see Engraving - Text below).
Defining the Navigation for UI Devices 1.1 = 110% 1.2 = 120% 1.3 = 130% 1.4 = 140% 1.5 = 150% Click inside the text field to enable Up and Down arrows to scale the selected button text up or down, in .10% increments. Exporting The Remote Button Engraving Template As A DXF File Once you have specified the text that you want to have engraved on each of the buttons on the Remote, you can export the button engraving template as a DXF file. DXF files are generally compatible with CAD graphics programs. 1.
Finishing the Project Finishing the Project Overview After creating a system, there are a few steps involved in finishing the project: 1. Review the Project Properties 2. Save the Project 3. Generate and Transfer System Files: Refer to the Generating The TPDesign4 Project (*.TP4) File section on page 122. Refer to the Generating The KeypadBuilder Project (*.KPB) File For Keypads section on page 129. Refer to the Generating The KeypadBuilder Project (*.
Finishing the Project Saving The Project Select File > Save (or click the toolbar button to save the project under its current name. The first time you save the project, the Save VisualArchitect Project dialog prompts you to define a File Name and specify a target directory for the Project (*.VAP) file. Select File > Save As to save the Project under a different name.
Finishing the Project Use the Select All and Deselect All buttons to select/deselect all diagrams in the list. 3. Specify the Margins for the printout: Enter the space you want to allocate as margins on the printed page (in inches) in these fields. The default margin settings are: Left = 0.5", Right = 0.5", Top = 0.25", Bottom = 0.25". 4.
Finishing the Project Select Generate System Report to generate the System Report (HTML) file (default = enabled). 4. Select a Compile option: Select Compile With Debug Info to include variable symbol information in the compiled file. This allows the debugger to identify and validate variable symbols in the code. You must compile with debug info in order to debug NetLinx files.
Finishing the Project 2. Under Actions, select Transfer Previously Generated System Files. 3. Under Transfer Options, specify a Transfer Folder (source directory) that contains the system files that will be transferred. Click the browse icon to navigate to the desired folder in the Browse for Folder dialog. 4. Click Start. The Progress bars indicate the status of the operation, and the program will alert you if there are any problems or issues with the system files during the process.
Finishing the Project Making Your Project Portable In some situations you may need to prepare your VA Project so that it can be opened on a PC that does not have VA installed. In this example, you would use the NetLinx Studio 2 application to transfer the System files generated in VA. To make your VA project portable: 1.
Finishing the Project b. Verify (or edit if necessary) the file name of the NetLinx Studio Workspace (*.APW) file that will be created. 7. Check the Include Module Files that are not part of the Workspace option. Verify that the Keep Existing Folder Names option is unchecked. 8. Click on Export to export the Workspace file (including all module files) to the specified "To Go" (*.AXW) file name and target directory. 9.
Finishing the Project FIG. 117 AXW File Extraction Is Complete Generating the System Report (HTML) File Select System > System Report (or click the toolbar button) to access the System Report dialog. Use this dialog to specify an output folder for the System Report (HTML) file for this project: 1. Specify an Output Folder: Enter the directory path for the target directory for the System Report, or click the folder icon to browse for the target directory. 2.
Finishing the Project System Diagram This is a printable version of the System diagram for this project (FIG. 118). FIG. 118 System Diagram Equipment List This is a listing of every device in the system (FIG. 119). FIG. 119 Equipment List Installation Checklist Use the Installation Checklist as a guide to the installation process. Each item in the checklist should be completed before you continue (FIG. 120). FIG. 120 Installation Checklist VisualArchitect v1.1 CONFIDENTIAL AND PROPRIETARY.
Finishing the Project Wiring Connections This section includes detailed wiring and connection information for each device in the system. Use the information in these sections to aid in the installation process. The subsections under Wiring Connections will depend on the devices in the system, and the types connections that exist between system devices (FIG. 121). FIG.
Finishing the Project Troubleshooting and Support This section contains troubleshooting information relating to many different aspects of the control system (FIG. 123). FIG. 123 Troubleshooting and Support Contact Information This section provides contact information for AMX technical support. VisualArchitect v1.1 CONFIDENTIAL AND PROPRIETARY.
Finishing the Project Using AMX Power Calculator Select Help > Power Calculator to open the AMX Power Calculator.xls worksheet file. FIG. 124 AMX Power Calculator You'll need to have a program loaded on your PC that can open XLS files (such as Microsoft® Excel) in order to use this worksheet. This worksheet uses macros to calculate maximum wiring distances and voltage drop. based on cable size and distance. When opening the file, select Enable Macros.
Finishing the Project By default, length is calculated in feet. Click the drop-down menu (in column E) to change "FEET" to "METERS". 4. Press the TAB key (or click in any other cell) to enter the information and update the table with the various cable and voltage drop information that it provides: Max Cable Length (Column C, Rows 4-10): This group of cells shows the total feet of cable of a particular size that can support the selected equipment.
Finishing the Project 146 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Appendix A: Troubleshooting and Support Appendix A: Troubleshooting and Support Overview AMX provides several useful Troubleshooting tools. In NetLinx systems you can use Terminal, Telnet, or the Master's browser-based UI. More information on these tools is available within both the Software Installation and AMX Technical Publications sections of the AMX website.
Appendix A: Troubleshooting and Support FIG. 125 Manage Other Devices page Ethernet Cable Troubleshooting Tips Look for the following things when troubleshooting Ethernet: With 10Base-T & 100Base-T, verify the cable being used has the correct number of twists to meet the data grade specifications. Electrical interference can be caused by tying the network cable together with monitor and power cords.
Appendix A: Troubleshooting and Support 2. Check the status of your transfers, and close File Transfer 2. Once File Transfer 2 shuts down, VA should be ready to use. 3. Check the System Number assignment for the Central Controller. By default, it is set to "1" (the system you are currently connected to). 4. Correct the system number assignment and save the project. 5. Press Ctrl+T to generate and transfer the system files.
Appendix A: Troubleshooting and Support Cabling Once you have a good indication from the TX LED: 1. Short pins 2 and 3 on the DB-9 or Phoenix connector on the port. 2. Send a command and watch the TX and RX (receive) LEDs. You should see both LEDs light when each command is sent. If only the TX LED is lighting, the unit is not sending strings and you should send it in for repair. If both LEDs light up, move on to the next step. 3.
Appendix A: Troubleshooting and Support The Controlled Device Although not every process can be described, some aspects of verification are commonplace. You must verify the following information by either reviewing the corresponding device's manual, or contacting the manufacturer for details: Baud rates are set to their default values (If it can be altered, verify current settings). Cable pin specification are the same as the actual cable. Make certain the COM port is enabled.
Appendix A: Troubleshooting and Support 2. Clicking on any of the Online Tree items opens menu items with the Control/Emulate button option available. 3. Click the Control/Emulate button to open the Control/Emulate dialog. 4. Click the Update Status button to query the Master for the status of the currently entered level and channel. 5. Select either the Control or Emulate option: a.
Appendix A: Troubleshooting and Support decimal numbers, ASCII characters and hexadecimal numbers (prepended with a $), and are comma-delimited. String Literals start and end with single quotes ( ' ). To escape a single quote, use ''' (three single quotes). Manage System - Diagnostics This page allows an authorized user to setup and monitor diagnostic messages coming from and going to devices available on the Online Tree.
Appendix A: Troubleshooting and Support Feature Description Update Click this button once you have completed setting up your filter. The popup then closes and returns you to the Diagnostics window.Watch the bottom Incoming Message pane for messages to begin coming in from the target device(s). Remove This list of up to 10 presets comes defaulted with Preset 0: All Devices, All Notifications·Store: Save the current notification selections to a Preset profile.
Appendix A: Troubleshooting and Support Remove a diagnostic filter by clicking the Modify button below it (from the Diagnostics dialog), then pressing the Remove button to delete this filter from the Diagnostics dialog. Once a Preset is assigned to a specific Diagnostic filter "slot" (up to 8), its System:Device:Port fields are greyed-out, and can't be modified unless the Preset in that slot is removed and replicated with new information within these fields.
Appendix A: Troubleshooting and Support If VA Won't Compile Your Project There are a few things that could prevent VA from successfully compiling your project. If your project won't compile, check the following: 1. Do you have "Power User" (or "Administrator") access rights on the PC running VA? Because the VA compiler writes to common areas of the registry, the User that is logged in on the PC cannot belong to the Restricted User group.
Appendix B: VA IR Templates - Channel Layouts Appendix B: VA IR Templates - Channel Layouts Overview Select Device Type in the IR Capture and Management dialog to view a listing of IR Template provided by VA. Custom Codes IR slots 240-255 are reserved for Custom use in VA, to allow you to capture remote-specific functions into Custom 1 - Custom 16. You can then write custom code in Custom .AXI to use those IR functions. The Custom.
Appendix B: VA IR Templates - Channel Layouts Channel Number 65 66 67 68 69 70 Camera (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 80 81 82 83 84 85 VisualArchitect v1.1 CD Changer/Player (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 86 87 88 89 90 91 92 93 94 98 99 100 101 102 103 104 105 106 107 108 109 110 160 CD Changer/Player (Cont.) Function Name Track 17 Track 18 Track 19 Track 20 Track 21 Track 22 Track 23 Track 24 Track 25 >10 >20 Disc 0 direct Disc 1 Disc 2 Disc 3 Disc 4 Disc 5 Disc 6 Disc 7 Disc 8 Disc 9 Disc 10 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 Required No No No No No No No No No No No No No No No No No No No No No No VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Digital Satellite System (DSS) Channel Number 9 10 11 12 13 14 15 16 17 18 19 21 22 23 24 25 26 27 28 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts Channel Number 67 68 69 70 71 72 73 162 Digital Satellite System (Cont.) Function Name Surf DSS +100 +1000 Help Page Up Page Down CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 Required No No No No No No No VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Digital Video Recorder (DVR) Channel Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 21 22 23 27 28 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts Channel Number 63 64 65 66 67 68 69 70 71 72 73 74 75 76 164 Digital Video Recorder (Cont.) Function Name Slow Motion Quick Skip Display Input Exp Help Info / Display List Page Up Page Down Frame + Frame Favorites Advance CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 Required No Yes Yes No No No No No No No No No No No VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Document Camera Channel Number 2 3 4 9 10 11 12 13 14 15 16 17 18 19 27 28 31 32 33 34 44 45 46 47 48 51 52 53 54 55 56 57 58 61 62 66 67 68 69 70 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: DVD Changer/Player Channel Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 27 28 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 166 Function Name Play Stop Pause Skip >>| Skip |<< Fwd >> Rev << Record Power 0 1 2 3 4 5 6 7 8 9 +10 Power On Power Off A/B A/B Repeat Menu Cursor ^ Cursor v Cursor < Cursor > Navigation Select Exit Title Menu T on Tosh; T/C Mitsu;Title/Chapter Clear Return Angle Subtitle On/Off
Appendix B: VA IR Templates - Channel Layouts Channel Number 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 84 86 87 88 89 90 91 92 93 VisualArchitect v1.1 DVD Changer/Player (Cont.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Lighting Channel Number 10 11 12 13 14 15 16 17 18 19 28 43 44 45 46 47 48 49 50 168 Function Name Scene 10 Scene 1 Scene 2 Scene 3 Scene 4 Scene 5 Scene 6 Scene 7 Scene 8 Scene 9 All Off Scene 11 Scene 12 Scene 13 Scene 14 Scene 15 Scene 16 Raise Lower CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 Required No No No No No No No No No No No No No No No No No No No VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Monitor IF THIS DEVICE HAS A TUNER, USE THE TV IR TEMPLATE AND THE TV TUNER DEVICE CATEGORY. Channel Number 9 10 11 12 13 14 15 16 17 18 19 21 24 25 26 27 28 44 45 46 47 48 49 50 51 52 53 54 55 61 62 63 64 65 66 67 68 69 70 71 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts Channel Number 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 102 103 104 105 106 107 108 109 110 111 112 113 120 121 122 170 Monitor (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 161 162 163 164 165 166 VisualArchitect v1.1 Monitor (Cont.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Motor Channel Number 2 3 4 7 8 Function Name Stop Open/Up Close/Down Rotate Left Rotate Right Required No No No No No IR Template Channel Layout: Pre Amp/Surround Processor Channel Number 9 24 25 26 27 28 43 44 45 46 47 48 49 50 59 60 61 62 63 64 65 66 67 68 69 72 73 74 75 76 77 78 79 80 172 Function Name Power Volume ^ Volume v Mute Main Power On (discrete) Main Power Off (discrete) MENU FUNCTIONS BELOW Menu Cursor Up Cursor Do
Appendix B: VA IR Templates - Channel Layouts Pre Amp/Surround Processor (Cont.) Channel Number Function Name 81 AV 1 82 AV 2 83 AV 3 84 AV 4 85 AV 5 86 AV 6 87 AV 7 88 AV 8 89 AV 9 90 AV 10 91 AV 11 92 AV 12 93 AV 13 94 AV 14 96 Up/Inc/Level + 97 Down/Dec/Level 100 SURROUND FUNCTIONS BELOW 101 Surround On/Off 102 Surround On (discrete) 103 Surround Off (discrete) 104 Main Mode Select (toggling) 105 Sub Mode Select 106 Direct 107 5.
Appendix B: VA IR Templates - Channel Layouts Pre Amp/Surround Processor (Cont.) Channel Number Function Name 129 Mode 9 130 Mode 10 131 Mode 11 132 Mode 12 133 Mode 13 134 Mode 14 135 Mode 15 136 Mode 16 137 Mode 17 138 Mode 18 139 Mode 19 140 SURROUND STEERING BELOW 141 Rear ^ 142 Rear v 143 Center ^ 144 Center v 145 Sub Vol + 146 Sub Vol 147 Balance Left 148 Balance Right 149 Ch Select 150 Ch Level + 151 Ch Level 152 Balance 153 Center 154 Rear 155 Side 174 CONFIDENTIAL AND PROPRIETARY.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Radio Channel Number 9 10 11 12 13 14 15 16 17 18 19 22 23 24 25 26 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 69 70 71 72 73 74 75 76 77 78 95 96 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts Channel Number 97 98 99 100 156 157 158 159 160 161 162 162 163 163 164 165 166 168 169 176 Radio(Cont.) Function Name AM FM XM Band 4 (TV, WX, SW) Jump / Prev Station Scan / Scan + Scan Seek / Seek + Seek Shift Band Band Cycle Direct Tune / Mode Direct Tuning; Mode Tuner Index + (Sony) Tuner Index - (Sony) FM Mode / ST / MONO Preset + Preset - CONFIDENTIAL AND PROPRIETARY.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Receiver Channel Number 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts Channel Number 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 178 Receiver (Cont.) Function Name Audio Input 6 Audio Input 7 Audio Input 8 Audio Input 9 Category Up (XM) Category Down (XM) .
Appendix B: VA IR Templates - Channel Layouts Channel Number 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 VisualArchitect v1.1 Receiver (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 180 Receiver (Cont.) Function Name Center Rear Side Jump/Prev Station Scan/Scan + Scan Seek/Seek + Seek Shift Or Bank Select Band or AM/FM Direct Tuning Tuner Index + Tuner Index FM Mode/ ST/Mono Save Tuner Preset + Tuner Preset - CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 Required No No No No No No No No No No No No No No No Yes Yes VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Set Top Box Channel Number Function Name 9 On/off (toggling) 10 0 11 1 12 2 13 3 14 4 15 5 16 6 17 7 18 8 19 9 21 Enter; Select 22 Channel ^; Tune ^ 23 Channel v : Tune v 24 Volume + 25 Volume 26 Mute/mts 28 Off (discrete) 42 A/B; Source on Zenith 44 Menu 45 Select ^ 46 Select v 47 Adjust < (Zenith) 48 Adjust > (Zenith) 49 Parental Control; AU; Authorize on Sci Atlanta 50 Timer; TCP; Sleep on SA 51 Clock 52 Delete 53 Select; Event 54
Appendix B: VA IR Templates - Channel Layouts Channel Number 68 69 71 72 73 74 75 76 182 Set Top Box (Cont.) Function Name --> (move on screen control arrow) Last Channel;LC; Pref/Next Exit Code; Learn (access code) DCR Guide Page Up Page Down CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 Required No No No No No No No No VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Slide Projector Channel Number 9 27 28 45 46 47 48 49 50 51 56 57 58 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts Channel Number 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 184 Slide Projector (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 VisualArchitect v1.1 Slide Projector (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 186 Slide Projector (Cont.) Function Name Slide 119 Slide 120 Slide 121 Slide 122 Slide 123 Slide 124 Slide 125 Slide 126 Slide 127 Slide 128 Slide 129 Slide 130 Slide 131 Slide 132 Slide 133 Slide 134 Slide 135 Slide 136 Slide 137 Slide 138 Slide 139 Slide 140 CONFIDENTIAL AND PROPRIETARY.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: TV Channel Number 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 VisualArchitect v1.
Appendix B: VA IR Templates - Channel Layouts Channel Number 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 188 TV (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 110 111 112 113 114 115 116 117 118 119 VisualArchitect v1.1 TV (Cont.) Function Name PIP Size PIP Split PIP Input Sleep 1000 Freeze Page Up Page Dn Input Toggle/Input + Input - CONFIDENTIAL AND PROPRIETARY.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: VCR Channel Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 44 190 Function Name Play Stop Pause Ffwd >> Rew << Search Fwd >>| Search Rev |<< Record Power; Standby (toggling) 0 or 10 1 2 3 4 5 6 7 8 9 +10 or +100 Enter Channel + Channel Volume + Volume Mute Power On (discrete) Power Off (discrete) TV/Video or TV/VCR TV Video1 or Line A or Input + Video 2 or
Appendix B: VA IR Templates - Channel Layouts Channel Number 45 46 47 48 49 50 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 81 82 83 84 85 86 87 88 89 90 VisualArchitect v1.1 VCR (Cont.
Appendix B: VA IR Templates - Channel Layouts IR Template Channel Layout: Video Projector Channel Number 9 10 11 12 13 14 15 16 17 18 19 21 24 25 26 27 28 30 31 32 33 34 35 36 37 38 39 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 192 Function Name Power; Standby; Lamp (toggling) Input/Key 0 Input/Key 1 Input/Key 2 Input/Key 3 Input/Key 4 Input/Key 5 Input/Key 6 Input/Key 7 Input/Key 8 Input/Key 9 Enter Volume up Volume Down Toggling Audio Mute Power On (discrete) Power Off (discrete) Input Video 1 Vid
Appendix B: VA IR Templates - Channel Layouts Channel Number 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 VisualArchitect v1.1 Video Projector (Cont.
Appendix B: VA IR Templates - Channel Layouts Channel Number 103 107 108 109 200 201 202 203 204 205 194 Video Projector (Cont.) Function Name Info PIP PIP Position Swap PIP Select + Select Standby toggle (only if 9,27,28 are present) Standby on (only if 9,27,28 are present) Standby Off (only if 9,27,28 are present) Select (only if enter is already present) CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 Required No No No No No No No No No No VisualArchitect v1.
Appendix C: Using an IRIS IR Capture Unit Appendix C: Using an IRIS IR Capture Unit Overview The IRIS Infrared Capture Unit (FIG. 126) is a stand-alone, self-contained unit used to capture infrared (IR) or wired-IR function signals from a hand-held remote controller (RC). FIG. 126 IRIS Infrared Capture Unit After you capture IR functions with the IRIS unit, the functions are sent to a PC running VA. VA creates RC function files that are then downloaded to the Central Controller.
Appendix C: Using an IRIS IR Capture Unit IRIS - Product Specifications (Cont.) Rear Panel Components: • 12 VDC/12 VA Connector: 2-pin (male) 12 VDC or 12 VAC power supply connector. • 8-pin data connector: Captures wired-IR RC functions. Connect the RC to the IRE IN or WIRED IN pins. • RS-232 connectors: DB-9 connector for data communications with a PC6-pin RJ-11 modular connector for data communications. Note: The RJ-11 connector is only used with older SX-DCU+ products.
Appendix C: Using an IRIS IR Capture Unit Press the send pushbutton to send the captured RC function to the PC running Visual Architect. Repeat steps 3 through 6 to capture all the RC functions on your list. If you cannot capture an RC function in default mode, set the IRIS unit to Special Function (SP) mode. IRIS - Capturing RC Functions In SP (Special Function) Mode If you cannot capture an RC function in default mode, set the IRIS unit to special function (SP) mode.
Appendix C: Using an IRIS IR Capture Unit Default Mode Settings: • Default Setting • Baud 9600 • P3 off • P4 on • P5 off • P6 on • P7 on • P8 off IRIS - Display Characters and P Mode Settings The following table lists the display characters and P mode settings for special remote controllers (RCs). Display Characters and P Mode Settings Characters Description • [] RC function is captured, analyzed, stored, and verified. • Er Error: RC function did not verify correctly. • Nd No Device.
Appendix C: Using an IRIS IR Capture Unit 3. The two digits that appear in the display represent the current baud rate setting. 4. Press the up or down pushbuttons to reset the baud rate. 5. Press and hold the up, down, and send pushbuttons again to set the new baud rate. The Ready LED lights to indicate the IRIS unit is ready to capture a RC function.
Appendix C: Using an IRIS IR Capture Unit IRIS - Remote Control IR Functions The following table lists Remote Controller IR functions in standard order: IRIS - Remote Control IR Functions Function Description Function Description 1 Play > 22 Channel up or + 2 Stop [ ] 23 Channel down or - 3 Pause | | or still 24 Volume up or + 4 Ffwd >> (AMS/skip track/chapter) 25 Volume down or - 5 Rewind << (AMS/skip track/chapter) 26 Mute 6 Search fwd >>| (AMS/scan) 27 On (power typically) 7
Appendix D: AMX Icon 2 Character Map Appendix D: AMX Icon 2 Character Map Overview Use the AMX Icon 2 font to use symbols instead of text for many standard transport and control functions, for use on engraved keypad buttons (FIG. 129).
Appendix D: AMX Icon 2 Character Map 202 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Appendix E: Supported Devices/Accessories by Type Appendix E: Supported Devices/Accessories by Type Supported Devices by Type Supported NetLinx Central Controllers Visual Architect v1.1 supports the following AMX NetLinx Central Controllers: • NI-700 • NI-2100 • NI-900 • NI-2100/ICS • NI-3100 • NI-2000 • NI-3000 • NI-4000 • NXI w/ NXC-ME260/64 • NI-4100 • NXF w/ NXC-ME260/64 • NI-3100/ICS All NetLinx Central Controllers require NetLinx Duet firmware. Supported AMX Keypads Visual Architect v1.
Appendix E: Supported Devices/Accessories by Type • NXF • NXC-COM2 • AXD-IR+ • NXF-MINI • NXC-VOL4 • AXR-IRSM+ • NXF-MHS • NXC-I/O10 • IRX-DM+ • NXS-NMS • NXC-REL10 • IRX-SM+ • NXC-NH • NXC-IRS4 • IRX-PP38 • NXC-HS • MIO-IRRX • PCS2 • NXC-HE • AXR-RF • VSS2 Supported AMX Remote Controllers Visual Architect v1.1 supports the following AMX Remotes. Mio R-1 Mio R-2 Supported AMX Media Devices Visual Architect v1.1 supports the following MAX by AMX Media Devices.
Appendix E: Supported Devices/Accessories by Type • Amplifier • Laser Disc Player • Switcher • Audio Conferencer • Lighting • Text Keypad • Audio Mixer • Mini Disc Player • TV • Audio Processor • Monitor • VCR • Camera • Motor • Video Conferencer • Cassette Deck • Multi-Window • Video Processor • CD Player/Changer • Other Disc Player • Video Projector • Digital Media Encoder • Pool/Spa • Video Wall • Digital Media Player • Power Controller (UPS) • Volume Controller • Digital Medi
Appendix E: Supported Devices/Accessories by Type Pole Mount Bracket NI-900 NI-2000 206 FG2105-09 FG2105-01 300 700 PMB FG531 $120 Rack Mount Kit AC-RK FG515 $80 2.8 amp Power Supply w/ Phoenix connector PSN2.8 FG423-17 $120 4.4 amp Power Supply w/ Phoenix connector PSN4.4 FG423-45 $150 6.5 amp Power Supply w/ Phoenix connector PSN6.
Appendix E: Supported Devices/Accessories by Type 6.5 amp Power Supply w/ Phoenix connector NI-2100/ICS NI-3000 NI-3100 FG2105-14 FG2105-02 FG2105-05 700 900 900 PSN6.5 FG423-41 $460 NetLinx IR Emitter Cable CC-NIRC FG10-000-11 $50 Serial to Screw Terminal Adapter STS FG959 $50 Serial Programming Cable CC-COM FG10-727 $50 2.8 amp Power Supply w/ Phoenix connector PSN2.8 FG423-17 $120 4.4 amp Power Supply w/ Phoenix connector PSN4.4 FG423-45 $150 6.
Appendix E: Supported Devices/Accessories by Type NI-4000 NI-4100 NXC-ME260/64 + NXI FG2105 FG2105-06 FG2010-64 + FG2101 900 + cards 900 + 4 cards 750 + 1090 NetLinx IR Emitter Cable CC-NIRC FG10-000-11 $50 Serial to Screw Terminal Adapter STS FG959 $50 Serial Programming Cable CC-COM FG10-727 $50 2.8 amp Power Supply w/ Phoenix connector PSN2.8 FG423-17 $120 4.4 amp Power Supply w/ Phoenix connector PSN4.4 FG423-45 $150 6.5 amp Power Supply w/ Phoenix connector PSN6.
Appendix E: Supported Devices/Accessories by Type Serial to Screw Terminal Adapter STS FG959 $50 Serial Programming Cable CC-COM FG10-727 $50 Supported AMX Accessories - Expansion Devices Product Model Product FG Power (mA) Accessory Description Accessory Model Accessory FG Accessory Additional MSRP Information NXF-MINI 25 + 4 cards 2.8 amp Power Supply w/ Phoenix connector PSN2.8 FG423-17 $120 4.4 amp Power Supply w/ Phoenix connector PSN4.4 FG423-45 $150 6.
Appendix E: Supported Devices/Accessories by Type Supported AMX Accessories - Remote Controllers Product Model Product FG Power (mA) MIO-R1 FG147 NA MIO-R2 FG147-418, FG147-433 NA Accessory Description Accessory Model Accessory FG Accessory MSRP Charging Cradle MIO-RCC FG147-02 $200 Charging Cradle Kit MIO-RCC-K FG147-03K $300 Battery Pack MIO-RBP FG147-10 $100 Custom Engraving MIO-R-EN FG147-01 $150 Charging Cradle MIO-RCC FG147-02 $200 Charging Cradle Kit MIO-RCC-K FG147
Appendix E: Supported Devices/Accessories by Type MIO-ELITE-S-sc MIO-ELITE-SL-sc MIO-ELITE-D-sc MIO-ELITE-DL-sc FG5796-01sc FG5796-03sc FG5796-02sc FG5796-04sc TBD TBD TBD TBD Set of 2 double buttons MIO-CLASSIC-DW-sc FG5795-22sc $40 Set of blank buttons MIO-CLASSIC-BB-sc FG5795-07sc $99 Accent Frame MIO-ACCCP-D-sc FG5795-09sc $80 Set of 4 single buttons MIO-ELITE-SW-sc FG5796-21sc $50 Set of 2 double buttons MIO-ELITE-DW-sc FG5796-22sc $40 Set of blank buttons MIO-ELITE-BB
Appendix E: Supported Devices/Accessories by Type Engraving for 2/4button sets MIO-ELITE-SL-dc MIO-ELITE-D-dc MIO-ELITE-DL-dc MIO-ELITE-S-mc FG5796-03dc FG5796-02dc FG5796-04dc TBD TBD TBD FG5796-01mc TBD Product Model Product FG MIO-ELITE-SL-mc FG5796-03mc TBD 212 MIO-ELITE-EN FG5796-50 $75 Set of 4 single buttons MIO-ELITE-SW-dc FG5796-21dc $50 Set of 2 double buttons MIO-ELITE-DW-dc FG5796-22dc $40 Set of blank buttons MIO-ELITE-BB-dc FG5796-07dc $99 Accent Frame MIO-ACC
Appendix E: Supported Devices/Accessories by Type Engraving for 2/4button sets MIO-ELITE-D-mc FG5796-02mc TBD MIO-ELITE-DL-mc FG5796-04mc TBD MIO-DMS-ac FG2408-01ac MIO-DMS-P-ac FG2408-02ac 525 525 MIO-ELITE-EN FG5796-50 $75 $50 Set of 4 single buttons MIO-ELITE-SW-cc FG5796-21cc Set of 2 double buttons MIO-ELITE-DW-cc FG5796-22cc $40 Set of blank buttons MIO-ELITE-BB-cc FG5796-07cc $99 Accent Frame MIO-ACCEL-D-cc FG5796-09cc $85 Engraving for full button set MIO-ELITE-D-EN
Appendix E: Supported Devices/Accessories by Type Wall Mount Docking Station - Silver FG5965-02 MVP-WDS-SL FG5965-21 $1,600 Kickstand MVP-KS FG5965-12 $320 Battery Pack MVP-BP FG5965-20 $350 Stylus Set of 3 MVP-STYLUS FG5965-30 $50 802.
Appendix E: Supported Devices/Accessories by Type NXT-CV7 FG2258-01K 1500 (TP), 1400 (BASE/1), TBD (WC-B), 460 (WC-G) Set of 2 bezels with buttons - beige NXA-BEZ-5B-BG FG2261-32 $160 Set of 2 bezels with buttons - light almond NXA-BEZ-5B-LA FG2261-33 $160 Set of 2 bezels without buttons- black NXA-BEZ-5NB-BL FG2261-40 $160 Set of 2 bezels without buttons - white NXA-BEZ-5NB-WH FG2261-41 $160 Set of 2 bezels without buttons - beige NXA-BEZ-5NB-BG FG2261-42 $160 Set of 2 bezels withou
Appendix E: Supported Devices/Accessories by Type NXT-CV10 FG2258-01K Product Model Product FG 216 1500 (TP), 1400 (BASE/1), TBD (WC-B), 460 (WC-G) Power (mA) Set of 2 bezels with buttons - beige NXA-BEZ-7B-BG FG2258-32 $160 Set of 2 bezels with buttons - light almond NXA-BEZ-7B-LA FG2258-33 $160 Set of 2 bezels without buttons - black NXA-BEZ-7NB-BL FG2258-40 $160 Set of 2 bezels without buttons - white NXA-BEZ-7NB-WH FG2258-41 $160 Set of 2 bezels without buttons - beige NXA-BEZ-7N
Appendix E: Supported Devices/Accessories by Type NXT-CV10/PB NXD-CV10 FG2258-03K FG2258-02K Product Model Product FG VisualArchitect v1.1 1500 (TP), 1400 (BASE/1), TBD (WC-B), 460 (WC-G) 1500, TBD (WC-B), 460 (WC-G) Power (mA) 4.4 amp Power Supply w/ Phoenix connector PSN4.4 FG423-45 $150 6.5 amp Power Supply w/ Phoenix connector PSN6.
Appendix E: Supported Devices/Accessories by Type NXT-CV12 NXT-1200V 218 FG2250-11K FG2250-60K 256MB Compact FLASH upgrade NXA-CFSP256M FG2116-37 $680 512MB Compact FLASH upgrade NXA-CFSP512M FG2116-38 $1,200 1GB Compact FLASH upgrade NXA-CFSP1GB FG2116-39 $1,998 802.11b wireless card NXA-WC80211B/CF FG2255-03 $258 802.11g wireless card NXA-WC80211G/CF FG2255-07 $280 PSN6.
Appendix E: Supported Devices/Accessories by Type NXT-1200 VGVideo NXD-1200 VGVideo FG2250-61V FG2251-61V Product Model Product FG NXT-1200 VGRGB 3500 (TP), 2700 (BASE/B) 3500 (TP), 575 (WC-G) Power (mA) FG2250-61RGB TBD (TP), 2700 (BASE/B) VisualArchitect v1.
Appendix E: Supported Devices/Accessories by Type NXD-1200 VGRGB NXT-CV15 220 FG2251-61RGB TBD (TP), 575 (WC-G) FG2250-11K 5100 (TP), 2700 (BASE/B) Audio/Video Breakout box NXA-AVB/RGB FG2254-11 INCL Rack Mount Kit for AVB AC-RK FG515 $80 256MB Compact FLASH upgrade NXA-CFTPV256M FG2116-43 $680 512MB Compact FLASH upgrade NXA-CFTPV512M FG2116-44 $1,200 1GB Compact FLASH upgrade NXA-CFTPV1GB FG2116-45 $1,998 Kensington Lock Bracket NXA-KLB FG2259-10 $145 Battery Base Kit NXA-B
Appendix E: Supported Devices/Accessories by Type NXD-1500 VGVideo NXT-1500 VGRGB FG2253-61V FG2252-61RGB TBD (TP), 2700 (BASE/B) Product Model Product FG NXD-1500 VGRGB 5500 (TP), 575 (WC-G) Power (mA) FG2253-61RGB TBD (TP), 575 (WC-G) VisualArchitect v1.
Appendix E: Supported Devices/Accessories by Type NXT-1700 VGVideo NXD-1700 VGVideo FG2252-61V FG2253-61V Product Model Product FG NXT-1700 VGRGB 222 TBD (TP), 2700 (BASE/B) TBD (TP), 575 (WC-G) Power (mA) FG2252-61RGB TBD (TP), 2700 (BASE/B) Rack Mount Kit for touch panel NXA-RK15 FG2904-51 VESA Mount Back Shell MB-TP15 FG032-50 $750 Conduit Box CB-TP15 FG032-10 $175 Audio/Video Breakout box NXA-AVB/RGB FG2254-11 INCL Rack Mount Kit for AVB AC-RK FG515 $80 256MB Compact FLASH
Appendix E: Supported Devices/Accessories by Type NXD-1700 VGRGB FG2253-61RGB TBD (TP), 575 (WC-G) VisualArchitect v1.
Appendix E: Supported Devices/Accessories by Type 224 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
Appendix F: The InConcert Resource Center Appendix F: The InConcert Resource Center InConcert Resource Center - Partner List Select Partner List in the InConcert Resource Center to display a list of manufacturers that participate in the InConcert program (FIG. 130). FIG. 130 InConcert Resource Center - Partner List You can use this page as a starting point for device searches: 1.
Appendix F: The InConcert Resource Center 4. Once you find the device that you're looking for, click on the Duet Module icon to open the Device Model Details dialog for that device. Use this dialog to view device specifications and download associated files, including the Duet Module (*JAR) file. InConcert Resource Center - Search Remote Controls Select Search Remote Controls in the InConcert Resource Center to access the Search fields shown in FIG. 132: FIG.
Appendix F: The InConcert Resource Center InConcert Resource Center - Voting / Request Select Voting/Request in the InConcert Resource Center to access the NetLinx Module Voting page shown in FIG. 134: FIG. 134 InConcert Resource Center - Voting / Request The options on this page allow you to vote for the NetLinx device modules that you would like to see developed and released by AMX, or request that a specific device module be developed.
Appendix F: The InConcert Resource Center 228 CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006 VisualArchitect v1.
VisualArchitect v1.
AMX. All rights reserved. AMX and the AMX logo are registered trademarks of AMX. AMX reserves the right to alter specifications without notice at any time. ©2006 033-004-2972 8/06 It’s Your World - Take Control™ 3000 RESEARCH DRIVE, RICHARDSON, TX 75082 USA • 800.222.0193 • 469.624.8000 • 469-624-7153 fax • 800.932.6993 technical support • www.amx.com CONFIDENTIAL AND PROPRIETARY.
