Wiki source code of **Crestron Zūm Wired and SHOWRUNNER™

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

version	line-number	content
22.1	1	(% class="box successmessage" %)
	2	(((
	3	Page for showrunner feature comparison, reasons for using showrunner, etc.; should also include information from old
	4	)))
	5
1.1	6	(% class="box errormessage" %)
	7	(((
	8	n/a
	9	)))
3.1	10
1.1	11	(% class="box warningmessage" %)
	12	(((
	13	n/a
	14	)))
	15
11.1	16	{{box cssClass="floatinginfobox" title="CONTENTS"}}
	17	{{toc/}}
	18	{{/box}}
	19
1.1	20	(% class="row" %)
	21	(((
	22	Lorem
	23
6.1	24	See //[[Figure 1>>WebHome\|\|anchor="HFigure1"]]// for details.
	25	See //[[Figure 2>>WebHome\|\|anchor="HFigure2"]]// for details.
1.1	26
	27	= The SHOWRUNNER™ Advantage =
	28
	29	Lorem
	30
14.1	31	== Exclusive Features ==
7.1	32
	33	Lorem
	34
14.1	35	== Suitable for a Range of Applications ==
13.1	36
7.1	37	Lorem
	38
14.1	39	== Ease of Start-Up and Documentation ==
12.1	40
14.1	41	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:
15.1	42
14.1	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
12.1	45
14.1	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™.
12.1	47
7.1	48	== Support and Continued Development ==
	49
	50	Lorem
	51
10.2	52	= Best Practices for Zūm Wired with SHOWRUNNER™ =
	53
11.1	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.
10.2	55
11.1	56	Instead, to take full advantage of everything that SHOWRUNNER™ has to offer, follow these best practices:
1.1	57
11.1	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
1.1	60
11.1	61	Zūm
1.1	62
11.1	63	SHOWRUNNER™
1.1	64
16.1	65	= Feature Comparison Tables =
1.1	66
18.1	67	== SHOWRUNNER™ vs Default Program vs Standalone ==
15.1	68
18.1	69	(% class="box errormessage" %)
	70	(((
19.1	71	need to verify information is up to date for this section
18.1	72	)))
	73
16.1	74	The below table compares some SHOWRUNNER exclusive features against networked systems using the default program and standalone systems using Zūm App mode.
	75
	76	\|=Feature\|=(((
	77	Networked
	78
	79	(SHOWRUNNER™)
	80	)))\|=(((
	81	Networked
	82
	83	(HUB4)
	84	)))\|=(((
	85	Zūm App
	86
	87	(Standalone)
	88	)))
	89	\|(% colspan="4" %)Hardware Requirements
	90	\|Requires ZUMNET-JBOX-*\|Y\|Y\|N
17.1	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
16.1	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
	145	\|BACNET Features\|(((
	146	Per Area Status:
	147	Active Scene
	148	Occupied
	149	Occupancy Enabled
	150	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
	157	)))\|(((
	158	Per Room Status:
	159	Online
	160	On
	161	Occupied
	162	Daylighting Active
	163	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\|(((
	183	CNET Mode: 3.016
	184	ZUM Mode: TBD
	185	)))\|N/A\|N/A
	186	\|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
	188
20.1	189	=== Caveats ===
21.1	190
20.1	191	* 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.
21.1	196
20.1	197	=== FAQ: ===
21.1	198
20.1	199	* 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
16.1	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
15.1	208	(% class="table-condensed" %)
	209	\|Feature\|Out of the Box Functionality\|(((
	210	Zūm App
	211
	212	(Standalone)
	213	)))\|(((
	214	Networked
	215
	216	(HUB4)
	217	)))\|Custom Prog.\|Notes
	218	\|Keypads\|Scn recall / OFF\|\|\|*\|Affect all load controllers excluding Plug controllers
	219	\|Presence detectors (Occ sensors)\|Scn 1 / Scn 16\|\|\|*\|Presence detectors affect all load controllers
	220	\|Programmable scenes\| \|✓\|\|\|
	221	\|Occupancy/Vacancy logic\| \|✓\|\|\|
	222	\|Daylight Harvesting\| \|✓\|\|\|J-box analog input support only, ZUMLINK- Daylight sensor via custom programming only.
	223	\|Customized Button Functions*
	224	(Tap/Double-Tap/ Hold)\| \|✓\|\|\|none, Off, On, Toggle, Scene 1-16, Export button to Hub
	225	\|Create a room configuration Template\| \|✓\|\|\|
	226	\|Apply room configuration template\| \|✓\|✓\| \|Identical hardware rooms required
	227	\|Universal 2-wire phase dimming up to 16A\| \|✓\|\|\|ZUMLINK-EXP-DIMU support & Zūm App discovery/configuration
	228	\|DALI addressing, Broadcast and groups
	229	support (Zūm Mode)\| \|✓\|\|\|Allows control as Broadcast or 16 DALI Groups
	230	\|Device Firmware updating via Zūm APP(BLE).\| \|✓\| \| \|Requires primary controller at ver. 1.2.60
	231	\|DALI addressing and DALI group support (CNET Mode)\| \| \| \|✓\|Allows addressing, grouping and control of 16 Dali Groups using Simpl #, Simpl Windows
	232	\|CNET / Zūm Mode Auto Switch\| \| \| \|✓\|Automatically switches from CNET to Zum Mode when control system goes offline
	233	\|Load shedding\| \| \|✓\|*\|
	234	\|Global/Multi/Cross-room KP\| \| \|✓\|*\|Scenes, plug load and Occupancy enable/disable
	235	\|Timeclock event triggers\| \| \|✓\|*\|
	236	\|DALI Type 6 TC\| \| \| \|✓\|
	237	\|DALI Type 8 TC\| \| \| \|✓\|
	238	\|Touch screen\| \| \|*\|✓\|Hub4 support with mirror room modules
	239	\|Shades\| \| \| \|✓\|
	240	\|AV integration\| \| \|*\|✓\|Hub4 support with mirror room modules
	241	\|Energy Monitoring\| \| \| \|✓\|
	242	\|(((
	243	Floor Map
	244
	245	* denotes that can be used but not required to achieve functionality
	246	)))\| \| \|*\|✓\|Hub4 support with mirror room modules
1.1	247	)))
15.1	248
	249