Last modified by Alexander Mott on 2023/12/13 19:15
From version 27.1
edited by Alexander Mott
on 2023/03/29 23:17
Change comment: Deleted image "1680131702997-679.png"
To version 7.1
edited by Alexander Mott
on 2023/03/29 21:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
1 +({{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 2  {{toc/}}
3 3  {{/box}}
4 4  
... ... @@ -6,44 +6,32 @@
6 6  (((
7 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 8  
9 -= App Mode (Zūm Discovery) =
10 -
9 += App Mode Zūm Discovery =
11 11  (% class="box errormessage" %)
12 12  (((
13 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 14  )))
15 -
16 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 -
18 18  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.
19 19  
20 -= CNET Mode (SHOWRUNNER™ Total Control) =
17 += (SHOWRUNNER™ Complete Control) =
21 21  
22 -Using SHOWRUNNER™ to control a networked Zūm Wired installation with ZUMNET-JBOXs running in CNET mode is the recommended way of using SHOWRUNNER™ with Zūm Wired. This is also the only way to gain control of legacy Cresnet devices (such as GL-EXP-DIMU-CN, C2N-IO, and GLS-PART-CN) that are connected to a ZUMNET-JBOX, as these Cresnet devices are not recognized or supported by the Crestron Zūm App.
19 += Start-Up Guide =
23 23  
21 +Lorem
22 +
24 24  (% class="box warningmessage" %)
25 25  (((
26 -steps subject to change pending finalization of chief zum wired loadscript tool
27 -)))
25 +cross reference/update to old [[zumnet startup>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]?
28 28  
29 -The steps for configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
27 +basic steps:
30 30  
31 -1. Install SHOWRUNNER™ and configure the processor per our [[startup guides>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]]
32 -1*. If using a processor without a dedicated Control Subnet, follow the [[additional steps detailed below>>doc:Design Guide.Hardware Design Guide.Crestron Zum Wired.Starting Up Zum Wired with SHOWRUNNER.WebHome||anchor="HToolsforStaticallyConfiguredLightingNetworks"]]
33 -1. Verify that all expected ZUMNET-JBOX-* devices are reporting online using the Device Discovery tool in Toolbox
34 -1*. Your laptop and the ZUMNET-JBOXs should all be connected to the Control Subnet
35 -1*. If there are missing ZUMNET-JBOXs, verify with the EC that the devices are powered and that the Zūm Net cabling is correct
36 -1*. Recall that any ZUMNET-JBOX that is unpowered or disconnected will prevent downstream ZUMNET-JBOXs from coming online
37 -1. Once all hardware is online, use the [[Device Discovery Tool>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HDeviceDiscoveryTool"]] in Toolbox to [[export a Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]] file
38 -1*. These steps can still be followed even if not all the hardware is online
39 -1*. If not all the hardware is online, then these steps will need to be repeated and the loadscripts run just for the previously offline devices
40 -1*. Alternatively, if there are only a few previously offline devices, then they can be [[configured and updated manually>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.ZUMNET-JBOX Setup.WebHome]]
41 -1. Add columns for hostname ("Host", J) and IP-ID ("IP-ID", K) as shown below[[image:1680131811288-423.png]]
42 -1. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
43 -1*. If there is no default gateway or DNS, use the processor's IP address instead
44 -1*. If this information has already been filled out in the SHOWRUNNER™ Takeoff IP Table sheet, then it is easy to copy/paste from the takeoff into the Device Summary .csv by sorting and filtering the two documents by MAC address
45 -
46 -* use crestron toolbox device discovery to create a [[Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HDeviceDiscoveryTool"]]
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"]]
47 47  * use chief tools tm tool to generate various zum wired load scripts
48 48  ** (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow)
49 49  ** (will likely generate two versions of the loadscripts; one connecting by default hostname and one connecting by new hostname)
... ... @@ -80,31 +80,5 @@
80 80  ** keypads can use standard SR types or be fully customized
81 81  ** set up schedule, etc.
82 82  * once done, save and back up configuration file
83 -
84 -= Tools for Statically Configured Lighting Networks =
85 -
86 -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.
87 -
88 -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.
89 -
90 -The steps for statically configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
91 -
92 -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"]]
93 -1. Use SHOWRUNNER™'s built in [[DHCP server>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]
94 -1*. If 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
95 -1*. If arbitrary static IP addresses are acceptable, then use the default IP address range
96 -1. Proceed with the standard [[CNET Mode>>doc:Design Guide.Hardware Design Guide.Crestron Zum Wired.Starting Up Zum Wired with SHOWRUNNER.WebHome||anchor="HCNETMode28SHOWRUNNER2122TotalControl29"]] start-up procedure from step 2
97 -1. Once the standard start-up procedure has been completed, [[export a new Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]] file
98 -1. Change the Device Summary filetype to ".csv" and open in Microsoft Excel
99 -1. Add columns for hostname ("Host", J), IP-ID ("IP-ID", K), static IP address ("IPA", L), static IP subnet mask ("IPM", M), default gateway ("DEFR", N), and domain name server ("DNS", O) as shown below[[image:1680131807403-927.png]]
100 -1. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
101 -1*. If there is no default gateway or DNS, use the processor's IP address instead
102 -1*. "IP-ID" column is optional
103 -1*. If this information has already been filled out in the SHOWRUNNER™ Takeoff IP Table sheet, then it is easy to copy/paste from the takeoff into the Device Summary .csv by sorting and filtering the two documents by MAC address
104 -1. Use the modified Device Summary file and Chief Integrations' Zūm Wired Loadscript Generator Tool to generate a loadscript that connects to devices by their hostname and sets their static IP settings
105 -1*. Up to 10 devices can be configured simultaneously
106 -1*. Devices will reboot once this script is run
107 -1. Verify that all devices report completing successfully in the Loadscript Manager tool
108 -1. If desired, export a new Device Summary file as a record that this step was completed successfully
109 -1. If desired, disable the processor's DHCP service (the service will not resume if the processor reboots or the program restarts)
110 110  )))
72 +)))
1680131725203-239.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -7.0 KB
Content
1680131728246-538.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -7.0 KB
Content
1680131811288-423.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.8 KB
Content