Changes for page Zūm Net Device Setup

Last modified by Alexander Mott on 2024/10/22 19:55
From version 43.1
edited by Alexander Mott
on 2023/05/16 14:29
Change comment: There is no comment for this version
To version 49.1
edited by Alexander Mott
on 2024/01/05 18:49
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  (% class="box warningmessage" %)
2 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 -For details on using the Zūm Discovery feature to automatically build a ShowRunnerCLC™ configuration based on the Zūm App settings, see [[this page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Zūm Discovery.WebHome]].
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.SHOWRUNNER™ Installation Guide.Preparation.Zūm App Overview.WebHome]].
4 +For details on using the Zūm Discovery feature to automatically build a ShowRunnerCLC™ configuration based on the Zūm App settings, see [[this page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Zūm Discovery.WebHome]].
5 5  )))
6 6  
7 7  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
... ... @@ -8,7 +8,7 @@
8 8  {{toc/}}
9 9  {{/box}}
10 10  
11 -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 ShowRunnerCLC™ is identical, so they will be referred to collectively as ZUMNET-JBOXs for the purposes of this article.
11 +Zūm Net devices are part of Crestron's latest Zūm Wired system, acting as 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 ShowRunnerCLC™ is identical, so they will be referred to collectively as ZUMNET-JBOXs for the purposes of this article.
12 12  
13 13  Much like DIN-CENCN-2s in ShowRunnerCLC™ 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.
14 14  
... ... @@ -77,7 +77,7 @@
77 77  
78 78  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.
79 79  
80 -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]].
80 +Full instructions on configuring Zūm Wired using the Crestron Zūm App, can be found [[here>>SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Zūm App Overview.WebHome]].
81 81  
82 82  === Identifying by Serial Number or MAC Address ===
83 83  
... ... @@ -106,8 +106,10 @@
106 106  
107 107  == Assigning Permanent Static IP Addresses and IP-IDs ==
108 108  
109 -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:
109 +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.
110 110  
111 +Note that static IP addresses are only required on jobs where there is no permanent DHCP server. Manual IP-ID assignment is not required for jobs intended to be used with Zūm Auto Discovery, though it may still be recommended in order to keep track and document which IP-ID is associated with each area (Auto Discovery will auto-assign IP-IDs to ZUMNET-JBOXs without IP-IDs, but if a ZUMNET-JBOX already has an IP table entry it will be imported to the configuration with that pre-existing IP-ID).
112 +
111 111  * Open Text Console in Toolbox and connect to the first ZUMNET-JBOX
112 112  * 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)
113 113  ** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.80**(%%)##
... ... @@ -122,20 +122,8 @@
122 122  
123 123  = Zūm Net Specific Configuration =
124 124  
125 -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.
127 +Zūm Net devices have a two additional settings not present for other devices: Primary/Secondary mode and Zūm/Cresnet mode. ZUMNET-JBOX-DALI have a third setting for Group/Legacy DALI mode, and all ZUMNET-JBOX-* that are in CNET mode can optionally be configured to automatically switch back and forth between CNET and App mode depending on whether the control processor is reachable.
126 126  
127 -== Zūm/Cresnet Mode ==
128 -
129 -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 ShowRunnerCLC™ features are required (such as changing the dimming response curve).
130 -
131 -The commands to view or change the Zūm/Cresnet mode are:
132 -
133 -* View current mode: ##zwmode##
134 -* Make Zūm/App mode: ##zwmode zum##
135 -* Make Cresnet mode: ##zwmode cnet##
136 -
137 -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.
138 -
139 139  == Primary/Secondary Mode ==
140 140  
141 141  (% class="box warningmessage" %)
... ... @@ -163,8 +163,41 @@
163 163  
164 164  A reboot is required if the mode is changed.
165 165  
166 -= Changing IP-IDs =
156 +== Zūm/Cresnet Mode ==
167 167  
158 +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 ShowRunnerCLC™ features are required (such as changing the dimming response curve).
159 +
160 +The commands to view or change the Zūm/Cresnet mode are:
161 +
162 +* View current mode: ##zwmode##
163 +* Make Zūm/App mode: ##zwmode zum##
164 +* Make Cresnet mode: ##zwmode cnet##
165 +
166 +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.
167 +
168 +=== DALI Group/Legacy Mode ===
169 +
170 +ZUMNET-JBOX-DALI that are operating in App mode should be kept in "Groups" DALI mode, and DALI loads must be configured through the Zūm App. ZUMNET-JBOX-DALI that are operating in CNET mode with ShowRunner™ must be changed to "Legacy" DALI mode, and the DALI ballasts must be addressed and grouped using the Crestron Toolbox DALI Commissioning 2.0 Tool.
171 +
172 +To change modes, run the appropriate dalisetmode command, wait 5 seconds, and then reboot the ZUMNET-JBOX-DALI:
173 +
174 +* Set Legacy mode: ##dalisetmode 1 1##
175 +* Set Groups mode: ##dalisetmode 1 2##
176 +
177 +=== Zūm Mode Auto Switch ===
178 +
179 +Zūm Mode Auto Switch is a feature introduced by Crestron in November of 2022 with .puf firmware v1.04.05 (device firmware 1.004.00005). This feature is intended to address concerns that arose from projects using custom programs with ZUMNET-JBOX-* devices in CNET Mode. Previously, if a device in CNET Mode lost connection to the processor, then it would be impossible to maintain any sort of control over the lighting. With Zūm Mode Auto Switch enabled, a ZUMNET-JBOX running in CNET Mode will automatically switch to App Mode and process local logic in the event that it loses connection to the processor.
180 +
181 +Note that on 0-10V and switched JBOXs, the connected loads will flash once when rebooting. On ZUMNET-DALI-JBOX models, the JBOX will reboot once when switching to App mode and twice when switching back to CNET mode (once to switch to CNET, and a second time to switch to Legacy DALI mode)
182 +
183 +Enable Zūm Mode Auto Switch using the command: ##autoswitch on##
184 +
185 +Rebooting after changing Auto Switch modes is not officially required, but is still recommended.
186 +
187 +//Any configuration changes made through the Zūm App should be made while the control processor is disconnected: the easiest ways to accomplish this are to either disconnect the Cat5e/Cat6 cable at the processor or use Text Console commands (//##stopprog -p:01##//)to temporarily suspend the custom program on the processor.//
188 +
189 +== Changing IP-IDs ==
190 +
168 168  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.
169 169  
170 170  If a Zūm Link device is moved from one ZUMNET-JBOX to another, then this ##"DeviceHostId"## must be updated with the IP-ID of the new device.