Skip to Content

Wiki source code of Keypad Configuration

Version 42.1 by Scott Kohlmann on 2023/04/21 14:04
Show last authors
1 {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 {{toc/}}
3 {{/box}}
4
5 (% class="row" %)
6 (((
7 The ShowRunnerCLC™ program includes several pre-built keypad types suitable for a wide variety of applications. In addition to standard keypad types, showrunner™ supports custom "X-Type" keypad configurations. Custom keypads can be configured from the ShowRunnerHUB™ Web Interface, or they can be manually added to the config and enabled using the XPanel Touchscreen interface. The [[ShowRunner™ Keypad Types >>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome]]page lists all the available built-in keypad types for the most common keypad models:
8
9 * [[Cameo Keypads>>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome||anchor="HCameoKeypads"]]
10 * [[Horizon Keypads>>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome||anchor="HHorizonKeypads"]]
11 * [[GLPPA-KP Keypads>>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome||anchor="HGLPPA-KPKeypads"]]
12 * [[Zūm Wired Keypads>>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome||anchor="HZūmWiredKeypads"]]
13 * [[Zūm Wireless Keypads>>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome||anchor="HZūmWirelessKeypads"]]
14
15 It is recommended to use built-in keypad types whenever possible, as configuring custom (X-Type) keypads is a more complex and time-consuming process. If custom keypad programming is required, there are several methods of configuring custom actions detailed in subsequent sections.
16 )))
17
18 (% class="row" %)
19 (((
20 = Keypad Configuration Options =
21
22 Keypads in ShowRunnerCLC™ can be configured using either the XPanel UI or the ShowRunnerHUB™ UI. Both user interfaces allow for enabling/disabling keypads, changing the keypad area assignment, and modifying the keypad type.
23
24 If a keypad is manually enabled or disabled through the Keypad Configuration menu, it will stay in that enabled or disabled state until something else (e.g. a scheduled event or a global action) occurs that changes its status. For this reason, it is only recommended to enable or disable keypads through the Keypad Configuration menu for testing purposes. During normal operation, keypads should be enabled and disabled using Scheduled Events. To prevent specific keypads from being disabled by scheduled events, check the "Disallow Disable" box.
25
26 Note that while it is possible to use the XPanel UI to change a keypad from a standard keypad type to a custom X-Type keypad, defining custom functions is only possible through the ShowRunnerHUB™ UI or by editing the configuration manually. X-Type keypads will perform any actions that are defined in the configuration. If no actions are defined for the keypad, then it will not perform any functions as an X-Type keypad. This means that correctly configured X-Type keypads can be changed into standard type keypads and then changed back into X-Type keypads without any loss of the custom functionality, but that standard type keypads cannot be changed into X-Type keypads without also configuring their custom actions using the ShowRunnerHUB™ UI or manually editing the configuration file.
27
28 == XPanel ==
29
30 The XPanel and touchscreen user interfaces can be used to configure standard keypad types. Custom keypad actions cannot be configured using the XPanel UI, and must be either manually added to the config file or configured using the ShowRunnerHUB™ UI.
31
32 To configure keypads using the XPanel or touchscreen:
33
34 * Enter the technician PIN code if required
35 * Tap the "Settings" gear icon in the top right of the screen
36 * Tap the "Keypad Configuration" button
37 * Select the desired keypad from the list of keypads on the left
38 * Edit the keypad attributes as desired
39 ** The Keypad Label can be edited from this menu
40 *** The Contractor Label still exists, but can only be edited through the ShowRunnerHUB™ UI or by manually editing the configuration file
41 ** The Area Assignment determines what areas and loads are controlled by standard type keypads
42 ** The Area Assignment also determines whether a scheduled event will change the keypad's behavior
43 *** The Ignore Disable checkbox allows excluding individual keypads from being disabled by scheduled events. Useful in situations where there are multiple keypads assigned to the same area, but only some of them need to be disabled during specific times of day
44 *** The Disable Off checkbox allows for using standard keypads with "Area Off" functionality (e.g. F-Type keypads) in front-of-house or otherwise public areas without fear of the lights being turned off by accident
45 ** The Keypad Type determines the keypad functionality
46 *** See the [[ShowRunner™ Keypad Types >>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome]]page for a list of standard keypad types
47 *** Some Keypad Types support direct loads (i.e. performing load-level actions rather than area-level actions), but they can only be edited through the ShowRunnerHUB™ UI or by manually editing the configuration file
48 *** Setting a keypad to "X-Type" allows the keypad to perform any previously configured custom actions, but these actions can only be configured through the ShowRunnerHUB™ UI or by manually editing the configuration file
49
50 == ShowRunnerHUB™ ==
51
52 The ShowRunnerHUB™ Web Interface can be used to configure both standard keypads as well as custom X-Type keypads. If an X-Type keypad was configured manually by editing the configuration file, then it might be missing some information that is required for the showrunnerHUB™ UI to be able to view and edit the keypad correctly. In these cases it is recommended to either continue editing the keypad manually using the configuration, or re-do the keypad customization with the showrunnerHUB™ UI in order to ensure that all the required information is generated.
53
54 Note that the ShowRunnerHUB™ UI performance on 3-Series processors can be slow, and it can require quite a bit of time for all the keypads, areas, loads, etc. to populate. If configuring a large number of keypads using the ShowRunnerHUB™ UI, it is recommended to load the configuration to a 4-Series processor running the same version of ShowRunnerCLC™ to make changes and then save/load that configuration to the 3-Series processor whenever possible.
55
56 To configure keypads using the ShowRunnerHUB™ UI:
57
58 * Log in to the web interface
59 * Click the "Setup" gear icon from the top right of the screen to navigate to the setup menu
60 * Click "Keypad Configuration" from the list on the left to bring up a list of keypads defined in the configuration
61 * Select the desired keypad from the list of keypads
62 * Edit the keypad attributes as desired
63 ** The Keypad Name/Keypad Label is what is displayed in the XPanel and touchscreen UI, while the Contractor Label is only visible in the configuration file or in this configuration menu
64 ** The Area Assignment determines what areas and loads are controlled by standard type keypads
65 ** The Area Assignment also determines whether a scheduled event will change the keypad's behavior
66 *** The Ignore Disable checkbox allows excluding individual keypads from being disabled by scheduled events. Useful in situations where there are multiple keypads assigned to the same area, but only some of them need to be disabled during specific times of day
67 *** The Disable Off checkbox allows for using standard keypads with "Area Off" functionality (e.g. F-Type keypads) in front-of-house or otherwise public areas without fear of the lights being turned off by accident
68 ** The Keypad Type determines the keypad functionality
69 *** See the [[ShowRunnerCLC™ Keypad Types >>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome]]page for a list of standard keypad types
70 *** Some Keypad Types support direct loads (i.e. performing load-level actions rather than area-level actions). Note that direct loads require saving the configuration and performing a progreset before they take effect.
71 *** Setting the keypad to "X-Type" brings up additional options for keypad customization and assigning custom keypad templates
72 *** Keypad logic can be verified by toggling on the "Simulate" function, selecting a type of interaction (Press, Tap, Double-Tap, or Hold), and then clicking on the buttons you wish to simulate
73 ** Detailed instructions on using the Keypad Configuration menu in the ShowRunnerHUB™ UI are available [[here>>attach:SHOWRUNNER™ Setup Guide.showrunnerHUB™.Keypad Configuration.WebHome@CI Keypad Editor UI Guide.pdf]]
74
75 The next section contains more detailed information regarding specific custom keypad functions and X-Type templates.
76
77 = Custom (X-Type) Keypad Configuration =
78
79 The ShowRunnerCLC™ X-Type keypad is a customizable keypad type available for Cameo, Horizon, GLPPA-KP, and Zūm Wired keypads. See[[ this document>>attach:SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome@showrunnerKeypadStyles.pdf]] for a list of possible keypad layouts for all keypad types. It is recommended to customize keypads using the ShowRunnerHUB™ UI whenever possible, as keypads which have been manually customized in the configuration will be missing certain attributes that are required to allow them to be subsequently editable from the ShowRunnerHUB™ UI.
80
81 == X-Type Templates ==
82
83 X-Type templates are a powerful tool available in ShowRunnerCLC™ that enable a technician to streamline configuring custom keypads on larger jobs. X-Type templates are similar to custom "standard" type keypads: once a custom template is created, it can be assigned to many different keypads and used to perform the same set of actions on different areas by simply re-mapping the template for each keypad.
84
85 Setting up custom keypads can be time consuming, as every action for every button for every keypad must be individually configured. If the types of functions (e.g. recall scene, toggle load 1, toggle load 2) are repeated across multiple keypads and the only thing that changes between them is the specific loads or areas being affected, then it is worthwhile to set up a template. Templates essentially allow a technician to configure a custom keypad one time, and then easily repeat it for multiple different keypads. When a keypad template is assigned to a keypad, all that is required is that the template be remapped so that it knows which areas, loads, etc. it is targeting for each keypad.
86
87 To create an X-Type template using the ShowRunnerHUB™ UI:
88
89 * Log in to the web interface
90 * Click the "Setup" gear icon from the top right of the screen to navigate to the setup menu
91 * Click "Keypad Configuration" from the list on the left to bring up a list of keypads defined in the configuration
92 * Select the first keypad that will be assigned a template
93 * Change the Keypad Type to "X-Type"
94 * Click the gear icon next to the "Keypad Template" field
95 * Click "ADD" underneath the "Keypad Templates" heading and name the template
96 * Once the template has been created, customize it as necessary
97 ** Use the Model field to create custom templates for C2N-CBD, HZ-KPCN, GLPPA-KP, or other types of keypads
98 ** Use the Style Picker button to select the desired button layout
99 ** Once the Model and Style are selected, click the Edit Actions button to define the template's actions
100 *** The Template Actions menu uses the same workflow as the X-Type Actions configuration menu 
101 **** Select a button
102 **** Give the button a descriptive label
103 **** Choose the required Button Model
104 **** Add actions for each interaction type on the button (Press, Tap, Double-Tap, Hold, or Release)
105 **** When adding an action to a button, you will be prompted to assign a number to the object.
106 ***** This number is known as the Host Global ID
107 ***** The Host Global ID is shown in the "[object] #" field. The name for this field updates depending on the type of object being targeted by the action (e.g. it will become "Load #" if the action is targeting loads)
108 ***** Do not repeat Host Global IDs within a template unless you intend for multiple buttons to target the same object
109 ****** E.g., if one button acts on an Area and another button acts on a Load, do not use "Area #: 1" and "Load #: 1" - instead, use "Area #:1" and "Load #: 2"
110 *** Once all the actions for all the buttons have been configured, exit back to the main Keypad Configuration menu
111 * To assign the template to a keypad, click the Keypad Template field and select the desired template
112 * Once a template is selected, click the map icon that appears next to the gear icon to open the Template Global Map menu
113 * Use the Template Global Map menu to assign specific objects to each custom keypad
114 ** The Type column indicates what type of object the template is expecting
115 *** By default, Host Global IDs are mapped to whatever object has a matching Global ID. These objects may or may note be the correct type of object for the template (e.g., a Host Global ID of 1 usually corresponds to a LoadController object)
116 ** Use the Object column to select the specific object to be mapped for this keypad
117 * Once the first keypad has been assigned the template and remapped:
118 ** Select the next keypad to be edited
119 ** Change the Keypad Type to "X-Type"
120 ** Select the custom template
121 ** Remap the Host Global IDs
122 ** Repeat for all keypads using the custom template
123 * Miscellaneous tips for configuring keypad templates:
124 ** Templates should be configured with the maximum number of loads/areas/etc. that any keypad will require, as excess generic objects can be skipped when mapping the template to specific keypads
125 *** E.g., if some keypads will have a button toggle 5 loads while others will have the same button toggle 7 loads, then the template should be defined to have 7 loads. Keypads which make use of all 7 loads will have all loads mapped, while the keypads that only require 5 loads should be mapped with "[Skip this Entry]" for the two extra loads
126 ** In certain situations, keypad templates can be used even if the actual keypad layout does not match the template
127 *** For example, a custom 4-button GLPPA-KP template can be used on a 2-button rocker GLPPA-KP as long as buttons 1 and 4 in the template do what is required. The extra functions assigned to buttons 2 and 3 do not matter because they can be skipped when mapping the template and the physical buttons cannot be pressed due to the rocker button cap
128
129 The table below contains a comprehensive list of possible actions for X-Type keypads (taken from the [[ShowRunnerCLC™ Keypad Types page>>SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome]]). The table was generated using ShowRunnerCLC™ version 3.019, but can be viewed for any version of ShowRunnerCLC™ by connecting to a processor running the desired version of ShowRunnerCLC™ and executing the command: ##sr sh ac##
130
131 Note that actions with "None" listed under "Triggers" are read-only and are only able to be used for keypad or keyswitch feedback, not for performing actions.
132
133 {{display excludeFirstHeading="false" reference="SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Keypad Types.WebHome" section="HX-TypeActionsTable"/}}
134 )))