User manual AMX ALD-H48 AMX NETWORK LIGHTING SOLUTION DIMMER INTERFACE

[. . . ] instruction manual ALD-H48 Network Lighting Solution Lighting Control AMX Limited Warranty and Disclaimer AMX Corporation warrants its products to be free of defects in material and workmanship under normal use for three (3) years from the date of purchase from AMX Corporation, with the following exceptions: · · · Electroluminescent and LCD Control Panels are warranted for three (3) years, except for the display and touch overlay components that are warranted for a period of one (1) year. Disk drive mechanisms, pan/tilt heads, power supplies, and MX Series products are warranted for a period of one (1) year. AMX Lighting products are guaranteed to switch on and off any load that is properly connected to our lighting products, as long as the AMX Lighting products are under warranty. AMX Corporation does guarantee the control of dimmable loads that are properly connected to our lighting products. [. . . ] 13 Interface between code and NetLinx module Some functionality in the device interface may not be implemented in the API interface. In cases where device functions are desired but not API supported, the PASSTHRU command may be used to send any and all device-protocol commands to the device. See the PASSTHRU command and the Adding Functions to Modules section on page 36 for more information. A sample UI module and a touch panel file are provided in the module package. These are not intended to cover every possible application, but can be expanded as needed to meet the requirements of a particular installation. ALD-H48 Lighting Controller 19 Advanced Programming Implementation To interface to the AMX Lutron_H48_Comm. jar module, you must: 1. Define the virtual device ID that the Lutron_H48_Comm. jar Duet module will use to communicate with the main program and User Interface. If a touch panel interface is needed, a touch panel file Lutron_H48. TP4 and module Lutron_H48_UI. axs have been created for testing. The NetLinx Lutron_H48_Comm. jar module must be included in the program with a DEFINE_MODULE command. This command starts execution of the module and passes in the following key information: the device ID of the H48 to be controlled, and the virtual device ID for communicating to the main program. An example of how to do this is shown below. DEFINE_DEVICE dvReal =0:5:0 dvTP =128:1:0 vdvLutron =41001:1:0 // The real H48 connected to the NetLinx IP port // The touch panel used for output /* The virtual device use for communication between the Comm module interface and User_Interface (UI) module interface. */ // Virtual device used by keypad 2. vdvKeypd2 =41001:2:0 DEFINE_VARIABLE VOLATILE DEV vdvArray[]={vdvLutron, vdvKeypd2} //Define arrays of button channels used on your own touch panel VOLATILE integer nButtons[]={1, 2, 3, 4, 5, 6, 7} DEFINE_START// Place define_module calls to the very end of the define_start section. // Comm module DEFINE_MODULE 'Lutron_H48_Comm' duet_code(vdvLutron, dvReal) // Touch panel module DEFINE_MODULE 'Lutron_H48_UI' ui_code(vdvArray, dvTP, nButtons) In order to establish a connection with the H48, the PROPERTY- command must be used to provide the Duet module with the correct IP to connect to, and the correct password needed to login. After the properties have been set, you must issue a REINIT to connect. Upon initialization the AMX Duet module will communicate with the H48 and information will be exchanged. 20 ALD-H48 Lighting Controller Advanced Programming Port Mapping This module uses multiple virtual devices in order distinguish events for one keypad from another. Port Mapping Virtual Device 41001:n:0 - {keypad n=1. . 24} Channels 1. . 24 & 101. . 124 Levels none Control PUSH RELEASE Feedback ON OFF FLASH Channel Assignment and Feedback While channel 251 is ON, the AMX system and the H48 are communicating. While channel 252 is ON, the Duet module has been initialized with the latest H48 data. Each keypad added to the keypad component list (see KEYPADADD-<index>, <addr> command) is controlled by turning a channel ON/OFF or by generating a button PUSH/RELEASE similar to a Netlinx native device. The virtual device you assign in your project will be used to accomplish this as follows: the virtual port number of your virtual device's D:P:S will represent the keypad number (1. . 24) and the channel will represent the keypad button (1. . 24). Most keypads, at this time, have a maximum of 10 LEDs, so LEDs 11 through 24 will not have a visual notification in this case, but they will have a virtual notification. Ports 1 through 24 and channels 1 through 24 on each port are used and cannot be changed. Example of use: Suppose you assign a virtual device number 41001:1:0 in your application code. All commands to and from the Duet code will use this virtual device as usual. [. . . ] This sample code should be used as a guide/code example for developing your own user interface. The Duet communication module will report the time every 1 minute as well as the date. If the AMX system is rebooted while connected and logged in to the H48, the TCP/IP link may need to timeout before another connection can be re-established by using the CONNECTcommand. If both the AMX system and the H48 are rebooted, then there is no timeout period. [. . . ]