Skip to Content
Version 14.23 by Alexander Mott on 2023/03/27 20:23
Show last authors
1 {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 {{toc/}}
3 {{/box}}
4
5 (% class="row" %)
6 (((
7 Crestron Zūm Wired is a distributed lighting control system that has various global and local control options. Zūm Wired uses industry standard dimming protocols (DALI, 0-10V, and phase dimming) and advanced sensors to provide automated control of a building or facility's lighting. With certain designs, it is also possible to integrate control over DMX fixtures, building management systems, and other third-party devices (such as motorized shades and HVAC).
8
9 The purpose of this article is to explain various important concepts that must be understood in order to design a system that meets the requirements of all project stakeholders.
10
11 = System Overview and Hardware Modes =
12
13 Zūm Wired systems consist of ZUMNET-JBOX-* room controllers and a number of connected ZUMLINK-* devices. ZUMLINK-* devices can be ZUMLINK-JBOX-* load controllers, ZUMLINK-OCC-* presence detectors, or ZUMLINK-KP-R-W keypads (wall switches). ZUMNET-JBOX-* and ZUMLINK-JBOX-* devices have additional inputs for third-party presence detectors, 0-10V analog photocells, and contact-closure local override.
14
15 ZUMNET-JBOX-* room controllers can be operated in App Mode or CNET Mode, with an additional setting to be either the Primary room controller or a Secondary load controller.
16
17 == App Mode ==
18
19 (% class="box warningmessage" %)
20 (((
21 add more here
22 )))
23
24 If devices in App Mode are being used as part of a networked system running a custom program, then any configuration changes made through the Zūm App should be made while the device is disconnected from the processor. The easiest ways to accomplish this are to either disconnect the Cat5e/Cat6 cable at the processor, or stop the program running on the processor using Text Console commands.
25
26 == CNET Mode ==
27
28 Using ZUMNET-JBOX-* devices in CNET Mode is only possible on a networked system with a processor that is running a custom program. While in CNET Mode, ZUMNET-JBOX-* devices do not process any local logic and cannot be connected to through the Zūm App in order to be configured. This is because while in CNET Mode, ZUMNET-JBOX act as a "dumb" Cresnet-to-Ethernet bridge with a built-in load controller. They report all Zūm Link traffic back to the control processor and do not do any "thinking" on their own. Any attached ZUMLINK-KP or ZUMLINK-OCC-* devices will not work without the processor if the ZUMNET-JBOX is in CNET Mode.
29
30 CNET Mode has some benefits over App Mode. Compared to App Mode, CNET Mode offers direct control of all hardware which enables the system to meet a wider range of sequences. Additionally, CNET Mode offers increased security as it is not possible to connect to a device with the Zūm App while it is in CNET Mode.
31
32 The two main drawbacks of using CNET Mode are the requirement for a networked system with a custom program and the loss of local control in the event that connection to the control processor is lost, however the introduction of the Zūm Mode Auto Switch feature in .puf firmware v1.04.05 (device firmware v1.004.00005) has eliminated this second drawback by enabling devices to automatically switch between CNET and Zūm Modes when connection to the processor is lost or regained.
33
34 //As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured in CNET mode, though this may change in the future.//
35
36 == Zūm Mode Auto Switch ==
37
38 Zūm Mode Auto Switch is a feature introduced 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.
39
40 Enabling this feature eliminates the biggest drawback of designing a system to use ZUMNET-JBOX-* devices in CNET Mode.
41
42 //As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured with Zūm Mode Auto Switch disabled, as this feature is only intended to be used with systems that are running custom programs.//
43
44 == Security Considerations ==
45
46 Any ZUMNET-JBOX that is running in App Mode with an attached ZUMLINK-KP can be connected to via the Crestron Zūm App, which is publicly available in the Google Play store. Although unlikely, it is technically possible that a bad actor could download the Zūm App and interfere with the lighting controls. Crestron ships all ZUMNET-JBOX-* devices with a default PIN that is intended to be changed during commissioning, however there is no guarantee that the technician who configured the Zūm Wired hardware knew or remembered to do this.
47
48 One way to counteract this security risk is to design the system to operate with the ZUMNET-JBOX-* devices in CNET Mode. In CNET Mode, it is impossible to connect to any devices using the Zūm App. Leaving the Zūm Mode Auto Switch function disabled will add another layer of security in exchange for a loss of localized control when the system is experiencing issues, as devices will stay in CNET Mode even when connection to the control processor is lost.
49
50 == Primary vs Secondary Mode ==
51
52 (% class="box infomessage" %)
53 (((
54 Note: the terminology used for these modes was modified in .puf firmware v1.03.27 (device firmware v1.002.00026). Hardware delivered with older firmware will require the use of different commands to change modes during start-up.
55 )))
56
57 ZUMNET-JBOX-* devices can be set to be either the Primary room controller or a Secondary load controller. There must only be one Primary ZUMNET-JBOX on a given Zūm Link bus, and in a networked system the Primary ZUMNET-JBOX is the one that should be connected to the Zūm Net.
58
59 * In Primary mode, the ZUMNET-JBOX acts as the Zūm Link host, and is able to detect all connected Zūm Link devices. If connected to in Crestron Toolbox, a Primary ZUMNET-JBOX can be used to view and manually address any connected ZUMLINK-* devices. While in App mode, a ZUMNET-JBOX in Primary mode is the logical room controller for the space and is the device that should be used for configuration via the Zūm App.
60 * In Secondary mode, the ZUMNET-JBOX acts as if it were a ZUMLINK-JBOX. It does not process any room control logic, and when connected to via Crestron Toolbox it will not be able to see any other ZUMLINK-* devices. Using Secondary mode is rare, and should only be used in cases where a spare ZUMNET-JBOX is being used to add a load to another ZUMNET-JBOX or replace a ZUMLINK-JBOX that has been lost or damaged.
61
62 //As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured in Secondary mode, however they have announced their intention to begin shipping hardware on newer firmware preconfigured in Primary mode.//
63
64 = Control Paradigms =
65
66 Designs for Zūm Wired systems are broadly categorized as either "standalone" or "networked" designs. Both standalone and networked systems should be designed with one ZUMNET-JBOX-* per room or logical control space connected to a number of ZUMLINK-* devices within that same space. In networked systems, there is also a control processor which provides centralized control of the entire system. ZUMNET-JBOX-* must be daisy-chained together with Zūm Net and then connected back to the processor. In standalone applications, there is no processor and no Zūm Net cabling connecting different rooms to each other.
67
68
69 (% class="box warningmessage" %)
70 (((
71 The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
72 )))
73
74 (% class="box warningmessage" %)
75 (((
76 In standalone applications, each room has one ZUMNET-JBOX-* with a number of connected ZUMLINK-* devices. There is no Zūm Net connecting different rooms,
77 )))
78
79 (% class="box warningmessage" %)
80 (((
81 Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
82 )))
83
84 (% class="box warningmessage" %)
85 (((
86 Depending on which control paradigm is selected, there will be various impacts to the hardware cost, start-up cost, start-up complexity, ease of maintenance, control capabilities, integration with third-party systems, available user interfaces, and the ability to meet a provided sequence of operations.
87 )))
88
89 == Standalone ==
90
91 Standalone Zūm Wired designs consist of completely independent Zūm Rooms. Each Zūm Room has a single ZUMNET-JBOX-* with any number of ZUMLINK-* devices connected to it. There is no Zūm Net connecting individual rooms, and there is no processor required. This results in a system which has a reduced hardware cost and can theoretically be commissioned and configured entirely by the electrical contractor, however there are some important drawbacks to consider.
92
93 The primary benefits of a standalone Zūm Wired system are:
94
95 * Reduced installation time and cost as no Zūm Net cabling is required between rooms
96 * Reduced hardware cost as no ZUM-HUB4 or networking hardware is required
97 * Theoretically possible to start-up using only the Crestron Zūm App, with no programming or specialty software required
98
99 Some drawbacks of a standalone Zūm Wired system are:
100
101 * As of 2/2023, ZUMNET-JBOX-* devices ship with factory settings that are incompatible with an App only startup, resulting in extra expense to configure and update devices prior to installation or extra time spent during startup to accomplish these tasks post-installation:
102 ** ZUMNET-JBOX-* devices must be manually set to Zūm App mode
103 ** ZUMNET-JBOX-* devices must be manually set to Primary mode
104 ** Updating firmware with the Crestron Zūm App is not possible with out-of-the-box firmware and must be initially done through Toolbox
105 * ZUMNET-JBOX-* devices can only be connected to via the App if there is a ZUMLINK-KP on their Zūm Link bus
106 ** During start-up, a technician must bring a ZUMLINK-KP to connect to the ZUMNET-JBOX in order to configure any rooms that were designed without a ZUMLINK-KP
107 * Firmware updates through the Zūm App can consume a large amount of time on-site
108 ** Only one room can be updated at a time using the Zūm App, and it is not possible to do anything else while the room is updating
109 ** The time required to update a room's firmware varies depending on the number of ZUMLINK devices in the room
110 * Standalone systems are limited compared to Networked systems in terms of what sequences can be met
111 ** No scheduling capabilities
112 ** No support for third-party integrations beyond the override contact-closure relay at each ZUMNET/ZUMLINK-JBOX and the relay output of any *-RLY model occupancy sensors
113 ** No support for DMX control
114 ** Any future modifications to the sequence requires reconfiguration through the Zūm App
115 * No support for Cresnet devices
116 * No cross-room control capabilities (i.e., ZUMLINK-* keypads and occupancy sensors are restricted to controlling loads that are attached to the same ZUMNET-JBOX as they are)
117 * No possibility for remote support or management, as the only way to connect to any of the devices is by being using the Zūm App, which requires being within Bluetooth range of the device
118 * Potential security concerns if the default PINs are not changed during start-up
119
120 == Networked ==
121
122 Networked systems are generally preferred over standalone systems for most applications. Networked systems, and in particular networked systems with custom programming, are able to meet a much wider variety of sequences compared to standalone systems. Additionally, start-up and maintenance can be simplified, and certain aspects completed remotely, compared to standalone systems.
123
124 In general, the drawbacks of any networked system are:
125
126 * Requires additional hardware (at minimum a processor and a network switch for the Zūm Net)
127 * Requires additional Zūm Net cabling between rooms
128 * Additional start-up time required to configure the program
129
130 All networked systems have the following benefits:
131
132 * Some aspects of start-up can be accomplished remotely if there is remote access to the lighting network
133 * Updating firmware and modifying hardware configurations can be accomplished over Zūm Net
134 ** Loadscripts can be written to simultaneous update firmware for up to 10 rooms
135 *** These can be run remotely if there is remote access to the lighting network, or scheduled by the technician to execute after working hours in order to free up time on-site
136 ** Loadscripts can be written to bulk modify hardware settings (such as changing from Secondary to Primary modes) and configure IP settings (such as changing hostnames or updating IP tables)
137 * Able to meet a wider range of sequences compared to standalone systems
138 ** Scheduling capabilities
139 ** BMS/BACnet integration
140
141 === Networked with Default Program ===
142
143 Some benefits of using the default program are:
144
145 *
146
147 Some drawbacks of using the default program are:
148
149 * Requires a ZUM-HUB4 processor (other types of processors can only be used with a custom program)
150 * Limited support for Cresnet devices on the Zūm Link bus (n**o support?**)
151 * Limited scheduling capabilities
152
153 === Networked with Custom Program ===
154
155 Some benefits of using a custom program such as SHOWRUNNER™ are:
156
157 *
158
159 Some drawbacks of using a custom program such as SHOWRUNNER™ are:
160
161 *
162
163 = Hardware Design Limitations =
164
165 There are a handful of limitations to keep in mind when designing Zūm Wired systems, with different restrictions applying to Zūm Net and Zūm Link:
166
167 Zūm Net limitations:
168
169 * Do not exceed 100m or 328' between subsequent ZUMNET-JBOX-* devices, or between the first ZUMNET-JBOX and the network switch
170 * Do not exceed 20 ZUMNET-JBOX-* devices on a single run of Zūm Net
171 * Do not "loop" Zūm Net cables (i.e., cables should start at the network switch and end at the last ZUMNET-JBOX, without a returning cable from the last device back to the switch)
172
173 Zūm Link limitations:
174
175 * Do not exceed 31 ZUMLINK-* and Cresnet devices on a single ZUMNET-JBOX-* device
176 * Do not exceed 85mA of 24VDC power consumption per ZUMNET/ZUMLINK-JBOX-* device on the Zūm Link bus
177 ** Each ZUMNET/ZUMLINK-JBOX-* is limited to 85mA of 24VDC output shared across their Zūm Link ports and sensor inputs
178 ** Power is shared between ZUMNET/ZUMLINK-JBOX-* devices on a single Zūm Link bus, so adding more ZUMNET/ZUMLINK-JBOX-* devices to a network increases the available power
179 ** ZUMLINK-IR-QUATTRO-HD-DLS/RLY occupancy sensors are rated at 32mA of power consumption
180 ** Other ZUMLINK-OCC-* sensors are rated at 25mA of power consumption each
181 ** ZUMLINK-KP keypads do not have a listed power consumption, but designing for approximately 20mA is safe
182 * Available power on the Zūm Link bus can be increased by adding additional ZUMLILNK-JBOX-* devices, or by adding a separate power pack to provide power for non-system sensors or Cresnet devices on the Zūm Link bus
183 )))