AMX VISUALARCHITECT 1.1, Руководство пользователя

Страница: 38 / 242

Working With the Device Database
26 VisualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
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.
For Non-IR Controlled (Ethernet, Modem, Serial and TCP/IP) Devices
Use the Control Strings Definition dialog to define control strings to control non-IR controlled devices,
and save the resulting Control Strings Definition (*.CSD) file to a directory included in the Search Paths
for the Device Database.
See Manually Adding Non-IR Controlled Devices to the Device Database for details.
Download a VA-compatible module file for the device from the InConcert Resource Center on
www.amx.com, and unzip the system files to a directory included in the Search Paths for the
Device Database.
See Adding Module-Supported Devices to the Device Database for details.
Adding IR Devices To The Device Database
VA uses a Device Database to populate the list of supported devices (displayed in the Devices tab of the
Toolbox).
In order for a device to be available for inclusion in your projects, it must be represented in the device
database with an IR Library (*.IRL) and an IR Metadata (*.XMD) file. Both files must be present in the
Device Database in order for the device to be listed in the Devices tab of the Toolbox.
There are two ways to approach adding an IR-controlled device to the Device Database:
Manually adding the device by capturing the IR Functions from device's remote controller,
using an AMX IRIS IR Capture Unit.
Downloading the device's IRL file from the InConcert Resource Center.
Either way, in order for any new devices to be represented in the Devices tab of the Toolbox (so that they
can be added to your System), the Device Database must be updated to include the new file(s), via the
Device Database Manager dialog.
If you use module-supported devices, the control information is already captured in
the Duet module associated with each device. For module-supported devices, you
only need to define macros to apply to the functions supported by each device/
module. VA requires Duet Module v1.7 or higher module files to support third-party
(controlled) devices.
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 end-
user to trigger several events from a single touch panel button. For example, a macro
could trigger a lighting scene, cause a projection screen to be lowered, power up a
DVD changer and other associated A/V equipment and set a particular volume level,
all from a single button event.
See Defining Device Macros (via CodeBuilder) for details.
Modules and IRLs/IRN files stored on media such as CDs cannot be added to the
device database.