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 24.1
edited by Alexander Mott
on 2022/09/16 23:54
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
... ... @@ -1,10 +1,21 @@
1 -=== Zūm Net Devices in SHOWRUNNER™ ===
1 +(% class="box warningmessage" %)
2 +(((
3 +This article is for configuring Zūm Net devices using Crestron Toolbox. For instructions on configuring Zūm Wired rooms using the Crestron Zūm App, see [[this page>>SHOWRUNNER™ Setup Guide.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome]].
4 +)))
2 2  
6 +{{box title="**Contents**"}}
7 +{{toc/}}
8 +{{/box}}
9 +
10 +(% class="row" %)
11 +(((
12 += Zūm Net Devices in SHOWRUNNER™ =
13 +
3 3  Zūm Net devices are part of Crestron's latest Zūm Wired system, acting as a the main lighting controller for a Zūm Wired room. In networked applications of Zūm Wired, they also act as bridges connecting the local Zūm Link devices in each room to the overall lighting network throughout the building. Since Zūm Link and Cresnet are [[interchangeable>>https://wiki.chiefintegrations.com/SHOWRUNNER%E2%84%A2%20Setup%20Guide/Wiring%20Guide/Wiring%20Overview/Z%C5%ABm%20Net/#HZ16BmLink]], and Zūm Net is an Ethernet protocol, this means that Zūm Net devices can be thought of as single-net DIN-CENCN-2s. As of Summer 2022, there are only two Zūm Net devices that have been announced and are in production: the ZUMNET-JBOX-16A-LV 0-10V load controller and the ZUMNET-JBOX-DALI DALI load controller. Configuring these devices for use with SHOWRUNNER™ is identical, so they will be referred to collectively as ZUMNET-JBOXs for the purposes of this article.
4 4  
5 5  Much like DIN-CENCN-2s in SHOWRUNNER™ installations, ZUMNET-JBOXs identify themselves to the processor via their IP-ID, so the specific IP address of any given ZUMNET-JBOX does not matter as long as it is in the same range as the processor and does not conflict with any other devices on the network. If hosted devices are moved between ZUMNET-JBOXs, or if the ZUMNET-JBOX needs to have a different IP-ID than it was initially assigned, the configuration will need to be updated (see below). Chief Integrations typically provides an SRTakeoff.xlsx spreadsheet which will list all the Zūm Net and Zūm Link devices and their associated IP-IDs. If no takeoff is provided, then the processor's IP table can be checked by running the ##ipt -t ##command from the processor after the configuration is loaded. ZUMNET-JBOX's will typically start with IP-IDs in the 30-5F range, but can potentially exceed this range.
6 6  
7 -=== Identification and IP Configuration ===
18 += Identification and IP Configuration =
8 8  
9 9  Configuring ZUMNET-JBOXs must be done over Ethernet, and is easiest to do once all ZUMNET-JBOXs have been installed, powered up, and connected to the lighting network. (It is not necessary for all Zūm Link devices to be installed in order to configure ZUMNET-JBOXs.)
10 10  
... ... @@ -21,7 +21,7 @@
21 21  1. Identifying which DHCP assigned IP address corresponds to each ZUMNET-JBOX
22 22  1. Connecting to each ZUMNET-JBOX and assigning a permanent static IP address and IP-ID
23 23  
24 -==== Identifying ZUMNET-JBOXs ====
35 +== Identifying ZUMNET-JBOXs ==
25 25  
26 26  Once all ZUMNET-JBOXs have been assigned temporary IP addresses from the DHCP server, they must each be identified so that the correct IP-ID can be assigned. The goal is to associate each assigned IP address with the room that each ZUMNET-JBOX is meant to control. Then we can connect to each ZUMNET-JBOX and set static IP addresses and update the IP table with the correct IP-ID.
27 27  
... ... @@ -47,9 +47,16 @@
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  
61 +Below is an example of a Device Summary for a fully-configured job:
62 +
63 +* DeviceSummary.txt:
64 +[[image:1655487020590-542.png]]
65 +* DeviceSummary.csv:
66 +[[image:1655487132138-904.png]]
67 +
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 -===== Identifying by Hostname =====
70 +=== Identifying by Hostname ===
53 53  
54 54  The Crestron Zūm App is used to configure the internal logic of Zūm Wired rooms. This internal logic determines the room behavior when ZUMNET-JBOXs are used in standalone applications or if communication to the processor is lost. Even on SHOWRUNNER™ jobs with a central program running the lighting controls, it is best practice to configure the internal logic to match as closely as possible the SHOWRUNNER™ logic in order to minimize disruption to end-users in the event of a processor or network failure.
55 55  
... ... @@ -67,18 +67,21 @@
67 67  
68 68  If all hostnames have been set, then it becomes very easy to know which DHCP assigned IP address is associated with each room using the Device Summary. Generate a Device Summary with the new hostnames and proceed to IP configuration.
69 69  
70 -===== Identifying by Serial Number or MAC Address =====
88 +Full instructions on configuring Zūm Wired using the Crestron Zūm App, can be found [[here>>SHOWRUNNER™ Setup Guide.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome]].
71 71  
90 +=== Identifying by Serial Number or MAC Address ===
91 +
72 72  Both the serial number and MAC address are printed onto each ZUMNET-JBOX. Just like with Cresnet jobs, it is good practice for the electrical contractor to record serial numbers as they install devices. It is also good to collect the MAC addresses, but it is not necessary since Device Summary will have both the serial number and MAC address.
73 73  
74 74  If the electrical contractor has provided a list of which serial numbers/MAC addresses belong to each installed ZUMNET-JBOX, then generate a Device Summary and proceed to IP configuration.
75 75  
76 -===== Identifying through Network Device Tree View =====
96 +=== 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.
98 +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
100 +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.
101 +
102 +* 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
110 +* Edit the Device Summary or SRTakeoff.xlsx so that you remember which JBOX is which
111 +* Repeat for each ZUMNET-JBOX until all of the ZUMNET-JBOXs have been identified
91 91  
92 -==== Assigning Permanent Static IP Addresses and IP-IDs ====
113 +Once you have determined and recorded which ZUMNET-JBOX is which, you may proceed to IP configuration.
93 93  
115 +== Assigning Permanent Static IP Addresses and IP-IDs ==
116 +
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**(%%))
120 +* 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,13 +102,14 @@
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##
128 +*** 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 -=== Zūm Net Specific Configuration ===
131 += Zūm Net Specific Configuration =
108 108  
109 109  Zūm Net devices have a two additional settings not present for other devices: Zūm/Cresnet mode and Master/Slave mode. ZUMNET-JBOXs should ship as Master devices in Zūm Mode from the factory, and this is typically the desired setting.
110 110  
111 -==== Zūm/Cresnet Mode ====
135 +== Zūm/Cresnet Mode ==
112 112  
113 113  Zūm Mode (also known as App Mode) is the default setting for new ZUMNET-JBOXs, and allows them to be configured from the Crestron Zūm App. If a ZUMNET-JBOX is put into Cresnet mode, it will no longer be able to be configured using the Crestron Zūm App and all internal logic will be disabled. Generally, Cresnet mode is only required if non-Zūm Link devices are connected to the ZUMNET-JBOX (e.g. a GL-EXP-DIMU-CN phase dimmer or C2N-CBD-P Cameo keypads) or if certain SHOWRUNNER™ features are required (such as changing the dimming response curve).
114 114  
... ... @@ -120,7 +120,7 @@
120 120  
121 121  A reboot is required if the mode is to be changed. Note that this command will also display the current Master/Slave mode, but will not allow you to change it.
122 122  
123 -==== Master/Slave Mode ====
147 +== Master/Slave Mode ==
124 124  
125 125  ZUMNET-JBOXs ship in "Master" mode by default, and generally this is how they should be configured. "Slave" mode effectively turns a ZUMNET-JBOX into a ZUMLINK-JBOX. There are two scenarios in which a ZUMNET-JBOX will need to be configured in "Slave" mode:
126 126  
... ... @@ -135,7 +135,7 @@
135 135  
136 136  A reboot is required if the mode is to be changed.
137 137  
138 -=== Changing IP-IDs ===
162 += 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.
141 141  
... ... @@ -148,3 +148,8 @@
148 148  [[image:1655247008527-737.png]]
149 149  
150 150  [[image:1655246948921-246.png]]
175 +
176 += Problems Connecting to Zūm Room (Error 13) =
177 +
178 +{{display excludeFirstHeading="true" reference="SHOWRUNNER™ Setup Guide.Wiring Guide.Zūm Wired System Overview.Crestron Zūm App Overview.WebHome" section="HProblemsConnectingtoZ16BmRoom28Error1329"/}}
179 +)))
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