Skip to Content

Wiki source code of *Design Considerations

Version 10.9 by Alexander Mott on 2023/03/24 18:57
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 that prior to .puf firmware v1.03.27 (device firmware v1.002.00026), these were referred to as "master" and "slave" mode. As of February, 2023, ZUMNET-JBOX-* are still shipping on this older firmware, and so the older commands must be used to initially change the mode prior to updating device firmware.
28 )))
29
30 ZUMNET-JBOX-* devices can be set to be either the primary room controller or a secondary load controller. As of February, 2023, ZUMNET-JBOX-*
31
32 * In Primary
33
34 While in secondary mode, the ZUMNET-JBOX-* acts as if it were cannot detect any devices on its
35
36 == Security ==
37
38 Lorem
39
40 = Control Paradigms =
41
42 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.
43
44
45 The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
46
47 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,
48
49 Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
50
51 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.
52
53 == Standalone ==
54
55 Lorem
56
57 == Networked ==
58
59 Lorem
60
61 === Networked with Default Program ===
62
63 Lorem
64
65 === Networked with SHOWRUNNER™ ===
66
67 Lorem
68
69 == Start-Up Considerations ==
70
71 Lorem
72
73 == Processor Selection for Networked Systems ==
74
75 Lorem
76
77 = Device Count Limitations =
78
79 Lorem
80 )))