Changes for page Zūm Net Device Setup

Last modified by Alexander Mott on 2024/10/22 19:55
From version 50.5
edited by Alexander Mott
on 2024/10/15 14:29
Change comment: (Autosaved)
To version 1.1
edited by Alexander Mott
on 2022/06/13 21:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Zūm Net Device Setup
1 +ZUMNET-JBOX Setup
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome
1 +SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.WebHome
Content
... ... @@ -1,236 +1,33 @@
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.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 -)))
1 +=== ZUMNET-JBOXs in SHOWRUNNER™ ===
6 6  
7 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
8 -{{toc/}}
9 -{{/box}}
3 +ZUMNET-JBOXs are part of Crestron's latest Zūm Wired system, acting as an Ethernet-to-Zūm Link bridge to convert between Ethernet and Zūm Link data traffic. This helps avoid issues with bandwidth over the Cresnet bus for jobs which have a large number of Cresnet devices, as well as allowing for additional power supplies to provide power Cresnet devices.
10 10  
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.
5 +For SHOWRUNNER™ installations, the IP address of the DIN-CENCN-2 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. Instead, DIN-CENCN-2s are identified to the processor via their IP-ID. Note that which Cresnet devices are landed at each Net of each DIN-CENCN-2 matters, and if devices are moved between Nets or between DIN-CENCN-2s then the configuration will need to be updated (see below). Chief Integrations typically provides an SRTakeoff.xlsx spreadsheet with an IP Table tab that lists all the DIN-CENCN-2 IP-IDs in the program. 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. DIN-CENCN-2's will typically have IP-IDs in the "##Dx##" range.
12 12  
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.
7 +=== IP Configuration ===
14 14  
15 -= Identification and IP Configuration =
9 +Typically, each DIN-CENCN-2 will need to be initially configured via USB, unless their MAC addresses are already known and the lighting network has a DHCP server (either by running DHCP server software on your computer, or if the processor has a control subnet or is running the [[SHOWRUNNER™ DHCP Server>>doc:SHOWRUNNER™ User Guide & Wiki.Troubleshooting.DHCP Server.WebHome]]).
16 16  
17 -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.)
11 +Whether connected to the DIN-CENCN-2 via USB or Ethernet, the process to configure the static IP addresses is the same:
18 18  
19 -Since there is no option to configure ZUMNET-JBOXs via USB, a DHCP server is required. There are three options for DHCP servers:
20 -
21 -* Using a processor with a Control Subnet (only available on certain processors)
22 -* Using the built-in [[ShowRunnerCLC™ DHCP Server>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]] (available on all processors running ShowRunnerCLC™ v3.009 or newer)
23 -* Using third party DHCP server software on your computer
24 -
25 -Most devices (DIN-CENCN-2, TSW, ZUMNET-JBOXs) rely only on IP-ID to identify themselves to the processor, but some devices (such as GLPACs, DMX controllers, and other processors) have IP addresses that are explicitly defined in the configuration file. The DHCP server should be configured to assign IP addresses that are visible to the processor, but excluded from assigning these explicitly defined IP addresses if possible.
26 -
27 -Configuring ZUMNET-JBOXs can be broken up into two separate processes:
28 -
29 -1. Identifying which DHCP assigned IP address corresponds to each ZUMNET-JBOX
30 -1. Connecting to each ZUMNET-JBOX and assigning a permanent static IP address and IP-ID
31 -
32 -== Identifying ZUMNET-JBOXs ==
33 -
34 -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.
35 -
36 -There are three primary ways of identifying ZUMNET-JBOXs:
37 -
38 -1. Identifying by hostname
39 -1. Identifying by serial number or MAC address
40 -1. Identifying through Device Tree View
41 -
42 -Each of these methods involves generating a Device Summary using the Device Discovery Tool in Toolbox. The Device Summary is a file which lists all devices that are discoverable on the network along with useful information such as their hostname, IP address, and MAC address.
43 -
44 -To generate a Device Summary in Toolbox:
45 -
46 -* Connect to the lighting network and open Device Discovery Tool in Toolbox
47 -* The Device Discovery tool will automatically report how many Ethernet devices have been discovered
48 -* Verify that the expected number of Ethernet devices have been discovered, including any TSWs, GLPACs, DIN-CENCN-2s, etc.
49 -** Note that only Crestron devices will appear in Device Discovery; non-Crestron devices (such as Pharos or Enttec DMX controllers) will not appear in Device Discovery Tool
50 -** If no devices are discovered, verify that your computer is connected to the network and your IP address is compatible with the network
51 -** If some devices are missing, there may be an issue with your DHCP server settings or the network wiring
52 -* Click the "Export..." button below the list of discovered devices
53 -** If this button says "Address Book", then Toolbox needs to be updated
54 -* Click the Write Device Summary button and save the Device Summary to your computer
55 -** Though saved as a text file, the Device Summary is actually a table of comma separated values
56 -** 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
57 -
58 -See the [[Export to Device Summary>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Preparation.Toolbox Basics.WebHome||anchor="HExporttoDeviceSummary"]] section of the Toolbox Basics page for more detail.
59 -
60 -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.
61 -
62 -=== Identifying by Hostname ===
63 -
64 -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 ShowRunnerCLC™ 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 ShowRunnerCLC™ logic in order to minimize disruption to end-users in the event of a processor or network failure.
65 -
66 -In addition to configuring default room logic, the Crestron Zūm App can be used to change the hostname of the ZUMNET-JBOX for each room. By default, the hostname for a ZUMNET-JBOX is the model followed by the last six digits of the MAC address, e.g. "ZUMNET-JBOX-16A-LV-F2DA94". If you or the electrical contractor already intend to configure the internal logic each ZUMNET-JBOX, it would be a good idea to also change the hostname to something more identifiable.
67 -
68 -To change the hostname using the Crestron Zūm App:
69 -
70 -* Connect to the ZUMNET-JBOX in the App
71 -* Tap "Room Settings"
72 -* Tap "Network"
73 -* Tap the Hostname field and edit the Hostname
74 -* Scroll to the bottom of the page and tap "Save settings"
75 -* Tap "OK" to apply the changes and reboot the ZUMNET-JBOX
76 -** Note that rebooting the JBOX will cause the lights to briefly cut out
77 -
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 -
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 -
82 -=== Identifying by Serial Number or MAC Address ===
83 -
84 -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.
85 -
86 -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.
87 -
88 -=== Identifying through Network Device Tree View ===
89 -
90 -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.
91 -
92 -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.
93 -
94 -* Generate a Device Summary and note the IP addresses for all installed ZUMNET-JBOXs
95 -* Connect to the first ZUMNET-JBOX using Network Device Tree View
96 -* Locate the "ZUMNET-JBOX-xx-xx-LOCAL" device in the list of connected devices
97 -** The model will vary between 0-10V and DALI JBOXs
98 -** The ID should be "03" regardless of model
99 -* Right click the device and press "Identify This Device..." from the context menu
100 -* The device will blink any attached fixtures and make an alarm sound
101 -* Walk around the jobsite until the room/controlled fixtures are located
102 -* Edit the Device Summary or SRTakeoff.xlsx so that you remember which JBOX is which
103 -* Repeat for each ZUMNET-JBOX until all of the ZUMNET-JBOXs have been identified
104 -
105 -Once you have determined and recorded which ZUMNET-JBOX is which, you may proceed to IP configuration.
106 -
107 -== Assigning Permanent Static IP Addresses and IP-IDs ==
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.
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 -
113 -* Open Text Console in Toolbox and connect to the first ZUMNET-JBOX
114 -* 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)
115 -** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.80**(%%)##
13 +* Open Text Console in Toolbox and connect to the DIN-CENCN-2
14 +* Run the following commands to configure the DIN-CENCN-2's IP settings (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a CENCN-2 IP address of (% style="color:blue" %)**10.0.0.12**(%%), a CENCN-2 IP-ID of (% style="color:olive" %)**D1**(%%), a processor IP address of (% style="color:orange" %)**10.0.0.10**(%%), and a hostname of (% style="color:purple" %)**CENCN-L1**(%%))
15 +** Disable DHCP: ##dhcp 0 off##
16 +** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)##
116 116  ** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)##
117 117  ** Set default gateway: ##defr 0 **10.0.0.1**##
118 -** Update IP table: ##addm (% style="color:olive" %)**30**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
119 -** Set hostname: ##host (% style="color:purple" %)**ZNET-JBOX-RM-201**(%%)##
120 -** Disable DHCP: ##dhcp off##
121 -** Reboot the ZUMNET-JBOX: ##reboot##
122 -*** Note that rebooting the JBOX will cause the lights to briefly cut out
123 -* Repeat for all ZUMNET-JBOXs on the job
19 +** Update IP table: ##addm (% style="color:olive" %)**D1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
20 +** Set hostname: ##host (% style="color:purple" %)**CENCN-L1**(%%)##
21 +** Reboot the DIN-CENCN-2: ##reboot##
22 +* Repeat for all DIN-CENCN-2s on the job
124 124  
125 -= Zūm Net Specific Configuration =
24 +=== Moving Cresnet Devices ===
126 126  
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.
26 +In SHOWRUNNER™, which Net each Cresnet cable is landed on is important. Each DIN-CENCN-2 is firmware limited to a maximum of 25 Cresnet devices per Net, and which CENCN-2/Net each device is on is tracked in the configuration file. If devices are moved between DIN-CENCN-2s or moved between Nets on the same DIN-CENCN-2, then the configuration file must be updated. Every device in the configuration has a ##"DeviceHostId"## (the host DIN-CENCN-2's IP-ID) and a ##"DeviceHostBranch"## (the Net of the DIN-CENCN-2) associated with it.
128 128  
129 -== Updating Firmware ==
28 +When moving devices between Nets or between DIN-CENCN-2's it is important to keep in mind several things:
130 130  
131 -(% class="box errormessage" %)
132 -(((
133 -Per Crestron's Zūm Wired firmware v4.01.06.02 release notes, devices running firmware v3.09.05 or earlier "are not supported for upgrade via the Zum App / Hub / or Toolbox" and users should contact Crestron True Blue Support for upgrade paths when required.
134 -)))
135 -
136 -Zūm Wired  The recommended process for updating Zūm Wired firmware is:
137 -
138 -1. Ensure that the ZUMNET-JBOX for the room is in Primary / Zūm Mode (see below) so that it will re-address all connected Zūm Link devices
139 -1. Connect to the ZUMNET-JBOX in Network Device Tree View and verify that all expected Zūm Link devices are online and that there are no conflicting/duplicate IDs
140 -1*. We have run into issues where devices will not always be uniquely addressed, typically as a result of cabling termination issues (incorrect pin-out or use of "EZ RJ45" passthrough connectors)
141 -1*. Occasionally, ZUMLINK-KP will be stuck at ID 03 after the ZUMNET-JBOX has been put into Primary/App Mode - in these cases, briefly disconnecting the keypad, reconnecting it, and waiting a few minutes will allow the keypad's address to be changed
142 -1. Use the Zūm Wired .puf file or the Firmware Updating Script tool built into ShowRunner™ to update all the ZUMNET-JBOXs
143 -1*. Note that as part of the update process, the ZUMNET-JBOX will reboot, which will cycle the connected load and briefly interrupt Ethernet connection to any downstream ZUMNET-JBOXs or other Ethernet devices, which in rare instances will cause the firmware update to fail
144 -1. Verify that all the ZUMNET-JBOXs have successfully updated by using the Device Discovery Tool device export and checking the reported firmware version
145 -
146 -Alternatively, rooms can be updated through the Crestron Zūm App as of firmware v1.03.54, however only one room can be upgraded at a time and your mobile device will become occupied for the duration of the firmware upgrade (15-45 minutes depending on firmware version and quantity of Zūm Wired devices in the room)
147 -
148 -== Primary/Secondary Mode ==
149 -
150 -(% class="box warningmessage" %)
151 -(((
152 -Zūm Wired firmware v1.03.27 (device firmware v1.002.00026) updates the terminology from "master"/"slave" to "primary"/"secondary", and changes the ##zwms## command to ##zwps##
153 -Devices running this newer firmware will not accept commands using "master"/"slave" as arguments.
154 -)))
155 -
156 -ZUMNET-JBOXs can be in either "Primary" or "Secondary" mode. In most situations, "Primary" is the desired mode of operations, as "Secondary" mode effectively turns a ZUMNET-JBOX into a ZUMLINK-JBOX and prevents it from discovering devices on the Zūm Link bus or performing any logic. There are two scenarios in which a ZUMNET-JBOX should be configured in "Secondary" mode:
157 -
158 -1. It is connected to another ZUMNET-JBOX via the Zūm Link bus
159 -1. It is being used as a Cresnet device, connected to a processor or DIN-CENCN-2 using a Cresnet/Zūm Link adapter
160 -
161 -ZUMNET-JBOXs with firmware 1.006.00012 or newer will ship from the factory in "Primary" mode, but will go to "Secondary" mode if a hardware reset is performed. ZUMNET-JBOXs with older firmware will ship in "Secondary" mode. The commands to view or change the Primary/Secondary mode are:
162 -
163 -* View current mode:
164 -** Current FW: ##zwps## or ##zwmode##
165 -** Old FW: ##zwms##
166 -* Make "Primary":
167 -** Current FW: ##zwps primary##
168 -** Old FW: ##zwms master##
169 -* Make "Secondary":
170 -** Current FW: ##zwps secondary##
171 -** Old FW: ##zwms slave##
172 -
173 -A reboot is required if the mode is changed.
174 -
175 -== Zūm/Cresnet Mode ==
176 -
177 -Zūm Mode (also known as App Mode) is the default setting for ZUMNET-JBOXs shipping on newer firmware, and allows them to be configured from the Crestron Zūm App as long as a ZUMLINK-KP is connected to the JBOX. 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.
178 -
179 -Generally, ZUMNET-JBOXs do not need to be in Cresnet mode to work with ShowRunnerCLC™ except in specific cases:
180 -
181 -* ZUMNET-JBOX-DALI controllers are being used in legacy mode
182 -* Site-specific security requirements do not allow for wireless connectivity to the lighting controls
183 -* Certain ShowRunnerCLC™ features are required (such as changing the dimming response curve)
184 -* On older versions of firmware, Cresnet mode was required if non-Zūm Link devices were connected to the ZUMNET-JBOX (e.g. a GL-EXP-DIMU-CN phase dimmer or C2N-CBD-P Cameo keypads)
185 -** This is no longer the case on recent firmware, and ZUMNET-JBOXs with Cresnet hardware connected to them can be left in Zūm/App mode, though the Cresnet hardware will not be able to function without the control processor
186 -
187 -When a ZUMNET-JBOX is in Zūm Mode and configured to communicate with a processor running ShowRunnerCLC™ software, it is operating in a kind of "App Plus" mode, where any actions that are defined in ShowRunnerCLC™ are performed "on top of" the actions defined in the App:
188 -
189 -* A keypad with actions defined in the Zūm App will perform actions defined in ShowRunnerCLC™ in addition to those App-defined actions while the ZUMNET-JBOX is in Zūm Mode
190 -** This is useful when trying to add functionality to a keypad, such as allowing the keypad to control devices not available in the Zūm App (e.g. shades, loads that are controlled by other ZUMNET-JBOXs or Cresnet load controllers, etc.), but can cause confusion in other situations where there are conflicts between the App-defined actions and the ShowRunnerCLC™-defined actions (e.g. if a rocker keypad with the default All On and All Off actions defined in the App is programmed in ShowRunnerCLC™ to act as a single load toggle, it will not work correctly)
191 -** A ZUMLINK-KP that is disabled from ShowRunnerCLC™ (i.e. by using the Keypad Disable function) will not perform any actions
192 -** A ZUMLINK-KP that has null actions defined in the Zūm App will only perform those actions that are defined in ShowRunnerCLC™
193 -* If occupancy sensor load assignments in the App do not match ShowRunnerCLC™, then odd behavior may result
194 -
195 -The commands to view or change the Zūm/Cresnet mode are:
196 -
197 -* View current mode: ##zwmode##
198 -* Make Zūm/App mode: ##zwmode zum##
199 -* Make Cresnet mode: ##zwmode cnet##
200 -
201 -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.
202 -
203 -=== DALI Group/Legacy Mode ===
204 -
205 -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.
206 -
207 -To change modes, run the appropriate dalisetmode command, wait 5 seconds, and then reboot the ZUMNET-JBOX-DALI:
208 -
209 -* Set Legacy mode: ##dalisetmode 1 1##
210 -* Set Groups mode: ##dalisetmode 1 2##
211 -
212 -=== Zūm Mode Auto Switch ===
213 -
214 -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.
215 -
216 -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)
217 -
218 -Enable Zūm Mode Auto Switch using the command: ##autoswitch on##
219 -
220 -Rebooting after changing Auto Switch modes is not officially required, but is still recommended.
221 -
222 -//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.//
223 -
224 -== Changing IP-IDs ==
225 -
226 -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.
227 -
228 -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.
229 -
230 -If a ZUMNET-JBOX is assigned a different IP-ID, then it's own ##"DeviceHostId"## as well as the ##"DeviceHostId"## for all hosted Zūm Link devices must be changed to the new IP-ID. In addition to changing these ##"DeviceHostId"##, the ##"IpId"## for the associated entry in ##"IpDevices"## must be updated. ##"IpDevices"## are located towards the beginning of the configuration file. Note that while the ##"DeviceHostId"## is in hexadecimal, the ##"IpId"## is a decimal integer. This means that a ZUMNET-JBOX with ##"DeviceHostId": "31"## would be associated with an entry in ##"IpDevices"## with ##"IpId": 49##
231 -
232 -Below are two snippets from a configuration file comparing a ZUMNET-JBOX-16A-LV lighting controller and it's associated entry in ##"IpDevices"##:
233 -
234 -[[image:1655247008527-737.png]]
235 -
236 -[[image:1655246948921-246.png]]
30 +1. Cresnet IDs (##"DeviceConnectionId"##) cannot conflict with the Cresnet ID of any other devices defined in the config on the same host ID and branch
31 +1. Cresnet IDs must be in the hexadecimal range 03 to 1B
32 +1. Any children devices (such as NS occ sensors, photocells, GLPPA-KP keypads, etc.) must also be moved. If the parent Cresnet ID is changed then the children IDs must also be updated
33 +1. If devices are moved from a DIN-CENCN-2 to be landed directly on a processor (or landed on a DIN-HUB on a processor), then the device host ID should be ##null## and the host branch should be ##0##
1655246948921-246.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -10.6 KB
Content
1655247008527-737.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -41.8 KB
Content
1655410981707-782.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -5.6 KB
Content
1655410997733-287.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 KB
Content
1655411066727-374.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -3.2 KB
Content
1655487002500-174.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
1655487008788-390.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
1655487020590-542.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
1655487132138-904.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -53.0 KB
Content