Last modified by Alexander Mott on 2023/12/13 19:15
From version 6.2
edited by Alexander Mott
on 2023/03/29 21:16
Change comment: (Autosaved)
To version 31.1
edited by Alexander Mott
on 2023/03/29 23:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,13 +11,3 @@
1 -(% class="box errormessage" %)
2 -(((
3 -n/a
4 -)))
5 -
6 -(% class="box warningmessage" %)
7 -(((
8 -n/a
9 -)))
10 -
11 11  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
12 12  {{toc/}}
13 13  {{/box}}
... ... @@ -14,36 +14,75 @@
14 14  
15 15  (% class="row" %)
16 16  (((
17 -Lorem
18 -See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
19 -See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
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.
20 20  
21 -= Zūm Discovery =
9 += App Mode (Zūm Discovery) =
22 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
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 +)))
24 24  
25 -= SHOWRUNNER™ Complete Control =
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.
26 26  
27 -= Start-Up Guide =
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.
28 28  
29 -Lorem
20 += CNET Mode (SHOWRUNNER™ Total Control) =
30 30  
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.
23 +
31 31  (% class="box warningmessage" %)
32 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]]?
26 +steps subject to change pending finalization of chief zum wired loadscript tool
27 +(i intend for the loadscript tool to require the showrunner license to function; the license contains the processor MAC address, which will be used to determine the IP address for the ip table entries; user will be prompted to confirm/correct IP address for IP table entries)
34 34  
35 -basic steps:
29 +(also intend to have check boxes to select which scripts are desired)
30 +)))
36 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"]]
32 +The steps for configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
33 +
34 +1. Install SHOWRUNNER™ and configure the processor per our [[startup guides>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]]
35 +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"]]
36 +1. Verify that all expected ZUMNET-JBOX-* devices are reporting online using the Device Discovery tool in Toolbox
37 +1*. Your laptop and the ZUMNET-JBOXs should all be connected to the Control Subnet
38 +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
39 +1*. Recall that any ZUMNET-JBOX that is unpowered or disconnected will prevent downstream ZUMNET-JBOXs from coming online
40 +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
41 +1*. These steps can still be followed even if not all the hardware is online
42 +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
43 +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]]
44 +1. Add columns for hostname ("Host", J) and IP-ID ("IP-ID", K) as shown below[[image:1680131811288-423.png]]
45 +1. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
46 +1*. Columns L through O are optional unless static IP addresses are required, as covered [[below>>doc:Design Guide.Hardware Design Guide.Crestron Zum Wired.Starting Up Zum Wired with SHOWRUNNER.WebHome||anchor="HToolsforStaticallyConfiguredLightingNetworks"]]
47 +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
48 +1. Use the modified Device Summary file and Chief Integrations' Zūm Wired Loadscript Tool to generate loadscripts for:
49 +1*. Convert to Primary & App Mode
50 +1*. Update FW
51 +1*. Convert to CNET Mode
52 +1**. Optionally, generate Convert to CNET + Autoswitch On if automatic switching between CNET and App mode is desired
53 +1*. IP Config (DHCP)
54 +1. Run the "Convert to Primary & App Mode" loadscript
55 +1*. This loadscript connects to each ZUMNET-JBOX by their default hostname and updates their "zwmode" settings
56 +1*. Devices will reboot
57 +1*. **Verify that all devices report completing successfully in the Loadscript Manager tool before proceeding to the next step; re-run the loadscript for specific devices as necessary**
58 +1. Connect to a handful of ZUMNET-JBOXs to verify that all ZUMLINK-* devices have been given unique CIDs
59 +1. Run the "Update FW" loadscript
60 +1*. This loadscript connects to each ZUMNET-JBOX by their default hostname and updates their firmware
61 +1*. This loadscript must be located in the same folder as the firmware .puf file
62 +1*. Devices will reboot
63 +1*. **Verify that all devices report completing successfully in the Loadscript Manager tool before proceeding to the next step; re-run the loadscript for specific devices as necessary**
64 +1**. If the script has been re-run multiple times and has failed each time, connect to the ZUMNET-JBOX and verify that all the ZUMLINK-* hardware appears correctly
65 +1**. Attempt to run the .puf file separately without a load script
66 +1**. If you encounter devices that report as "UNDEFINED" model types, see our FAQ on this topic (link)
67 +1. Once FW updates are complete, verify all ZUMNET-JBOX actually took the FW update by using Device Discovery Tool to export a Device Summary and observe that the reported FW for all devices matches the FW version in the .puf file
68 +1*. Because ZUMNET-JBOX update their own firmware after attached ZUMLINK-* devices, if a ZUMNET-JBOX is up-to-date then all ZUMLINK-* devices should also be updated
69 +1*. If ZUMLINK-* devices have conflicting CIDs or are not online, then they will not update
70 +1. If using
71 +
72 +
73 +
74 +
43 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 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 48  ** devices will reboot
49 49  ** per crestron, 1.0006.00012 and newer ship in primary mode (**tbd if they will ship in app mode?**)
... ... @@ -54,7 +54,6 @@
54 54  ** devices will reboot, possibly multiple times
55 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 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 58  * if app mode backup is desired, configure the boxes using the app now
59 59  * run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
60 60  ** devices will reboot
... ... @@ -76,5 +76,31 @@
76 76  ** keypads can use standard SR types or be fully customized
77 77  ** set up schedule, etc.
78 78  * once done, save and back up configuration file
107 +
108 += Tools for Statically Configured Lighting Networks =
109 +
110 +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.
111 +
112 +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.
113 +
114 +The steps for statically configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
115 +
116 +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"]]
117 +1. Use SHOWRUNNER™'s built in [[DHCP server>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]
118 +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
119 +1*. If arbitrary static IP addresses are acceptable, then use the default IP address range
120 +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
121 +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
122 +1. Change the Device Summary filetype to ".csv" and open in Microsoft Excel
123 +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:1680131811288-423.png]]
124 +1. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
125 +1*. If there is no default gateway or DNS, use the processor's IP address instead
126 +1*. "IP-ID" column is optional
127 +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
128 +1. Use the modified Device Summary file and Chief Integrations' Zūm Wired Loadscript Tool to generate a loadscript that connects to devices by their hostname and sets their static IP settings
129 +1*. Up to 10 devices can be configured simultaneously
130 +1*. Devices will reboot once this script is run
131 +1*. **Verify that all devices report completing successfully in the Loadscript Manager tool before proceeding to the next step; re-run the loadscript for specific devices as necessary**
132 +1. If desired, export a new Device Summary file as a record that this step was completed successfully
133 +1. If desired, disable the processor's DHCP service (the service will not resume if the processor reboots or the program restarts)
79 79  )))
80 -)))
1680131811288-423.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +6.8 KB
Content