Last modified by Alexander Mott on 2023/12/13 19:15
From version 14.1
edited by Alexander Mott
on 2023/03/29 23:14
Change comment: Uploaded new attachment "1680131684799-737.png", version {1}
To version 1.1
edited by Alexander Mott
on 2023/03/27 21:28
Change comment: There is no comment for this version

Summary

Details

Page properties
Hidden
... ... @@ -1,1 +1,1 @@
1 -true
1 +false
Content
... ... @@ -1,86 +1,36 @@
1 +(% class="box errormessage" %)
2 +(((
3 +n/a
4 +)))
5 +(% class="box warningmessage" %)
6 +(((
7 +n/a
8 +)))
1 1  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 2  {{toc/}}
3 3  {{/box}}
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.
8 -
9 -= App Mode (Zūm Discovery) =
10 -
11 -(% class="box errormessage" %)
12 -(((
13 -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.
14 -)))
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™ 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.
18 -
19 -= CNET Mode (SHOWRUNNER™ Total Control) =
20 -
21 21  Lorem
22 -
23 -(% class="box warningmessage" %)
24 -(((
25 -cross reference/update to old [[zumnet startup>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]?
26 -
27 -basic steps:
28 -
29 -* configure your processor per chief's startup guide
30 -* get all zumnet jbox online
31 -** use built in dhcp from processor control subnet
32 -** if using proc without control subnet, use showrunner [[dhcp>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]
33 -** (**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**)
34 -* use crestron toolbox device discovery to create a [[Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]]
35 -* use chief tools tm tool to generate various zum wired load scripts
36 -** (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow)
37 -** (will likely generate two versions of the loadscripts; one connecting by default hostname and one connecting by new hostname)
38 -** (intend to require SR license for zwired LS generator, if only to get the proc mac address)
39 -* 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
40 -** devices will reboot
41 -** per crestron, 1.0006.00012 and newer ship in primary mode (**tbd if they will ship in app mode?**)
42 -* connect to a few devices in device discovery tool to ensure that all zumlink devices were automatically readdressed and there are no conflicting cids
43 -** firmware 1.0001.00081 is new enough that this works correctly
44 -* run "fw update (def. hostname)" loadscript to update the fw for all devices
45 -** will take up to several minutes per room, but will be able to do up to 10 rooms simultaneously
46 -** devices will reboot, possibly multiple times
47 -** 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)
48 -* run device discovery again to confirm that all zumnet boxes were updated
49 -** 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
50 -* if app mode backup is desired, configure the boxes using the app now
51 -* run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
52 -** devices will reboot
53 -** devices will now have new hostnames, so any further loadscripts should use (new hostname) versions
54 -* run "cnet mode (def. hostname)" loadscript to put devices into CNET mode
55 -** if app mode backup is desired, also run "autoswitch enable (def. hostname)" loadscript
56 -** devices will reboot
57 -* if using a processor without control subnet, run the "static ip config (new hostname)" script
58 -** 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
59 -** (**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**)
60 -* once done, commission job essentially as normal showrunner job
61 -** (**sr commissioning guide is incomplete**)
62 -** connect to each zumnet jbox and address zumlink devices per the takeoff
63 -*** if devices are not online, then troubleshoot why and update firmware through device tree view once they are online
64 -** occ timeouts can be adjusted through UI; other settings (ie reach) should be adjusted through app
65 -** photocells etc are set up through UI
66 -** loads teseted and verified through UI; can be moved around between controllers as necessary
67 -*** loads don't need to be in the same room as the zumnet that controls them
68 -** keypads can use standard SR types or be fully customized
69 -** set up schedule, etc.
70 -* once done, save and back up configuration file
15 +See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
16 +See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
17 += The SHOWRUNNER™ Advantage =
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
71 71  )))
72 -
73 -= Tools for Statically Configured Lighting Networks =
74 -
75 -Unlike installations using the default program, SHOWRUNNER™ offers the opportunity to reduce the cost of hardware by enabling the use of any 3 or 4-Series processor, rather than being restricted to using the ZUM-HUB4 exclusively. Some of these other processors (DIN-AP4, RMC4, etc.) do not include a Control Subnet with built-in router, which requires the use of static IP addresses if the lighting network is to remain independent and there is no router specified to manage traffic on the lighting network. SHOWRUNNER™ includes several built-in features to assist with these sort of startups without requiring a Technician to bring their own router.
76 -
77 -This section does not apply to processors with a built in Control Subnet (CP4N, AV4, PRO4, ZUM-HUB4, etc.) or lighting networks that are fully integrated with a managed building LAN.
78 -
79 -The steps for statically configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
80 -
81 -1. [[Configure the static IP address>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome||anchor="HIPConfiguration"]] for the processor and [[install SHOWRUNNER™>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome||anchor="HProgramLoad"]]
82 -1. Use SHOWRUNNER™'s built in [[DHCP server>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]
83 -** If it you want to use specific static IP addresses for specific ZUMNET-JBOXs, use the SHOWRUNNER™ UI and set the DHCP range outside of the range you intend to use for the ZUMNET-JBOXs
84 -** If arbitrary static IP addresses are acceptable, then use the default IP address range
85 -1. Proceed with the standard [[CNET Mode>>doc:Hardware Design Guide.Crestron Zum Wired.Starting Up Zum Wired with SHOWRUNNER.WebHome||anchor="HIPConfiguration"]] start-up procedure
86 -)))
1680129701821-479.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.8 KB
Content
1680131641698-670.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.0 KB
Content
1680131684799-737.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.0 KB
Content