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		-false
	1	+true

Content

...	...	@@ -2,35 +2,79 @@
2	2	(((
3	3	n/a
4	4	)))
	5	+
5	5	(% class="box warningmessage" %)
6	6	(((
7	7	n/a
8	8	)))
	10	+
9	9	{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
10	10	{{toc/}}
11	11	{{/box}}
	14	+
12	12	(% class="row" %)
13	13	(((
14	14	Lorem
15	15	See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
16	16	See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
17		-= The SHOWRUNNER™ Advantage =
	20	+
	21	+= Zūm Discovery =
	22	+
	23	+SHOWRUNNER™ includes a Zum 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 the Zum Rooms
	24	+
	25	+= SHOWRUNNER™ Complete Control =
	26	+
	27	+= Start-Up Guide =
	28	+
18	18	Lorem
19		-== Ease of Start-Up ==
20		-Lorem
21		-== Exclusive Features ==
22		-Lorem
23		-== Suitable for a Range of Applications ==
24		-Lorem
25		-== Support and Continued Development ==
26		-Lorem
27		-= Best Practices for Zūm Wired with SHOWRUNNER™ =
28		-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.
29		-Instead, to take full advantage of everything that SHOWRUNNER™ has to offer, follow these best practices:
30		-* Design the system to use SHOWRUNNER™ as the main program
31		-* Set ZUMNET-JBOX-* devices in CNET mode after any App-specific configurations have been made
32		-Zūm
33		-SHOWRUNNER™
34		-= Feature Comparison Table =
35		-Lorem
	30	+
	31	+(% class="box warningmessage" %)
	32	+(((
	33	+cross reference/update to old [[zumnet startup>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]?
	34	+
	35	+basic steps:
	36	+
	37	+* configure your processor per chief's startup guide
	38	+* get all zumnet jbox online
	39	+** use built in dhcp from processor control subnet
	40	+** if using proc without control subnet, use showrunner [[dhcp>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]
	41	+** (**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**)
	42	+* use crestron toolbox device discovery to create a [[Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]]
	43	+* use chief tools tm tool to generate various zum wired load scripts
	44	+** (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow)
	45	+** (will likely generate two versions of the loadscripts; one connecting by default hostname and one connecting by new hostname)
	46	+** (intend to require SR license for zwired LS generator, if only to get the proc mac address)
	47	+* if firmware is old, run "zwms master/zum (def. hostname)" loadscript to make all ZUMNET JBOX primary and in app mode in order to enable discovery of devices on zumlink
	48	+** devices will reboot
	49	+** per crestron, 1.0006.00012 and newer ship in primary mode (**tbd if they will ship in app mode?**)
	50	+* connect to a few devices in device discovery tool to ensure that all zumlink devices were automatically readdressed and there are no conflicting cids
	51	+** firmware 1.0001.00081 is new enough that this works correctly
	52	+* run "fw update (def. hostname)" loadscript to update the fw for all devices
	53	+** will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously
	54	+** devices will reboot, possibly multiple times
	55	+** 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)
	56	+* run device discovery again to confirm that all zumnet boxes were updated
	57	+** 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
	58	+* if app mode backup is desired, configure the boxes using the app now
	59	+* run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
	60	+** devices will reboot
	61	+** devices will now have new hostnames, so any further loadscripts should use (new hostname) versions
	62	+* run "cnet mode (def. hostname)" loadscript to put devices into CNET mode
	63	+** if app mode backup is desired, also run "autoswitch enable (def. hostname)" loadscript
	64	+** devices will reboot
	65	+* if using a processor without control subnet, run the "static ip config (new hostname)" script
	66	+** 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
	67	+** (**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**)
	68	+* once done, commission job essentially as normal showrunner job
	69	+** (**sr commissioning guide is incomplete**)
	70	+** connect to each zumnet jbox and address zumlink devices per the takeoff
	71	+*** if devices are not online, then troubleshoot why and update firmware through device tree view once they are online
	72	+** occ timeouts can be adjusted through UI; other settings (ie reach) should be adjusted through app
	73	+** photocells etc are set up through UI
	74	+** loads teseted and verified through UI; can be moved around between controllers as necessary
	75	+*** loads don't need to be in the same room as the zumnet that controls them
	76	+** keypads can use standard SR types or be fully customized
	77	+** set up schedule, etc.
	78	+* once done, save and back up configuration file
36	36	)))
	80	+)))