Working With the Device Database
29
VisualArchitect v1.1
CONFIDENTIAL AND PROPRIETARY. COPYRIGHT, AMX LLC, 2006
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 module-
supported. Module-supported devices have their basic IR codes captured within the module, so there is
no need to capture their IR codes.
To capture IR Codes, you'll need:
The hand control (remote controller) that is associated with the device.
An AMX IRIS IR Capture Unit, connected to your PC.
Use the options in the IR Code Capture and Management dialog to capture IR codes.
The basic steps in capturing IR Code include:
1.
Enter device information and select an IR template that matches the device type
2.
Select the IR functions you wish to capture, from a listing of all function supported by the device
3.
Set IR properties for this device
4.
Capture the IR codes from the device's hand controller
5.
Save the IRL file (
File > Save
) to a local directory.
6.
Update the Device Database to include the new IRL and XMD files.
IR Capture And Management Dialog
Select
IR Capture and Management
from either the File Menu, or the System Tree context menu to
access the IR Capture and Management dialog, where you can capture IR control codes from IR-
controlled devices (that do not already exist in the VA device database).
This dialog contains its own Menu Bar and Toolbar.
This dialog is divided in to three main sections (left-to-right):
Device Information window
: The Device Information window contains a set of text fields that allow
you enter information for the device that you are capturing IR codes for (FIG. 16):
Once you have captured a device's IR codes, they are added to the VA database as
an IR Capture (*.IRL) file, which will be available for other future projects.
When VA generates the IRL file, it also creates an *.XMD file to handle metadata for
this device. The XMD file is copied to the same location as the IRL file, and both files
must be present in the Device Database in order for this device to be represented in
the Devices tab of the Toolbox.
Содержание VISUALARCHITECT 1.1
Страница 12: ...x VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 Table of Contents ...
Страница 26: ...VisualArchitect v1 1 Overview 14 VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 ...
Страница 36: ...Creating a New VA Project 24 VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 ...
Страница 102: ...Setting Device Properties 90 VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 ...
Страница 106: ...Defining Control Strings 94 VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 ...
Страница 158: ...Finishing the Project 146 VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 ...
Страница 214: ...Appendix D AMX Icon 2 Character Map 202 VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 ...
Страница 240: ...Appendix F The InConcert Resource Center 228 VisualArchitect v1 1 CONFIDENTIAL AND PROPRIETARY COPYRIGHT AMX LLC 2006 ...
Страница 241: ...229 VisualArchitect v1 1 ...