Skip to Content
Version 21.1 by Alexander Mott on 2023/12/08 18:38
Show last authors
1 (% class="box errormessage" %)
2 (((
3 n/a
4 )))
5
6 (% class="box warningmessage" %)
7 (((
8 n/a
9 )))
10
11 {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
12 {{toc/}}
13 {{/box}}
14
15 (% class="row" %)
16 (((
17 Lorem
18
19 See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
20 See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
21
22 = The SHOWRUNNER™ Advantage =
23
24 Lorem
25
26 == Exclusive Features ==
27
28 Lorem
29
30 == Suitable for a Range of Applications ==
31
32 Lorem
33
34 == Ease of Start-Up and Documentation ==
35
36 Every SHOWRUNNER™ job comes with a number of Chief Tools™ to simplify the start-up process and enable Agents and Technicians to for networked Zūm Wired systems. These tools include:
37
38 * SRTakeoff spreadsheet provides the Technician with one location to view device addresses, record serial numbers, and track any issues discovered during start-up
39 * Zūm Wired Load Script generator enables technicians to easily create load scripts to streamline necessary configuration tasks based on the DeviceSummary.txt generated by Toolbox
40
41 See the [[Starting Up Zūm Wired with SHOWRUNNER™>>doc:Design Guide.Hardware Design Guide.Crestron Zum Wired.Crestron Zum Wired Overview.WebHome||anchor="HStart-UpGuide"]] page for more information on starting up Zūm Wired systems with SHOWRUNNER™.
42
43 == Support and Continued Development ==
44
45 Lorem
46
47 = Best Practices for Zūm Wired with SHOWRUNNER™ =
48
49 Though it is possible to design a Zūm Wired system to use the standard ZUM-HUB4 program and then import rooms from SHOWRUNNER™, it is not recommended as it adds the expense of a custom program without taking advantage of any of the added functionality that SHOWRUNNER™ has to offer.
50
51 Instead, to take full advantage of everything that SHOWRUNNER™ has to offer, follow these best practices:
52
53 * Design the system to use SHOWRUNNER™ as the main program
54 * Set ZUMNET-JBOX-* devices in CNET mode after any App-specific configurations have been made
55
56 Zūm
57
58 SHOWRUNNER™
59
60 = Feature Comparison Tables =
61
62 == SHOWRUNNER™ vs Default Program vs Standalone ==
63
64 (% class="box errormessage" %)
65 (((
66 need to verify information is up to date for this section
67 )))
68
69 The below table compares some SHOWRUNNER exclusive features against networked systems using the default program and standalone systems using Zūm App mode.
70
71 |=Feature|=(((
72 **Networked**
73
74 **(**SHOWRUNNER™**)**
75 )))|=(((
76 **Networked**
77
78 **(HUB4)**
79 )))|=(((
80 **Zūm App**
81
82 **(Standalone)**
83 )))
84 |(% colspan="4" %)**Hardware Requirements**
85 |Requires ZUMNET-JBOX-*|Y|Y|N
86 |Requires 3 or 4-Series Control System|Y (Can use a number of different 3 and 4-Series processors)|Y (Requires ZUM-HUB4)|N
87 |Requires Physical Presence in Room to Change Scenes|N|TBD|Y
88 |Maximum Rooms|TBD|1000|N/A
89 |(% colspan="4" %)**User Interfaces**
90 |Web Browser|(((
91 Crestron SmartGraphics XPanel
92 HTML5 UI
93 )))|HTML5 UI|N
94 |iOS/Android|Y, Crestron App (Paid Upgrade) or HTML5 UI (Device Web Browser)|N|Y*
95 |Touchscreens (Crestron TSW series)|Y|N|N
96 |(% colspan="4" %)**Features**
97 |Scene Recall|Y|Y|Y
98 |Override Fade Time for Scene Recall|Y|TBD|TBD
99 |Scene Save|Y|TBD|Y
100 |Load Control|Y|TBD|Y
101 |Demand Response|Y|Y|N
102 |Enable/Disable Occupancy|Y|Y|Y
103 |Override Occupancy Logic|Y|TBD|N
104 |Override|Y|TBD|N/A
105 |Plug Load On/Off|Y|Y|By Hardware
106 |Integration with Non-Zūm Crestron Hardware|Y|N|N
107 |Custom Zūm Keypad Programming|Y|TBD|Y, within the limits of the hardware
108 |New Feature Release Cycle|Aggressive|6-12 months|6-12 months
109 |Room Organization|(((
110 Organize According to Defined Nodes, multiple levels
111 Categorization to Filter by Tag
112 )))|Category/Room|(((
113 N/A
114 )))
115 |Room Discovery|Automatic Discovery of ZUMNET and ZUMLINK devices (Pending)|Automatic Discovery of ZUMNET and ZUMLINK devices|N/A
116 |Network Topology|(((
117 * Flat
118 * Single Handoff to LAN w/ Control Subnet
119 (Requires CP4N/AV4/PRO4)
120 )))|Single Handoff to LAN w/ Control Subnet|N/A
121 |Network Addressing|(((
122 * Manual
123 * Customer (DHCP or Manual)
124 * DHCP: Control Subnet (Requires CP4N/AV4/PRO4)
125 )))|Control Subnet|N/A
126 |Firmware Updates|PUF Tool
127 Automatic Support on Roadmap|Automatic, Internet Connection Required|N/A
128 |Floorplans|Y|N|N/A
129 |(% colspan="4" %)**Calendar/Scheduling**
130 |Logic Type|Event Driven
131 Profile Support (Under Development)|Pattern assigned to Category|N/A
132 |Astronomical Clock|Y|Y, Per Category|N/A
133 |Holidays|Pattern|Hard Coded|N/A
134 |Custom Patterns|Y, Advanced Scheduler License|N|N/A
135 |(% colspan="4" %)**Integrations**
136 |A/V Integration: API|Y|Limited|N/A
137 |A/V Integration: Crestron EISC|Y|N|N/A
138 |A/V Integration: RS-232|Y|TBD|N/A
139 |BACNET|Y, SHOWRUNNER™ and Crestron Licenses Needed|Y|N/A
140 |BACNET Features|(((
141 Per Area Status:
142 Active Scene
143 Occupied
144 Occupancy Enabled
145 Individual Load Level
146 Photocell Level (per Photocell)
147 Plug Loads Enabled
148 System:
149 Demand Response Enabled
150 System Wide Override (Panic/Emergency)
151 ~* More Features added upon request
152 )))|(((
153 Per Room Status:
154 Online
155 On
156 Occupied
157 Daylighting Active
158 Device Battery is Low
159 Plug Loads Enabled
160 Occupancy Sensor Enabled
161 Current Daylight Level
162 Active Scene
163 \\System:
164 Demand Response Enabled
165 )))|N/A
166 |BACNET Settings Scope
167 (What Points are Exposed)|Per Area|Global|N/A
168 |BACNET Points Supported|Depends on Crestron License and Hardware|1000|N/A
169 |Crestron Fusion|Y|N|N/A
170 |Export to Zūm Floor Hub|Y, Licensed|N/A|N/A
171 |GLPAC|Y|N|N/A
172 |System to System Link|Y|N|N/A
173 |Minimum ZUM-NET Firmware|(((
174 CNET Mode: ZUM-WIRED 1.02.10 puf
175 ZUM Mode: ZUM-WIRED 1.xx.xxx puf (Pending)
176 )))|See Crestron, expected to be v1.01|See Crestron, expected to be v1.01
177 |Minimum SHOWRUNNER™ Version|(((
178 CNET Mode: 3.016
179 ZUM Mode: TBD
180 )))|N/A|N/A
181 |ZWMS (Zum Wired Master/Slave Mode)|MASTER|MASTER|MASTER or SLAVE
182 |ZWMODE|CNET or ZUM (ZUM Support Pending official release from Crestron)|ZUM|ZUM
183
184 === Caveats ===
185
186 * Consult Chief Integrations to verify sequence of operations if there are any concerns.
187 * Additional caveats:
188 ** --Occupancy status is not reported to ShowRunner when ZUMNET/ZUMLINK JBOXs come online. This has been acknowledged as a bug by Crestron in firmware v1.001.054 and v1.00.009 and is pending a fix from Crestron.-- Fixed in 1.02.010 firmware and Device Database 200.150.002, ShowRunner 3.016 has been updated with these fixes from Crestron.
189 ** --Raw Occupancy reporting does not work. A delay of 5 seconds to 5 minutes between sensor vacancy and reported vacancy to ShowRunner. ShowRunner attempts to set 30 seconds (v3.003 to v3.009) or 5 seconds (v3.010 and later) but it is not always honored. This has been acknowledged as a bug by Crestron in firmware v1.001.054 and v1.00.009 and is pending a fix from Crestron.-- Fixed in 1.02.010 firmware and Device Database 200.150.002, ShowRunner 3.016 has been updated with these fixes from Crestron.
190 ** Cresnet Discovery is not working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE. Discovery must be fixed before ShowRunner can auto-discover hardware.
191
192 === FAQ: ===
193
194 * I want to have a single connection to the building and have all of my Crestron devices on the Control Subnet (same topology as a ZUM-FLOOR-HUB) and use ShowRunner™ Total Control?
195 //Use a CP4N in lieu of the ZUM-FLOOR-HUB. A DIN-AP4 is not required. Crestron can supply a DIN-EN-6X18 with CEN-SW-POE-16 and CP4N racked in a 2RU mount plus 3 DIN rails. [[See Design Details.>>doc:Design Guide.Hardware Design Guide.Crestron Zūm Wired.Design to co-locate a CP4N and CEN-SWPOE-16 in the Same DIN-EN Cabinet.WebHome]]//
196 * Do I need a Crestron BACnet license when using ShowRunner for BACnet integration?
197 //If over 50 BACnet points are needed then a license (SW-3SERIES-BACNET-50+) will be needed for each Crestron processor that will provide BACnet points to the BMS.//
198
199 == Out-of-the-Box vs App vs Default Program vs Custom Program ==
200
201 Below is a Feature Comparison Table taken from the v3.05.02 Zūm Wired firmware release notes.
202
203 (% class="table-condensed" %)
204 |**Feature**|**Out of the Box Functionality**|(((
205 **Zūm App**
206
207 **(Standalone)**
208 )))|(((
209 **Networked**
210
211 **(HUB4)**
212 )))|**Custom Prog.**|**Notes**
213 |Keypads|Scn recall / OFF|*|*|*|Affect all load controllers excluding Plug controllers
214 |Presence detectors (Occ sensors)|Scn 1 / Scn 16|*|*|*|Presence detectors affect all load controllers
215 |Programmable scenes| |✓|*|*|
216 |Occupancy/Vacancy logic| |✓|*|*|
217 |Daylight Harvesting| |✓|*|*|J-box analog input support only, ZUMLINK- Daylight sensor via custom programming only.
218 |Customized Button Functions*
219 (Tap/Double-Tap/ Hold)| |✓|*|*|none, Off, On, Toggle, Scene 1-16, Export button to Hub
220 |Create a room configuration Template| |✓|*|*|
221 |Apply room configuration template| |✓|✓| |Identical hardware rooms required
222 |Universal 2-wire phase dimming up to 16A| |✓|*|*|ZUMLINK-EXP-DIMU support & Zūm App discovery/configuration
223 |DALI addressing, Broadcast and groups
224 support (Zūm Mode)| |✓|*|*|Allows control as Broadcast or 16 DALI Groups
225 |Device Firmware updating via Zūm APP(BLE).| |✓| | |Requires primary controller at ver. 1.2.60
226 |DALI addressing and DALI group support (CNET Mode)| | | |✓|Allows addressing, grouping and control of 16 Dali Groups using Simpl #, Simpl Windows
227 |CNET / Zūm Mode Auto Switch| | | |✓|Automatically switches from CNET to Zum Mode when control system goes offline
228 |Load shedding| | |✓|*|
229 |Global/Multi/Cross-room KP| | |✓|*|Scenes, plug load and Occupancy enable/disable
230 |Timeclock event triggers| | |✓|*|
231 |DALI Type 6 TC| | | |✓|
232 |DALI Type 8 TC| | | |✓|
233 |Touch screen| | |*|✓|Hub4 support with mirror room modules
234 |Shades| | | |✓|
235 |AV integration| | |*|✓|Hub4 support with mirror room modules
236 |Energy Monitoring| | | |✓|
237 |(((
238 Floor Map
239
240 * denotes that can be used but not required to achieve functionality
241 )))| | |*|✓|Hub4 support with mirror room modules
242 )))
243
244