**Crestron Zūm Wired and SHOWRUNNER™

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:

42

43

* SRTakeoff spreadsheet provides the Technician with one location to view device addresses, record serial numbers, and track any issues discovered during start-up

44

* 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

45

46

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™.

47

48

== Support and Continued Development ==

Lorem

= Best Practices for Zūm Wired with SHOWRUNNER™ =

53

54

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.

55

56

Instead, to take full advantage of everything that SHOWRUNNER™ has to offer, follow these best practices:

57

58

* Design the system to use SHOWRUNNER™ as the main program

59

* Set ZUMNET-JBOX-* devices in CNET mode after any App-specific configurations have been made

Zūm

SHOWRUNNER™

= Feature Comparison Tables =

66

67

== SHOWRUNNER™ vs Default Program vs Standalone ==

68

69

(% class="box errormessage" %)

70

(((

71

need to verify information is up to date for this section

72

)))

73

74

The below table compares some SHOWRUNNER exclusive features against networked systems using the default program and standalone systems using Zūm App mode.

|=Feature|=(((

**Networked**

**(**SHOWRUNNER™**)**

)))|=(((

**Networked**

**(HUB4)**

)))|=(((

**Zūm App**

**(Standalone)**

)))

|(% colspan="4" %)**Hardware Requirements**

90

|Requires ZUMNET-JBOX-*|Y|Y|N

91

|Requires 3 or 4-Series Control System|Y (Can use a number of different 3 and 4-Series processors)|Y (Requires ZUM-HUB4)|N

92

|Requires Physical Presence in Room to Change Scenes|N|TBD|Y

93

|Maximum Rooms|TBD|1000|N/A

94

|(% colspan="4" %)**User Interfaces**

95

|Web Browser|(((

96

Crestron SmartGraphics XPanel

97

HTML5 UI

98

)))|HTML5 UI|N

99

|iOS/Android|Y, Crestron App (Paid Upgrade) or HTML5 UI (Device Web Browser)|N|Y*

100

|Touchscreens (Crestron TSW series)|Y|N|N

101

|(% colspan="4" %)**Features**

102

|Scene Recall|Y|Y|Y

103

|Override Fade Time for Scene Recall|Y|TBD|TBD

104

|Scene Save|Y|TBD|Y

105

|Load Control|Y|TBD|Y

106

|Demand Response|Y|Y|N

107

|Enable/Disable Occupancy|Y|Y|Y

108

|Override Occupancy Logic|Y|TBD|N

109

|Override|Y|TBD|N/A

110

|Plug Load On/Off|Y|Y|By Hardware

111

|Integration with Non-Zūm Crestron Hardware|Y|N|N

112

|Custom Zūm Keypad Programming|Y|TBD|Y, within the limits of the hardware

113

|New Feature Release Cycle|Aggressive|6-12 months|6-12 months

114

|Room Organization|(((

115

Organize According to Defined Nodes, multiple levels

116

Categorization to Filter by Tag

117

)))|Category/Room|(((

118

N/A

119

)))

120

|Room Discovery|Automatic Discovery of ZUMNET and ZUMLINK devices (Pending)|Automatic Discovery of ZUMNET and ZUMLINK devices|N/A

121

|Network Topology|(((

122

* Flat

123

* Single Handoff to LAN w/ Control Subnet

124

(Requires CP4N/AV4/PRO4)

125

)))|Single Handoff to LAN w/ Control Subnet|N/A

126

|Network Addressing|(((

127

* Manual

128

* Customer (DHCP or Manual)

129

* DHCP: Control Subnet (Requires CP4N/AV4/PRO4)

130

)))|Control Subnet|N/A

131

|Firmware Updates|PUF Tool

132

Automatic Support on Roadmap|Automatic, Internet Connection Required|N/A

133

|Floorplans|Y|N|N/A

134

|(% colspan="4" %)**Calendar/Scheduling**

135

|Logic Type|Event Driven

136

Profile Support (Under Development)|Pattern assigned to Category|N/A

137

|Astronomical Clock|Y|Y, Per Category|N/A

138

|Holidays|Pattern|Hard Coded|N/A

139

|Custom Patterns|Y, Advanced Scheduler License|N|N/A

140

|(% colspan="4" %)**Integrations**

141

|A/V Integration: API|Y|Limited|N/A

142

|A/V Integration: Crestron EISC|Y|N|N/A

143

|A/V Integration: RS-232|Y|TBD|N/A

144

|BACNET|Y, SHOWRUNNER™ and Crestron Licenses Needed|Y|N/A

|BACNET Features|(((

Per Area Status:

Active Scene

Occupied

Occupancy Enabled

Individual Load Level

151

Photocell Level (per Photocell)

152

Plug Loads Enabled

153

System:

154

Demand Response Enabled

155

System Wide Override (Panic/Emergency)

156

~* More Features added upon request

)))|(((

Per Room Status:

Online

On

Occupied

Daylighting Active

Device Battery is Low

164

Plug Loads Enabled

165

Occupancy Sensor Enabled

166

Current Daylight Level

167

Active Scene

168

\\System:

169

Demand Response Enabled

170

)))|N/A

171

|BACNET Settings Scope

172

(What Points are Exposed)|Per Area|Global|N/A

173

|BACNET Points Supported|Depends on Crestron License and Hardware|1000|N/A

174

|Crestron Fusion|Y|N|N/A

175

|Export to Zūm Floor Hub|Y, Licensed|N/A|N/A

176

|GLPAC|Y|N|N/A

177

|System to System Link|Y|N|N/A

178

|Minimum ZUM-NET Firmware|(((

179

CNET Mode: ZUM-WIRED 1.02.10 puf

180

ZUM Mode: ZUM-WIRED 1.xx.xxx puf (Pending)

181

)))|See Crestron, expected to be v1.01|See Crestron, expected to be v1.01

182

|Minimum SHOWRUNNER™ Version|(((

CNET Mode: 3.016

ZUM Mode: TBD

)))|N/A|N/A

|ZWMS (Zum Wired Master/Slave Mode)|MASTER|MASTER|MASTER or SLAVE

187

|ZWMODE|CNET or ZUM (ZUM Support Pending official release from Crestron)|ZUM|ZUM

=== Caveats ===

* Consult Chief Integrations to verify sequence of operations if there are any concerns.

192

* Additional caveats:

193

** --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.

194

** --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.

195

** 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.

=== FAQ: ===

* 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?

200

//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]]//

201

* Do I need a Crestron BACnet license when using ShowRunner for BACnet integration?

202

//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.//

203

204

== Out-of-the-Box vs App vs Default Program vs Custom Program ==

205

206

Below is a Feature Comparison Table taken from the v3.05.02 Zūm Wired firmware release notes.

207

208

(% class="table-condensed" %)

209

|**Feature**|**Out of the Box Functionality**|(((

210