Last modified by Alexander Mott on 2023/12/08 18:49

From version 18.1
edited by Alexander Mott
on 2023/03/28 16:47
Change comment: There is no comment for this version
To version 10.24
edited by Alexander Mott
on 2023/03/27 20:24
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -8,12 +8,10 @@
8 8  n/a
9 9  )))
10 10  
11 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
12 -{{toc/}}
13 -{{/box}}
14 -
15 15  (% class="row" %)
16 16  (((
13 +(% class="col-xs-12 col-sm-8" %)
14 +(((
17 17  Lorem
18 18  
19 19  See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
... ... @@ -23,6 +23,11 @@
23 23  
24 24  Lorem
25 25  
24 +== Ease of Start-Up ==
25 +
26 +
27 +Lorem
28 +
26 26  == Exclusive Features ==
27 27  
28 28  Lorem
... ... @@ -31,15 +31,6 @@
31 31  
32 32  Lorem
33 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 43  == Support and Continued Development ==
44 44  
45 45  Lorem
... ... @@ -46,184 +46,30 @@
46 46  
47 47  = Best Practices for Zūm Wired with SHOWRUNNER™ =
48 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.
43 +Though it is possible to design a Zūm Wired system to use the standard ZUM-HUB4 program and then import rooms from a separate processor running SHOWRUNNER, it is not recommended as the
50 50  
51 -Instead, to take full advantage of everything that SHOWRUNNER™ has to offer, follow these best practices:
45 += Feature Comparison Table =
52 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
47 +Lorem
48 +)))
55 55  
56 -Zūm
57 57  
58 -SHOWRUNNER™
51 +(% class="col-xs-12 col-sm-4" %)
52 +(((
53 +{{box title="**CONTENTS**"}}
54 +{{toc/}}
55 +{{/box}}
59 59  
60 -= Feature Comparison Tables =
61 -
62 -== SHOWRUNNER™ vs Default Program vs Standalone ==
63 -
64 -(% class="box errormessage" %)
57 +(% class="wikigeneratedid" id="HFigure1" %)
65 65  (((
66 -need to update this section
59 +[[image:Templates.Article.Template.WebHome@image1.jpg]]
60 +//Figure 1: [[Sea>>https://commons.wikimedia.org/wiki/File:Isle_of_Icacos_II.jpg]]//
67 67  )))
68 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)**
63 +(% class="wikigeneratedid" id="HFigure2" %)
64 +(((
65 +[[image:Templates.Article.Template.WebHome@image2.jpg]]
66 +//Figure 2: [[Waves>>https://commons.wikimedia.org/wiki/File:Culebra_-_Playa_de_Flamenco.jpg]]//
83 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 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 -== Out-of-the-Box vs App vs Default Program vs Custom Program ==
185 -
186 -Below is a Feature Comparison Table taken from the v3.05.02 Zūm Wired firmware release notes.
187 -
188 -(% class="table-condensed" %)
189 -|**Feature**|**Out of the Box Functionality**|(((
190 -**Zūm App**
191 -
192 -**(Standalone)**
193 -)))|(((
194 -**Networked**
195 -
196 -**(HUB4)**
197 -)))|**Custom Prog.**|**Notes**
198 -|Keypads|Scn recall / OFF|*|*|*|Affect all load controllers excluding Plug controllers
199 -|Presence detectors (Occ sensors)|Scn 1 / Scn 16|*|*|*|Presence detectors affect all load controllers
200 -|Programmable scenes| |✓|*|*|
201 -|Occupancy/Vacancy logic| |✓|*|*|
202 -|Daylight Harvesting| |✓|*|*|J-box analog input support only, ZUMLINK- Daylight sensor via custom programming only.
203 -|Customized Button Functions*
204 -(Tap/Double-Tap/ Hold)| |✓|*|*|none, Off, On, Toggle, Scene 1-16, Export button to Hub
205 -|Create a room configuration Template| |✓|*|*|
206 -|Apply room configuration template| |✓|✓| |Identical hardware rooms required
207 -|Universal 2-wire phase dimming up to 16A| |✓|*|*|ZUMLINK-EXP-DIMU support & Zūm App discovery/configuration
208 -|DALI addressing, Broadcast and groups
209 -support (Zūm Mode)| |✓|*|*|Allows control as Broadcast or 16 DALI Groups
210 -|Device Firmware updating via Zūm APP(BLE).| |✓| | |Requires primary controller at ver. 1.2.60
211 -|DALI addressing and DALI group support (CNET Mode)| | | |✓|Allows addressing, grouping and control of 16 Dali Groups using Simpl #, Simpl Windows
212 -|CNET / Zūm Mode Auto Switch| | | |✓|Automatically switches from CNET to Zum Mode when control system goes offline
213 -|Load shedding| | |✓|*|
214 -|Global/Multi/Cross-room KP| | |✓|*|Scenes, plug load and Occupancy enable/disable
215 -|Timeclock event triggers| | |✓|*|
216 -|DALI Type 6 TC| | | |✓|
217 -|DALI Type 8 TC| | | |✓|
218 -|Touch screen| | |*|✓|Hub4 support with mirror room modules
219 -|Shades| | | |✓|
220 -|AV integration| | |*|✓|Hub4 support with mirror room modules
221 -|Energy Monitoring| | | |✓|
222 -|(((
223 -Floor Map
224 -
225 -* denotes that can be used but not required to achieve functionality
226 -)))| | |*|✓|Hub4 support with mirror room modules
227 227  )))
228 -
229 -