Last modified by Alexander Mott on 2023/12/13 19:15
From version 8.2
edited by Alexander Mott
on 2023/03/29 21:30
Change comment: There is no comment for this version
To version 5.1
edited by Alexander Mott
on 2023/03/28 17:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,13 @@
1 +(% class="box errormessage" %)
2 +(((
3 +n/a
4 +)))
5 +
6 +(% class="box warningmessage" %)
7 +(((
8 +n/a
9 +)))
10 +
1 1  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 2  {{toc/}}
3 3  {{/box}}
... ... @@ -4,21 +4,10 @@
4 4  
5 5  (% class="row" %)
6 6  (((
7 -SHOWRUNNER™ provides a number of benefits over using the default program. These benefits are covered in detail on our [[Crestron Zūm Wired and SHOWRUNNER™>>doc:Design Guide.Hardware Design Guide.Crestron Zum Wired.Crestron Zum Wired Overview.WebHome]], but one of the largest benefits are the tools included with SHOWRUNNER™ to make Zūm Wired start-ups go as smoothly as possible.
17 +Lorem
18 +See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
19 +See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
8 8  
9 -
10 -(% class="box errormessage" %)
11 -(((
12 -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.
13 -)))
14 -
15 -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.
16 -Installing SHOWRUNNER™ on different processors is covered in our [[startup pages>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]], while importing Zūm Rooms is covered in the [[Zūm Wired Discovery>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Zūm Discovery.WebHome]] page.
17 -
18 -= CNET Mode (SHOWRUNNER™ Total Control) =
19 -
20 -= Tools for Processors without a Control Subnet =
21 -
22 22  = Start-Up Guide =
23 23  
24 24  Lorem
... ... @@ -48,22 +48,14 @@
48 48  ** will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously
49 49  ** devices will reboot, possibly multiple times
50 50  ** 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)
51 -* run device discovery again to confirm that all zumnet boxes were updated
52 -** 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
53 -* if app mode backup is desired, configure the boxes using the app now
54 54  * run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
55 55  ** devices will reboot
56 56  ** devices will now have new hostnames, so any further loadscripts should use (new hostname) versions
57 -* run "cnet mode (def. hostname)" loadscript to put devices into CNET mode
58 -** if app mode backup is desired, also run "autoswitch enable (def. hostname)" loadscript
59 -** devices will reboot
60 60  * if using a processor without control subnet, run the "static ip config (new hostname)" script
61 61  ** 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
62 62  ** (**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**)
63 63  * once done, commission job essentially as normal showrunner job
64 64  ** (**sr commissioning guide is incomplete**)
65 -** connect to each zumnet jbox and address zumlink devices per the takeoff
66 -*** if devices are not online, then troubleshoot why and update firmware through device tree view once they are online
67 67  ** occ timeouts can be adjusted through UI; other settings (ie reach) should be adjusted through app
68 68  ** photocells etc are set up through UI
69 69  ** loads teseted and verified through UI; can be moved around between controllers as necessary
... ... @@ -70,6 +70,5 @@
70 70  *** loads don't need to be in the same room as the zumnet that controls them
71 71  ** keypads can use standard SR types or be fully customized
72 72  ** set up schedule, etc.
73 -* once done, save and back up configuration file
74 74  )))
75 75  )))