Wiki source code of *Design Considerations

Version 10.6 by Alexander Mott on 2023/03/24 18:42

Hide last authors
Alexander Mott 4.2 1 {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 {{toc/}}
3 {{/box}}
Alexander Mott 3.1 4
Alexander Mott 1.1 5 (% class="row" %)
6 (((
Alexander Mott 10.5 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).
Alexander Mott 1.1 8
Alexander Mott 10.6 9 The purpose of this article is to explain
Alexander Mott 7.1 10
Alexander Mott 5.2 11
12
Alexander Mott 10.6 13 the various control paradigms available with Zūm Wired and the different modes that Zūm Wired devices can be operated in, and the impacts on the system's capabilities that must be cons
14
15 = ZUMNET-JBOX Hardware Modes =
16
Alexander Mott 10.2 17 Lorem
Alexander Mott 5.2 18
Alexander Mott 10.2 19 == CNET Mode ==
Alexander Mott 5.2 20
21 Lorem
22
Alexander Mott 10.2 23 == App Mode ==
Alexander Mott 5.2 24
25 Lorem
26
Alexander Mott 10.2 27 == Primary vs Secondary ==
Alexander Mott 5.2 28
29 Lorem
30
Alexander Mott 10.5 31 == Security ==
32
33 Lorem
34
Alexander Mott 10.2 35 = Control Paradigms =
Alexander Mott 5.2 36
Alexander Mott 10.4 37 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.
Alexander Mott 5.2 38
Alexander Mott 1.1 39
Alexander Mott 10.3 40 The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
Alexander Mott 4.3 41
Alexander Mott 10.2 42 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,
43
Alexander Mott 10.3 44 Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
45
46 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.
47
Alexander Mott 10.2 48 == Standalone ==
49
Alexander Mott 1.1 50 Lorem
51
Alexander Mott 10.2 52 == Networked ==
Alexander Mott 1.1 53
54 Lorem
55
Alexander Mott 10.2 56 === Networked with Default Program ===
Alexander Mott 1.1 57
58 Lorem
59
Alexander Mott 10.2 60 === Networked with SHOWRUNNER™ ===
Alexander Mott 1.1 61
62 Lorem
63
Alexander Mott 10.2 64 == Start-Up Considerations ==
Alexander Mott 1.1 65
66 Lorem
67
Alexander Mott 10.2 68 == Processor Selection for Networked Systems ==
Alexander Mott 1.1 69
70 Lorem
71
72 = Device Count Limitations =
73
74 Lorem
75 )))