Back to Corporate

General:

This module is used to control zones of whole house audio using Lutron keypads. Any keypad can control any zone of audio, and the audio state will be reflected on the keypads. For example, a ten button keypad with raise and lower buttons can control five lighting scenes and the other five buttons can control four audio sources and a mute/zone off/system off button. Four keypads in the same room can control the same zone of audio.

The raise and lower buttons will raise and lower a lighting scene if a lighting button has been pressed in the last seven seconds; otherwise, the raise and lower buttons will control the volume for the zone associated with the keypad. If the keypad's audio zone is on and the mute button is pressed, the button will flash to show mute status. If the button is pressed and held for two seconds, the zone will turn off. If the zone is off and the button is held for two seconds, the audio system will be shut off. Besides source selection, a source's 'Previous' and 'Next' can be defined by pressing a source button that is already on and pressing the raise or lower buttons.

All audio keypad properties are defined within a data file called, 'AudioKeypads.dat'. If the file does not already exist during boot up, it will be created in the 'LightKeypadData' directory. Comments within the file will explain the format for entering the properties. A good FTP Client program will make this part of the job a lot easier.

Prerequisites:

• General Function Library Include File
• Lighting Communication Module

Module Header:

Constraints:

1. Keypad button 17 must be programmed in the lighting system as Master Raise.
2. Keypad button 16 must be programmed in the lighting system as Master Lower.
3. Maximum of 48 audio keypads (any zone).
4. Maximum of 10 sources.
5. Mute/Off button must be the next button after the last source button.
6. The main program must handle messages from the module and provide status channels on dvInterface for each zone's source, mute, and room off status.
7. dvInterface must be an array of all audio locations available (in zone order) where each device in the array can represent a volume card or a virtual device.

The following dvInterface channels are for volume control from the module to the main program:

The following dvInterface channels are for status from the main program to the module. These will effect the LED state on the keypads:

Send_Commands (program to module):

•  '?' - This causes the module to display all supported commands via messages to the master.
• 'Ver' - Displays the compilation and version information for the module.
• 'Initialize' - Causes the data to be read and initialized. A channel on the virtual device for the module is pulsed when completed.
• 'Load_Data' - Reads the data from disk. A channel on the virtual device for the module is pulsed when completed.

Send_Strings (module to program):

• 'ON <zone>, <source kpd button>' - When a source keypad button  is selected to turn on a source (1 - 10).
• 'MUTE <zone>' - When mute toggle is requested.
• 'NEXT <zone>' - Perform a 'Next' feature on this zone's current source.
• 'PREV <zone>' - Perform a 'Previous' feature on this zone's current source.
• 'ROOM_OFF <zone>' - If this zone is on, turn this zone off. Otherwise, turn the system off.

API Calls Supported:

None

API Calls Returned:

None

Last Modified: 05/16/2008 08:20:14 PM