Last modified by Alexander Mott on 2023/12/13 19:15
From version 2.1
edited by Alexander Mott
on 2023/03/27 21:30
Change comment: There is no comment for this version
To version 35.1
edited by Alexander Mott
on 2023/12/13 19:15
Change comment: Renamed back-links.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -*Starting Up Zūm Wired with SHOWRUNNER™
1 +**Starting Up Zūm Wired with SHOWRUNNER™
Hidden
... ... @@ -1,1 +1,1 @@
1 -false
1 +true
Content
... ... @@ -1,24 +1,117 @@
1 +{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 +{{toc/}}
3 +{{/box}}
4 +
5 +(% class="row" %)
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 +
1 1  (% class="box errormessage" %)
2 2  (((
3 -n/a
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.
4 4  )))
5 5  
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 +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.Program Configuration.Zūm Discovery.WebHome]] page.
19 +
20 += CNET Mode (SHOWRUNNER™ Total Control) =
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.
23 +
6 6  (% class="box warningmessage" %)
7 7  (((
8 -n/a
26 +steps subject to change pending finalization of chief zum wired loadscript tool
27 +
28 +our regular commissioning guide is still incomplete, and it is referenced below
29 +(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)
30 +
31 +(also intend to have check boxes to select which scripts are desired)
9 9  )))
10 10  
11 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
12 -{{toc/}}
13 -{{/box}}
34 +The steps for configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
14 14  
15 -(% class="row" %)
16 -(((
17 -Lorem
18 -See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
19 -See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
36 +1. Install SHOWRUNNER™ and configure the processor per our [[startup guides>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]]
37 +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"]]
38 +1. Verify that all expected ZUMNET-JBOX-* devices are reporting online using the Device Discovery tool in Toolbox
39 +1*. Your laptop and the ZUMNET-JBOXs should all be connected to the Control Subnet
40 +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
41 +1*. Recall that any ZUMNET-JBOX that is unpowered or disconnected will prevent downstream ZUMNET-JBOXs from coming online
42 +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
43 +1*. These steps can still be followed even if not all the hardware is online
44 +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
45 +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]]
46 +1. Add columns for hostname ("Host", J) and IP-ID ("IP-ID", K) as shown below[[image:1680131811288-423.png]]
47 +1. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
48 +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"]]
49 +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
50 +1. Use the modified Device Summary file and Chief Integrations' Zūm Wired Loadscript Tool to generate loadscripts for:
51 +1*. Convert to Primary & App Mode
52 +1*. Update FW
53 +1*. Convert to CNET Mode
54 +1**. Optionally, generate Convert to CNET + Autoswitch On if automatic switching between CNET and App mode is desired
55 +1*. IP Config (DHCP)
56 +1. Run the "Convert to Primary & App Mode" loadscript
57 +1*. This loadscript connects to each ZUMNET-JBOX by their default hostname and updates their "zwmode" settings
58 +1*. Devices will reboot
59 +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**
60 +1. Connect to a handful of ZUMNET-JBOXs to verify that all ZUMLINK-* devices have been given unique CIDs
61 +1. Run the "Update FW" loadscript
62 +1*. This loadscript connects to each ZUMNET-JBOX by their default hostname and updates their firmware
63 +1*. This loadscript must be located in the same folder as the firmware .puf file
64 +1*. Devices will reboot
65 +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**
66 +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
67 +1**. Attempt to run the .puf file separately without a load script
68 +1**. If you encounter devices that report as "UNDEFINED" model types, see our [[FAQ on this topic>>doc:FAQ.My ZUMNET-JBOX or ZUMLINK device reports as an UNDEFINED model type?.WebHome]]
69 +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
70 +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
71 +1*. If ZUMLINK-* devices have conflicting CIDs or are not online, then they will not update
72 +1. Perform any Zūm App specific configurations (such as occupancy sensor reach) at this time.
73 +1*. If using the App Mode Autoswitch function and you do not want to use the factory room logic, configure all the Zūm Rooms using the Zūm App
74 +1*. Note that some functions such as occupancy sensor timeouts can be done later through the SHOWRUNNER™ UI
75 +1. Run the "Convert to CNET Mode" or "Convert to CNET Mode + Autoswitch On" loadscript
76 +1*. These loadscripts connect to each ZUMNET-JBOX by their default hostname and put them into CNET Mode (optionally enables the Autoswitch function)
77 +1*. Devices will reboot
78 +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**
79 +1. Run the "IP Config (DHCP)" loadscript
80 +1*. This loadscript will update the device IP-IDs and hostnames
81 +1*. Devices will reboot
82 +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**
83 +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"]] starting with step 4. If not, proceed to the next step
84 +1. Connect to each ZUMNET-JBOX to identify and address ZUMLINK devices per the SRTakeoff
85 +1. Verify loads and start-up the job as an ordinary SHOWRUNNER start-up™
86 +1. Once done, save and back up the configuration file for your records
20 20  
21 -= Start-Up Guide =
88 += Tools for Statically Configured Lighting Networks =
22 22  
23 -Lorem
90 +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.
91 +
92 +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.
93 +
94 +The steps for statically configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
95 +
96 +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"]]
97 +1. Use SHOWRUNNER™'s built in [[DHCP server>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]
98 +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
99 +1*. If arbitrary static IP addresses are acceptable, then use the default IP address range
100 +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
101 +1. Once the standard start-up procedure has been completed through step 14, [[export a new Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]] file
102 +1. Change the Device Summary filetype to ".csv" and open in Microsoft Excel
103 +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]]
104 +1. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
105 +1*. If there is no default gateway or DNS, use the processor's IP address instead
106 +1*. "IP-ID" column is optional
107 +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
108 +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
109 +1*. Up to 10 devices can be configured simultaneously
110 +1*. Devices will reboot once this script is run
111 +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**
112 +1. If desired, export a new Device Summary file as a record that this step was completed successfully
113 +1. If desired, disable the processor's DHCP service (the service will not resume if the processor reboots or the program restarts)
114 +1. Connect to each ZUMNET-JBOX to identify and address ZUMLINK devices per the SRTakeoff
115 +1. Verify loads and start-up the job as an ordinary SHOWRUNNER start-up™
116 +1. Once done, save and back up the configuration file for your records
24 24  )))
1680131811288-423.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +6.8 KB
Content