Changes for page **Starting Up Zūm Wired with SHOWRUNNER™

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Hidden

...	...	@@ -1,1 +1,1 @@
1		-true
	1	+false

Content

...	...	@@ -1,24 +1,22 @@
1		-({{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2		-{{toc/}}
3		-{{/box}}
4		-
5		-(% class="row" %)
	1	+(% class="box errormessage" %)
6	6	(((
7		-SHOWRUNNER™ provides
	3	+n/a
	4	+)))
8	8
9		-https://wiki.chiefintegrations.com/Design%20Guide/Hardware%20Design%20Guide/Crestron%20Zum%20Wired/Crestron%20Zum%20Wired%20Overview/
10		-
11		-= App Mode Zūm Discovery =
12		-(% class="box errormessage" %)
	6	+(% class="box warningmessage" %)
13	13	(((
14		-WARNING: Cresnet Discovery is not currently working on ZUMNET-JBOXs. Crestron has acknowledged a fix has been sent to QE. Discovery must be fixed before SHOWRUNNER™ can auto-discover hardware.
	8	+n/a
15	15	)))
16		-SHOWRUNNER™ includes a Zūm Wired Discovery feature that makes it easy to import Zūm Rooms that have been configured in App Mode into an existing SHOWRUNNER™ configuration. The process for starting up a system using this method is the same as starting up any other networked installation in App Mode, but with the added steps of installing SHOWRUNNER and importing Zūm Rooms into the configuration.
17		-Installing SHOWRUNNER™ onto various processors is covered on our [[startup pages>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Zūm Discovery.WebHome]], while importing rooms is covered on the [[Zūm Wired Discovery>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Zūm Discovery.WebHome]] page.
18	18
19		-https://wiki.chiefintegrations.com/SHOWRUNNER%E2%84%A2%20Setup%20Guide/SHOWRUNNER%E2%84%A2%20Installation%20Guide/SHOWRUNNER%E2%84%A2%20Installation%20and%20Network%20Setup/
	11	+{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
	12	+{{toc/}}
	13	+{{/box}}
20	20
21		-= (SHOWRUNNER™ Complete Control) =
	15	+(% class="row" %)
	16	+(((
	17	+Lorem
	18	+See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
	19	+See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
22	22
23	23	= Start-Up Guide =
24	24
...	...	@@ -26,15 +26,12 @@
26	26
27	27	(% class="box warningmessage" %)
28	28	(((
29		-cross reference/update to old [[zumnet startup>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]?
	27	+Basic steps:
30	30
31		-basic steps:
32		-
33	33	* configure your processor per chief's startup guide
34	34	* get all zumnet jbox online
35	35	** use built in dhcp from processor control subnet
36		-** if using proc without control subnet, use showrunner [[dhcp>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]
37		-** (**will probably need a lot of extra steps + alterations to how we make configs since static IPs require a lot more information as well as corresponding modifications to SrConfig.json**)
	32	+** if using proc without control subnet, use showrunner [[dhcp>>https://wiki.chiefintegrations.com/SHOWRUNNER%E2%84%A2%20Setup%20Guide/Troubleshooting%20Guide/Advanced%20Tools/DHCP%20Server/]]
38	38	* use crestron toolbox device discovery to create a [[Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]]
39	39	* use chief tools tm tool to generate various zum wired load scripts
40	40	** (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow)
...	...	@@ -49,28 +49,11 @@
49	49	** will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously
50	50	** devices will reboot, possibly multiple times
51	51	** check loadscript manager for any failures and re-run script for those devices if necessary (a rebooting zumnet box will temporarily disrupt online status for downstream zumnet jboxs and potentially interrupt the firmware update)
52		-* run device discovery again to confirm that all zumnet boxes were updated
53		-** zumnet boxes update last, so if a zumnet jbox is updated then this means that all of the zumlink devices that were online have also been updated
54		-* if app mode backup is desired, configure the boxes using the app now
55	55	* run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
56	56	** devices will reboot
57	57	** devices will now have new hostnames, so any further loadscripts should use (new hostname) versions
58		-* run "cnet mode (def. hostname)" loadscript to put devices into CNET mode
59		-** if app mode backup is desired, also run "autoswitch enable (def. hostname)" loadscript
60		-** devices will reboot
61	61	* if using a processor without control subnet, run the "static ip config (new hostname)" script
62	62	** this loadscript is necessary, as the showrunner DHCP server is only intended for commissioning. It must always be manually started after program restart and should not be used in production
63	63	** (**will probably need a lot of extra steps + alterations to how we make configs since static IPs require a lot more information as well as corresponding modifications to SrConfig.json**)
64		-* once done, commission job essentially as normal showrunner job
65		-** (**sr commissioning guide is incomplete**)
66		-** connect to each zumnet jbox and address zumlink devices per the takeoff
67		-*** if devices are not online, then troubleshoot why and update firmware through device tree view once they are online
68		-** occ timeouts can be adjusted through UI; other settings (ie reach) should be adjusted through app
69		-** photocells etc are set up through UI
70		-** loads teseted and verified through UI; can be moved around between controllers as necessary
71		-*** loads don't need to be in the same room as the zumnet that controls them
72		-** keypads can use standard SR types or be fully customized
73		-** set up schedule, etc.
74		-* once done, save and back up configuration file
75	75	)))
76	76	)))