Installation guide

Programming AMX Controllers for a Kaleidescape System
Page 20
5. Add a line to the program to call the Kaleidescape Multiple Panel Include file.
INCLUDE 'Kaleidescape Multiple Panel Include'
The module is configured with passed parameters and send_command commands
listed in the Kaleidescape Multiple Panel Include file.
Configuring the Kaleidescape Multiple Panel Include file
Use the following steps to configure the Kaleidescape Multiple Panel Include file.
1. Define virtual devices for all the zones to be controlled.
 A virtual device is usually required for each zone but it is not
necessary to configure unused zones.
 Verify again that the virtual devices used are not used anywhere
else in the program. Virtual devices that use ports other than the
first (i.e., 33001:2:0 or 33001:3:0) do not always behave properly when
used in an array as required by the Kaleidescape module.
 AMX recommends using virtual devices over 33000:1:0.
2. Modify the KTouchPanels array to include the touch panels that will be
controlling the zones in the Kaleidescape System.
3. Modify the controlledKplayers array to define which touch panel controls
which virtual device.
4. In the Set up interface section, modify or add send_command commands to
tell each virtual device which zone to control.
5. Instruct the module how to connect to the system by sending the IP
command to any ONE virtual device or by sending the RS-232 configuration
(baud rate) to any ONE virtual device.
6. For each defined SATP virtual device, set how many lines to use on the
interface.
7. For any keypad control, set the Preset ID or music collection to browse
through.
8. For the touch panels to change the zone controlled at runtime, either
comment in the appropriate code or create the necessary code to modify
the controlledKplayers array at runtime.
9. Save work, compile, and load the program to the processor.
Module version number
The module version number describes changes both internally and in the interface.
The version number of a module is presented in the following format:
(major).(minor).(patch)
The major version number changes indicate major changes, such as the removal
or addition of levels or channels to the module, and changes to the user interface.