Wiki source code of *Design Considerations

Version 10.5 by Alexander Mott on 2023/03/24 18:37

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.5 9 The purpose of this article is to
Alexander Mott 7.1 10
Alexander Mott 5.2 11 (% class="box warningmessage" %)
12 (((
13 Add more to intro
14 )))
15
Alexander Mott 10.2 16 = Hardware Modes =
Alexander Mott 5.2 17
Alexander Mott 10.2 18 Lorem
Alexander Mott 5.2 19
Alexander Mott 10.2 20 == CNET Mode ==
Alexander Mott 5.2 21
22 Lorem
23
Alexander Mott 10.2 24 == App Mode ==
Alexander Mott 5.2 25
26 Lorem
27
Alexander Mott 10.2 28 == Primary vs Secondary ==
Alexander Mott 5.2 29
30 Lorem
31
Alexander Mott 10.5 32 == Security ==
33
34 Lorem
35
Alexander Mott 10.2 36 = Control Paradigms =
Alexander Mott 5.2 37
Alexander Mott 10.4 38 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 39
Alexander Mott 1.1 40
Alexander Mott 10.3 41 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 42
Alexander Mott 10.2 43 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,
44
Alexander Mott 10.3 45 Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
46
47 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.
48
Alexander Mott 10.2 49 == Standalone ==
50
Alexander Mott 1.1 51 Lorem
52
Alexander Mott 10.2 53 == Networked ==
Alexander Mott 1.1 54
55 Lorem
56
Alexander Mott 10.2 57 === Networked with Default Program ===
Alexander Mott 1.1 58
59 Lorem
60
Alexander Mott 10.2 61 === Networked with SHOWRUNNER™ ===
Alexander Mott 1.1 62
63 Lorem
64
Alexander Mott 10.2 65 == Start-Up Considerations ==
Alexander Mott 1.1 66
67 Lorem
68
Alexander Mott 10.2 69 == Processor Selection for Networked Systems ==
Alexander Mott 1.1 70
71 Lorem
72
73 = Device Count Limitations =
74
75 Lorem
76 )))