Changes for page Zūm Net Device Setup

Last modified by Alexander Mott on 2024/10/22 19:55
From version 10.9
edited by Alexander Mott
on 2022/06/17 17:19
Change comment: There is no comment for this version
To version 18.1
edited by Alexander Mott
on 2022/06/21 18:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.WebHome
1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome
Content
... ... @@ -47,6 +47,13 @@
47 47  ** Though saved as a text file, the Device Summary is actually a table of comma separated values
48 48  ** Renaming DeviceSummary.txt to DeviceSummary.csv will allow it to be opened and manipulated in common spreadsheet software such as Microsoft Excel or LibreOffice Calc
49 49  
50 +Below is an example of a Device Summary for a fully-configured job:
51 +
52 +* DeviceSummary.txt:
53 +[[image:1655487020590-542.png]]
54 +* DeviceSummary.csv:
55 +[[image:1655487132138-904.png]]
56 +
50 50  Once the Device Summary has been generated, proceed to identifying each ZUMNET-JBOX using the hostname, SN/MAC, or Device Tree View methods described below.
51 51  
52 52  ===== Identifying by Hostname =====
... ... @@ -75,10 +75,11 @@
75 75  
76 76  ===== Identifying through Network Device Tree View =====
77 77  
78 -If the electrical contractor has not provided a list of which serial numbers/MAC addresses belong to each installed ZUMNET-JBOX, then it is necessary to connect to each ZUMNET-JBOX individually and identify them through Toolbox. Putting a device into identify will stop any programs running on a processor, and taking a device out of identify mode will restart the program. This starting/stopping of the program can be time consuming when a large number of devices are being identified, so it may be a good idea to run the ##stopprog -p:01## command on the processor prior to identifying devices. Once all the devices are identified, run the ##progreset## command to resume the program.
85 +If the electrical contractor has not provided a list of which serial numbers/MAC addresses belong to each installed ZUMNET-JBOX and nobody intends to rename each ZUMNET-JBOX using the Crestron Zūm App, then the only way to identify which ZUMNET-JBOX is installed where is to use the Device Tree View tool in Toolbox. This is by far the slowest and most disruptive way to identify devices, so it is only recommended as a last resort.
79 79  
80 -* Connect to the lighting network and open Device Discovery Tool in Toolbox
81 -* Note the IP addresses for all of the installed ZUMNET-JBOXs
87 +Putting a ZUMNET-JBOX into identify mode will make it continuously produce an alarm-clock sound and flash any connected loads. Additionally, putting a device into identify mode will stop any programs running on a processor, and taking a device out of identify mode will restart the program. This starting/stopping of the program can be time consuming when a large number of devices are being identified, so it may be a good idea to suspend the program using the ##stopprog -p:01## command on the processor prior to identifying devices. Once all the devices are identified, run the ##progreset## command to resume the program.
88 +
89 +* Generate a Device Summary and note the IP addresses for all installed ZUMNET-JBOXs
82 82  * Connect to the first ZUMNET-JBOX using Network Device Tree View
83 83  * Locate the "ZUMNET-JBOX-xx-xx-LOCAL" device in the list of connected devices
84 84  ** The model will vary between 0-10V and DALI JBOXs
... ... @@ -86,15 +86,17 @@
86 86  * Right click the device and press "Identify This Device..." from the context menu
87 87  * The device will blink any attached fixtures and make an alarm sound
88 88  * Walk around the jobsite until the room/controlled fixtures are located
89 -* Update the SRTakeoff.xlsx with the device serial number, MAC address, and automatically assigned IP address
90 -* Repeat all steps for each ZUMNET-JBOXs until all of the ZUMNET-JBOXs have been identified
97 +* Edit the Device Summary or SRTakeoff.xlsx so that you remember which JBOX is which
98 +* Repeat for each ZUMNET-JBOX until all of the ZUMNET-JBOXs have been identified
91 91  
100 +Once you have determined and recorded which ZUMNET-JBOX is which, you may proceed to IP configuration.
101 +
92 92  ==== Assigning Permanent Static IP Addresses and IP-IDs ====
93 93  
94 94  Once you have identified which IP address has been assigned to each ZUMNET-JBOX, you can begin configuring them with permanent static IP addresses and the correct IP-ID:
95 95  
96 96  * Open Text Console in Toolbox and connect to the first ZUMNET-JBOX
97 -* Run the following commands to configure the ZUMNET-JBOXs IP settings (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a permanent IP address of (% style="color:blue" %)**10.0.0.80**(%%), an IP-ID of (% style="color:olive" %)**30**(%%), a processor IP address of (% style="color:orange" %)**10.0.0.10**(%%), and a hostname of (% style="color:#800080" %)**ZNET-JBOX-RM-201**(%%))
107 +* Run the following commands to configure the ZUMNET-JBOXs IP settings (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a permanent IP address of (% style="color:blue" %)**10.0.0.80**(%%), an IP-ID of (% style="color:olive" %)**30**(%%), a processor IP address of (% style="color:orange" %)**10.0.0.10**(%%), and a hostname of (% style="color:#800080" %)**ZNET-JBOX-RM-201**(%%); the hostname can be skipped if it has already been configured from the Crestron Zūm App)
98 98  ** Disable DHCP: ##dhcp off##
99 99  ** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.80**(%%)##
100 100  ** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)##
... ... @@ -102,6 +102,7 @@
102 102  ** Update IP table: ##addm (% style="color:olive" %)**30**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
103 103  ** Set hostname: ##host (% style="color:purple" %)**ZNET-JBOX-RM-201**(%%)##
104 104  ** Reboot the ZUMNET-JBOX: ##reboot##
115 +*** Note that rebooting the JBOX will cause the lights to briefly cut out
105 105  * Repeat for all ZUMNET-JBOXs on the job
106 106  
107 107  === Zūm Net Specific Configuration ===
... ... @@ -135,6 +135,24 @@
135 135  
136 136  A reboot is required if the mode is to be changed.
137 137  
149 +=== Problems Connecting to Zūm Room (Error 13) ===
150 +
151 +If you cannot connect to the Zūm Room (i.e., the primary ZUMNET-JBOX for the room) using the Crestron Zūm App:
152 +
153 +* Verify the ZUMNET-JBOX is in "zum" mode
154 +* Verify that the primary ZUMNET-JBOX for the room is in "master" mode
155 +* Confirm you are on an Android device (the iOS app does not currently support Zūm Wired devices)
156 +* If you get an "Error 13" code:
157 +** Uninstall the app
158 +** Reboot your phone
159 +** Reinstall the app
160 +** Navigate to Android Application settings
161 +** Navigate to the Crestron Zūm App
162 +** Clear storage for the Crestron Zūm App
163 +** Open the Crestron Zūm App and accept the license agreements
164 +** Connect to the Zūm Room
165 +** When prompted, input a valid pin (default is 2468)
166 +
138 138  === Changing IP-IDs ===
139 139  
140 140  If ZUMNET-JBOXs must be assigned different IP-IDs than indicated in the SRTakeoff.xlsx, or if Zūm Link devices are moved between ZUMNET-JBOXs, then the configuration file must be updated. Every Zūm Link device in the configuration has a ##"DeviceHostId"## associated with it, which corresponds to the IP-ID of the ZUMNET-JBOX hosting it.
1655487002500-174.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
1655487008788-390.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
1655487020590-542.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
1655487132138-904.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +53.0 KB
Content