kaleidescape Programming AMX Controllers for a Kaleidescape System May 2015
Contents Who Should Use This Document 6 Getting Started with AMX 6 Overview of Kaleidescape Module and Templates 6 Touch Panels and Keypads 7 Touch panels 7 Touch panel variations 7 OSD control with a video window 7 OSD control without a video window 8 Standalone touch panel (SATP) control 9 Layout for touch panel user interface 10 Keypad control 11 Using Music Presets 11 Music items in the Kaleidescape System 12 Random and repeat 13 Tags and the Preset ID 13 Zones 14 Saving
Downloading and importing the Kaleidescape module for AMX 19 Configuring the Kaleidescape Multiple Panel Include file 20 Module version number 20 Updating the module 21 Verifying the module version 21 Connection methods 21 Command routing 23 Command routing using Control Protocol Device IDs (CPDID) 23 Command routing using serial number addressing 26 SATP setup 26 Keypad Setup 27 Calibrating the touch interface 27 Music zone control 28 Naming music zones 28 Controlling music zone
Setting the M500 Player and Music Player CPDIDs 38 Configuring the Kaleidescape Multiple Panel Include file 39 System Readiness 40 Screen masking 41 CinemaScape Mode 42 Lighting and shades 43 Enabling volume control from a Kaleidescape controller 43 Configuring an AMX controller for volume control when a player can only be used in one zone at a time or when messages will be triggered by IR 43 Configuring an AMX controller and the Kaleidescape App for iPad for volume control when a player can b
1U, 3U and 5U Servers RS-232 port pinouts 57 57 Appendix C: OSD Module v8.3 Channel Lineup 58 Appendix D: SATP Module v8.3 Channel Lineup 60 Appendix E: Keypad Module v8.3 Channel Lineup 63 Appendix F: Module v8.3 Level Lineup 64 Appendix G: Module v8.
Who Should Use This Document This document explains how to configure an AMX control system for a Kaleidescape System. Kaleidescape provides a module specifically designed for controlling Kaleidescape Systems using AMX controllers. The installer must be familiar with AMX NetLinx Studio, the NetLinx programming language, AMX Touch Panel Design (TPDesign4) software, and Kaleidescape products. This document revision corresponds to kOS version 6.1 and Kaleidescape AMX module version 8.4.0.
Touch Panels and Keypads Touch panels The Kaleidescape module uses the full screen on a touch panel and incorporates a large video window to provide complete consistency even when a separate video display is unavailable. Only the buttons required for a particular feature are displayed. For example, the keyboard is displayed only when alphanumeric input is required. After text entry is complete, the keyboard vanishes.
Figure 1: OSD control with a video window OSD control without a video window Instead of the video window, the OSD No Video template delivers text-based details for the content currently selected in the OSD. The touch panel replicates the movie details page or album details page for the selected movie or album in any OSD view. Use this variation only when the touch panel cannot support a video window or when the touch panel has too little area to display the OSD video image clearly.
Standalone touch panel (SATP) control The standalone touch panel (SATP) template provides control for music on touch panels in rooms without video displays, like hallways, dining rooms, and patios, or touch panels with display areas too small to support a large video window. This simple, text-based interface is a powerful browsing tool, ideal for small LCD displays (320 × 240 pixels).
Layout for touch panel user interface Figure 4 outlines the organization of the Kaleidescape touch panel user interface. This layout complements the Kaleidescape OSD and provides an intuitive method to control the Kaleidescape System. Using a consistent implementation of this grid layout across all panel sizes and control platforms improves overall system usability. Figure 4: Layout for touch panel user interface Selecting the Kaleidescape logo accesses the Kaleidescape menu.
Keypad control Keypad commands provide a method for controlling music playback from any zone on any Kaleidescape player without requiring control feedback. Although keypad commands were created for keypads, these commands can use any button-like input, a button on a keypad or touch panel, a motion sensor, or any other input device. Kaleidescape provides two different types of keypad commands.
Music items in the Kaleidescape System The Kaleidescape System treats several different music items as playable. Table 1 defines these items and the effect of the random and repeat settings on each item.
Random and repeat In the Kaleidescape System, some music items always play in random order and repeat. These music items include any genre, artist, composer, user-defined collection, and all music. When any of these items are saved to a preset and played, the item plays in random order starting with a random track. If the preset is selected again, a new random track plays. This behavior removes the requirement to use a next track button to skip a track within the selection.
Zones Presets are shared between all zones on all players in the system. A preset saved on one music zone can be used anywhere in the system. The zone number must be defined when setting up the virtual device. A single virtual device can control both an SATP interface as well as a set of keypads. See Programming on page 17 for more information.
Collection browsing A set of buttons can be programmed to browse through the items in a music collection. Any music collection (Albums by Artist, Albums by Title, Artists, Genres, Mix Albums, Classical Composers, Classical Works, New, or any user-defined collection) can be specified. The module provides three controls for browsing: first, next, and previous. These controls step through the collection in the order displayed on the OSD.
Item Description (of system contents) Alphabetical Sort Order New Most recently imported Album name albums. The time period for considering an album new can be set in the browser interface. User-defined Collection of any music items defined by the user Item name First Item First new album All in this collection As more music collections are added to the Kaleidescape System, the keypad commands are also able to browse the collections.
Programming Kaleidescape command protocol Kaleidescape System control is based on bidirectional ASCII string commands. All Kaleidescape components respond to commands from an AMX controller and provide feedback in ASCII format. Although understanding the details of Kaleidescape command protocol is not required for AMX programming, it is important to understand how these commands are routed in the Kaleidescape System.
the targeted zone by comparing the device ID of the response and the device IDs set in the program. If CPDIDs are used for command routing each Premiere line component being controlled must have a unique CPDID set in the browser interface. String examples: If CPDID 02 is used as the device ID, the PLAY command has the following format. '02/1/PLAY:',$0D If the Kaleidescape component’s serial number is used as the device ID, the PLAY command has the following format.
Kaleidescape module Kaleidescape provides a single control module for either standalone touch panel (SATP), onscreen display (OSD), or keypad controls. The Kaleidescape module is designed to control all zones in the Kaleidescape System via a single connection. Each playback zone is represented by a virtual device in the array passed to the module. To configure the zone controlled by each virtual device, use send commands in the Kaleidescape Multiple Panel Include file.
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.
The minor version number changes indicate changes to the internal behavior of the module or minor modifications to the interface. Changes in the minor version number indicate that the program might have to be modified when the program is updated. Changes to the patch number indicate that there are no outward changes to the module and updating the module should not require any program changes. Example If module version 9.0.0 is released and the version currently in use is 8.0.
Kaleidescape recommends using TCP/IP over Ethernet for control connection in most cases. TCP/IP over Ethernet offers several advantages over RS-232: Very high bandwidth compared to RS-232 Error detection and correction Standard Cat5/5e/6 cable and pinout (simple standard termination) usage Longer cable runs possible Only a single network port required No extra COM port cards needed Bandwidth can be a key issue, especially in multi-zone systems.
Command routing Command routing allows control of multiple Kaleidescape players with only one connection to the controller. This can be either a TCP/IP or an RS-232 connection to almost any player or server in the system. Although multiple controllers can make multiple connections to Kaleidescape players, it is usually unnecessary to define more than a single connection to the Kaleidescape System.
4. Click on the Settings button for the player. Figure 5: Component Settings button Click on Settings 5. Select the CONTROL tab from the Settings page. 6. Select the Control Protocol Device ID (None, 02 through 99) from the dropdown menu. Select None only if command routing is NOT used for this device as shown in the following figure. Figure 6: Control tab Select None 7. Click OK. The component does not have to be rebooted.
Figure 7: CPDID addressing example Within DEFINE_START, set each virtual device to control an individual movie or music zone, and set another virtual device to control the family room M500 Player via SATP: send_command send_command send_command send_command send_command send_command send_command send_command send_command KPLAYER1, KPLAYER2, KPLAYER3, KPLAYER4, KPLAYER5, KPLAYER6, KPLAYER7, KPLAYER8, KPLAYER9, 'ID 'ID 'ID 'ID 'ID 'ID 'ID 'ID 'ID 02' //Theater 03' //Kitchen 04' //Master Bedroom 05' //Fami
The 1U Server receives the command and routes the command to the Music Player (CPDID 06) over Ethernet. The Music Player identifies the Zone ID of the command and plays back music in zone 3. The response is directed through the 1U Server and the module sends feedback through the KPLAYER8 virtual device. Command routing using serial number addressing Every Kaleidescape component has a twelve-character alphanumeric serial number.
The number of lines to be displayed on the touch panel must be defined for every SATP virtual device. Define the number of lines using a send_command to the virtual device. send_command KPLAYER6, 'lines 16' The module allocates 16 lines for the touch panel. The lines command can be resent at any time, which is helpful if the same virtual device is accessed by different sized panels. Keypad Setup Keypad controls piggyback on the SATP virtual devices.
Music zone control Music zone control provides control for any music zone in a Premiere line system from the OSD for a movie zone. Setting the music zone control in the browser interface allows the user to select any zone from the movie zone onscreen display. Now Playing shows what is playing in the currently selected zone. Music zone control is not supported on Cinema One (2nd generation). Naming music zones Music zone names appear in the OSD to identify the controlled music zone.
Controlling music zones Use the following steps to set music zone control. 1. Open the browser interface using: http://my-kaleidescape/ (Windows) http://my-kaleidescape.local/ (Mac) 2. Select the SETTINGS tab as shown in Figure 9. 3. Select Any music zone in the system can be controlled from the onscreen display radio button. Figure 9: General Settings page Select Any music zone in the system can be controlled from the onscreen display 4. Click Save Changes.
Figure 10: Now Playing view When the user selects Control Zone, the Select Music Zone dialog box appears with all the available music zones in the system, labeled with the names assigned in the Kaleidescape browser interface. Figure 11: Select Music Zone dialog box If the OSD is not controlling the local zone when the user selects new music for playback, a reminder that control is for a different music zone will appear. The user then has the option to confirm playback or to select another music zone.
Controlling multiple players with multiple touch panels The Kaleidescape Multiple Panel Include file makes it easy to integrate multiple touch panels and Kaleidescape players into a system. These settings can be set at compile time and never changed or can be modified at run time by pressing buttons or using other programming logic.
The particular zone that the touch panel controls changes at runtime. When a touch panel connects to a virtual device, send the REFRESH command to instruct the module to resend page flips and text information.
Controlling the same zone with multiple virtual devices In some installations, it is necessary to control a single zone with multiple devices such as touch panels and remotes. This is especially useful for SATP control where a second virtual device can support touch panels with differing numbers of lines. The virtual devices can browse independently — a user can be searching among albums with the first device while another user can be viewing Now Playing information with a second virtual device.
With command routing, a serial connection can be made to one player and issue commands that route to a second player. Routed commands travel over the network to the second player. If the second player is in standby mode in this scenario, power on commands routed through the first player will not cause the second player to leave standby. In some situations, this limitation is not an issue. The Movie Player remembers the last power state, and resumes that last power state after a power outage.
When the ENTER STANDBY command is sent to Cinema One, the system responds with a DEVICE_POWER_STATE event message indicating the new power state and turns off the movie zone and first music zone. Similarly, Cinema One responds to the LEAVE STANDBY command by immediately returning to the fully powered-on state and sending another DEVICE_POWER_STATE message. Unlike the components listed in the previous section, Cinema One does not drop the TCP/IP connection when entering or leaving standby mode.
Sample Installation This section contains a step-by-step implementation of a sample installation that uses command routing, via TCP/IP over Ethernet. The following figure shows the layout of the sample installation. Figure 12: Layout for a sample Installation Theater The Theater has an NXT-1500VG touch panel with video capabilities. The theater contains a projector, an adjustable screen masking system, controlled lighting, and shades. The M500 Player will be controlled using the OSD Video template.
This installation requires a total of five virtual devices to be defined. Three for OSD control of the three M500 Players Two for two of the Music Player zones Music zone 1 from the Music Player is unused in this installation. The entire system is controlled with a single TCP/IP connection to the 1U Server. Assigning a static IP address for the 1U Server Kaleidescape components, by default, obtain IP addresses from a DHCP server.
Figure 13: Static IP address assignment under the NETWORK tab Select Use the following IP configuration 6. Select the Use the following IP configuration radio button. 7. Enter the IP Address, Subnet Mask, Default Gateway, and DNS Servers. This information is required for interactive BD-Live features of Blu-ray discs to operate correctly. 8. For M-Class players, select the radio button to allow or deny Internet access through BD-Live.
Figure 14: Control tab 4. Use the drop-down menu to change the Control Protocol Device ID for the component. 5. Click OK to save the change. 6. Repeat steps 2 to 5 for each component. Configuring the Kaleidescape Multiple Panel Include file Define these virtual devices in the Kaleidescape Multiple Panel Include file. Be sure each device is unique across the project.
2. Add the touch panels to the KTouchPanels array. dev KTouchPanels[] = { TP_Theater, TP_Family_Room, TP_Kitchen, TP_Bedroom, TP_Sunroom } 3. Define which touch panel controls which virtual device. integer controlledKplayer[] = { 1, //Theater TP to control KPLAYER_Theater 2, //Family Room TP to control KPLAYER_FamilyRoom 3, //Kitchen TP to control KPLAYER_Kitchen 4, //Bedroom TP to control KPLAYER_MusicZ3 5, //Sunroom TP to control KPLAYER_MusicZ4 } 4.
system-wide state; every player in the system will report the same system readiness state. An idle system will automatically exit idle mode when it receives LEAVE_IDLE_MODE, LEAVE_STANDBY, or any other user interaction. Level 35 can be used to provide feedback to the user that the Kaleidescape system is idle, warming up, or ready to be used.
case 3: { call 'MASK'('1.78') } //image is 1.78 (16x9) case 4: { call 'MASK'('1.85') } //image is 1.85 case 5: { call 'MASK'('2.35') } //image is 2.35 } } With this logic (and an appropriately written 'MASK' system call), an automated screen masking system is truly automated — the masking system changes dynamically to fit whatever content is played. CinemaScape Mode When CinemaScape is active in any mode, Level 33 is used to report the aspect ratio of the current video.
Lighting and shades In rooms that are primarily for movie watching, for example, the Theater and Family Room, it is a nice touch to turn down the lights when the movie starts, turn up the lights during intermission, and turn on the lights as the end credits roll. The Kaleidescape module provides a set of channels to control lighting.
Configuration Search for #DEFINE volumeByPlayer in the DEFINE_VARIABLE section of the Kaleidescape Multiple Panel Include. Remove the open and close comment symbols (/* and */) surrounding the code block. Enter the number of Kaleidescape players being controlled by the AMX controller in the constant numberOfPlayers. This should be the same as the number of virtual devices in the Kplayer array. In the example below two players are being controlled.
Programming Events When the AMX master receives a volume control message, it will pulse the standard AMX channel (unless an alternate channel has been defined as described above) for the command on the virtual device of the player that received the command. Button events for these channels can be created and used to trigger actions that can raise, lower, or mute the volume in the zone.
Mute feedback can be sent to Kaleidescape controllers that support feedback by turning on and off channel 26 of the player’s virtual device. The value in playerVolumeProperties[].muteStatus is sent in response to VOLUME_QUERY and should be set to reflect the mute state of the zone. CHANNEL_EVENT [KZone1, 26] { on: { on [KPLAYER1, 26] playerVolumeProperties[1].muteStatus = 1 } off: { off [KPLAYER1, 26] playerVolumeProperties[1].
Also in DEFINE_VARIABLE modify the KZones array to include the zones that can access the Kaleidescape players. dev KZones[] = { KZone1, KZone2, KZone3 } On each iPad, enter a controller zone name on the Kaleidescape page in the Settings app. Find #IF_DEFINED volumeByZone in DEFINE_START. For each iPad create a new element in the array controllerProperties; enter the controller zone name used on the iPad in .controllerZoneName and enter a default zone for the iPad to control in .zoneToControl.
Programming Events The zone being controlled by the Kaleidescape App for iPad can be changed by pulsing channels between 600 and 608 or by using the call Select Zone for Kaleidescape Controller in your zone selection code. The parameters that must be included in this call are the iPad ID, new zone number, volume level of the zone, and mute status of the zone.
Mute feedback can be sent to a Kaleidescape controller by turning channel 26 of the zone in KZones on and off, or using the call Send Mute Feedback to Kaleidescape Controller. These calls also store the volume level and mute state to send when the zone is changed or when the Kaleidescape App for iPad sends VOLUME_QUERY. Secondary SATP control After programming the controller in the sample installation, the owner decides to add a second SATP touch panel in the Bedroom, for example, an MVP-8400.
3. If using an RS-232 connection and a message appears indicating the Kaleidescape module is sending the command "01/0/GET_DEVICE_POWER_STATE:" every 20 seconds, it means the module is not receiving responses from the Kaleidescape System and is in an initialization loop. Verify cable connections and pinouts (usually a cross-over cable).
Cannot make selections with a touch panel with a video window The Kaleidescape movie zone touch panel interface might not be calibrated correctly. See Calibrating the touch interface on page 27. No video on the touch panel with a video window 1. If using S-Video, verify that the Y and C connections are not reversed. (Try reversing connections to be sure.) 2. Verify that the touch panel video input is set correctly. In the console, type send_command , 'setup' to put the panel into setup mode.
Appendix A: Screen Shots for UI Layouts OSD control with a video window — Music Programming AMX Controllers for a Kaleidescape System Page 52
OSD control with a video window — Movies Music can be playing while selecting a movie to watch. The playback status box in the lower left corner feeds back either movie or music information. Programming AMX Controllers for a Kaleidescape System This layout shows the keyboard pop-up after selecting the SEARCH… button.
OSD control without a video window — Music Programming AMX Controllers for a Kaleidescape System Page 54
OSD control without a video window — Movies This layout shows the keyboard pop-up after selecting the SEARCH… button. Programming AMX Controllers for a Kaleidescape System Music can be playing while selecting a movie. The playback status box in the lower left corner feeds back either movie or music information.
Standalone touch panel Programming AMX Controllers for a Kaleidescape System Page 56
Appendix B: RS-232 Port Configuration and Cable Pinout Port configuration M500 Player, Music Player and Cinema One (1st generation) If the RS-232 port is used to communicate with a Kaleidescape player or Cinema One, use the following default communication parameters: Baud rate Data bits Stop bits Parity Flow control 19200 8 1 N N RS-232 communication parameters can be changed on the installer pages of the browser interface.
Appendix C: OSD Module v8.4 Channel Lineup All feedback channels are offset by 1000. For example, during playback channel 1001 is on (PLAY feedback) and when playback stops, channel 1002 is on (STOP feedback).
43 unused 73 COLLECTIONS 44 DISC MENU 74 PARENTAL CONTROL 45 UP 75 SYSTEM STATUS 46 DOWN 76 DEMO 47 LEFT 77 DEMO LOOP (replaced) 48 RIGHT 78 SCREEN SAVER 49 OK 79 SCREEN SAVER STOP 50 CANCEL 80 51 TOP MENU 52 CHAPTER ENTRY (Same as 32) 53 CLEAR DISC OR KALEIDESCAPE MENU (Shows disc menu in playback or Kaleidescape menu otherwise. Designed for oneway small panels or remotes.
Appendix D: SATP Module v8.4 Channel Lineup All channels up to channel 49 are the same as the OSD channel lineup. All feedback is shown offset by 1000. For example, during playback channel 1001 is on (PLAY feedback) and when playback stops, channel 1002 is on (STOP feedback).
41 unused 71 LIST LINE 11 42 unused 72 LIST LINE 12 43 unused 73 LIST LINE 13 44 DISC MENU (Future use) 74 LIST LINE 14 45 UP (Future use) 75 LIST LINE 15 46 DOWN (Future use) 76 LIST LINE 16 47 LEFT (Future use) 77 LIST LINE 17 48 RIGHT (Future use) 78 LIST LINE 18 49 OK (Future use) 79 LIST LINE 19 50 FIRST LIST COMMAND 80 LIST LINE 20 51 LIST KEYB CANCEL 81 LIST BACK 52 LIST KEYB ENTER 82 LIST UP 53 LIST KEYB SPACE 83 LIST DOWN 54 LIST KEYB BACKSPACE
101 LINE 1 STATUS (f/b only) 111 LINE 11 STATUS (f/b only) 102 LINE 2 STATUS (f/b only) 112 LINE 12 STATUS (f/b only) 103 LINE 3 STATUS (f/b only) 113 LINE 13 STATUS (f/b only) 104 LINE 4 STATUS (f/b only) 114 LINE 14 STATUS (f/b only) 105 LINE 5 STATUS (f/b only) 115 LINE 15 STATUS (f/b only) 106 LINE 6 STATUS (f/b only) 116 LINE 16 STATUS (f/b only) 107 LINE 7 STATUS (f/b only) 117 LINE 17 STATUS (f/b only) 108 LINE 8 STATUS (f/b only) 118 LINE 18 STATUS (f/b only) 109 LIN
Appendix E: Keypad Module v8.4 Channel Lineup All channels piggyback on the SATP channel lineup. All feedback channels are offset by 1000. For example, when Preset 1 is activated, channel 1121 turns on (Preset 1 feedback) and when playback stops, channel 1121 turns off.
Appendix F: Module v8.4 Level Lineup Except where noted, these values are set by the module and are used for feedback. 1 MOVIE LOCATION RELATIVE (For the progress bar) 12 MASK TRIM TOP (Percentage adjustment for the top) 2 unused 13 MASK TRIM BOTTOM (Percentage adjustment for the bottom) 3 unused 14 4 SCROLL BAR COMMAND (For the SATP scroll bar, sent to the module) MASK CONSERVATIVE (Uses the same values as 11. Using this level instead of 11 ensures that the mask never covers any light.
21 22 VIDEO MODE COMPONENT 0) no output 1) 480i60 4×3 NTSC 2) 480i60 16×9 3) 480p60 4×3 4) 480p60 16×9 5) 576i50 4×3 PAL 6) 576i50 16×9 7) 576p50 4×3 8) 576p50 16×9 9) 720p60 NTSC HD 10) 720p50 PAL HD 11) 1080i60 16x9 12) 1080i50 16x9 13) 1080p60 16x9 14) 1080p50 16x9 15) Reserved 16) Reserved 17) 1080p24 16x9 18) Reserved 19) 1080i60 64x27 20) 1080i50 64x27 21) 1080p60 64x27 22) 1080p50 64x27 23) 1080p24 64x27 24) Reserved 33 CINEMASCAPE MASK (A three digit 0 padded number describing the CinemaScape as
Appendix G: Module v8.4 Commands All of the commands in this appendix are sent to a virtual device passed to the module. The commands can be sent in the Kaleidescape Multiple Panel Include file, in a program or even from the text console. All commands are case-insensitive. Syntax send_command ' []' Any command sent to the module not listed below is forwarded directly to the corresponding Kaleidescape zone as a protocol command.
IP Use to set the IP address that the module should connect to. This command can be sent to any one of the defined virtual devices, but should only be sent ONCE in the entire program. Syntax 'IP
' Example 'IP 192.168.1.10' Set Baud Use to set the baud rate that the module should send to the RS-232 port when coming online. This command can be sent to any one of the defined virtual devices but should only be sent ONCE in the entire program.Example 'A' '4' '.' ' ' //send //send //send //send the letter A the number 4 a period a space character The [ character cannot be sent as a single character. If needed, send as a single predictive text character, [[]. [] Use to send a predictive text character. When using SATP search, this command sends a character group to use for predictive text. This group is used by the zone to match results. Sending [AB] causes the zone to show anything starting with A or B.
Collection Used to indicate which music collection to cycle through when the collection first/next/previous channels are triggered. Syntax 'Collection ' collection number is a number from 1 to 3 to indicate which set of buttons to use. collection name is the name of the collection to control.
Syntax 'Lines ' Example 'Lines 16' //16 line interface (large TP) 'Lines 8' //8 line interface (smaller TP) Max Preset Use to indicate the number of presets to cycle through when using the preset next and preset previous commands. When this preset index is reached in the cycle, another press of the next preset command returns to the first preset. When at the first preset, a previous preset command switches to the preset with the index that corresponds to the value set with this command.
Refresh Use to resend all the strings through the virtual device. This command is used to repopulate all strings on a touch panel that was either offline or previously not controlling this virtual device. This command also sends any page change strings to bring the panel in sync with the OSD.
Appendix H: Revision History Version 8.4.0 Added support for using serial numbers as control IDs Added support for SYSTEM_READINESS_STATE. Version 8.3.0 Added support for controller zone names in volume messages from the Kaleidescape app for iPad. Added support for SCALE MODE Removed port connection logic from DEFINE_PROGRAM and added support for a connection handling popup Minor performance enhancements and bug fixes. Version 8.2.0 Added support for video modes above 1080i.
Better handling of component power states and IP connection issues. Added feedback for the power state. Virtual device channels 1027 (power on feedback) and 1028 (power off feedback) now reflect the component power state. The SATP search button is now suppressed on top Browse node. Searching on the top node is not supported. Better handling of an invalid SATP node. If an SATP interface is showing a collection while the collection is deleted, the interface will correctly move to a valid node.
Modified nomenclature inside the module to clarify the browse protocol implementation. Fixed lighting event channel feedback IDs in the multiple panel Kaleidescape Multiple Panel Include file. Version 6.2.0 Modified coding style of module to reflect a single consistent style. Modified many channel and variable names to clarify their purpose and use a consistent style. Fixed bug where the module would not properly initialize if using command routing.
Notices Document Name: Programming AMX Controllers for a Kaleidescape System Document Number: 101-0123-00 Publication Date: May 2015 This document revision corresponds to kOS version 6.1 and Kaleidescape AMX module version 8.4.0. This document is for informational purposes only.
