Skip to Content

Wiki source code of *Design Considerations

Version 11.1 by Alexander Mott on 2023/03/24 19:24
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 == App Mode ==
16
17 Lorem
18
19 == CNET Mode ==
20
21 Lorem
22
23 == Primary vs Secondary Mode ==
24
25 (% class="box infomessage" %)
26 (((
27 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.
28 )))
29
30 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.
31
32 * 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.
33 * 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.
34
35 As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* preconfigured in Secondary mode, though this may change in the future.
36
37 == Security ==
38
39 Lorem
40
41 = Control Paradigms =
42
43 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.
44
45
46 The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
47
48 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,
49
50 Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
51
52 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.
53
54 == Standalone ==
55
56 Lorem
57
58 == Networked ==
59
60 Lorem
61
62 === Networked with Default Program ===
63
64 Lorem
65
66 === Networked with SHOWRUNNER™ ===
67
68 Lorem
69
70 == Start-Up Considerations ==
71
72 Lorem
73
74 == Processor Selection for Networked Systems ==
75
76 Lorem
77
78 = Device Count Limitations =
79
80 Lorem
81 )))