Last modified by Alexander Mott on 2023/12/13 19:15
From version 31.1
edited by Alexander Mott
on 2023/03/29 23:36
Change comment: There is no comment for this version
To version 29.1
edited by Alexander Mott
on 2023/03/29 23:17
Change comment: Deleted image "1680131725203-239.png"

Summary

Details

Page properties
Content
... ... @@ -24,9 +24,6 @@
24 24  (% class="box warningmessage" %)
25 25  (((
26 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)
28 -
29 -(also intend to have check boxes to select which scripts are desired)
30 30  )))
31 31  
32 32  The steps for configuring a networked Zūm Wired installation with SHOWRUNNER™ are:
... ... @@ -43,36 +43,14 @@
43 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 44  1. Add columns for hostname ("Host", J) and IP-ID ("IP-ID", K) as shown below[[image:1680131811288-423.png]]
45 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"]]
43 +1*. If there is no default gateway or DNS, use the processor's IP address instead
47 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 71  
72 -
73 -
74 -
46 +* use crestron toolbox device discovery to create a [[Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HDeviceDiscoveryTool"]]
75 75  * use chief tools tm tool to generate various zum wired load scripts
48 +** (need to determine exact process for this; will need to add IP-ID and new hostname to device summary somehow)
49 +** (will likely generate two versions of the loadscripts; one connecting by default hostname and one connecting by new hostname)
50 +** (intend to require SR license for zwired LS generator, if only to get the proc mac address)
76 76  * 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
77 77  ** devices will reboot
78 78  ** per crestron, 1.0006.00012 and newer ship in primary mode (**tbd if they will ship in app mode?**)
... ... @@ -83,6 +83,7 @@
83 83  ** devices will reboot, possibly multiple times
84 84  ** 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)
85 85  * run device discovery again to confirm that all zumnet boxes were updated
61 +** 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
86 86  * if app mode backup is desired, configure the boxes using the app now
87 87  * run "ip config (def. hostname)" loadscript to update device IP-IDs and hostnames
88 88  ** devices will reboot
... ... @@ -120,15 +120,15 @@
120 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 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 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]]
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]]
124 124  1. Fill out these columns for each of the ZUMNET-JBOXs in the device summary
125 125  1*. If there is no default gateway or DNS, use the processor's IP address instead
126 126  1*. "IP-ID" column is optional
127 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
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
129 129  1*. Up to 10 devices can be configured simultaneously
130 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**
107 +1. Verify that all devices report completing successfully in the Loadscript Manager tool
132 132  1. If desired, export a new Device Summary file as a record that this step was completed successfully
133 133  1. If desired, disable the processor's DHCP service (the service will not resume if the processor reboots or the program restarts)
134 134  )))