Wiki source code of *Design Considerations
Version 10.5 by Alexander Mott on 2023/03/24 18:37
Show last authors
author | version | line-number | content |
---|---|---|---|
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 | ||
10 | |||
11 | (% class="box warningmessage" %) | ||
12 | ((( | ||
13 | Add more to intro | ||
14 | ))) | ||
15 | |||
16 | = Hardware Modes = | ||
17 | |||
18 | Lorem | ||
19 | |||
20 | == CNET Mode == | ||
21 | |||
22 | Lorem | ||
23 | |||
24 | == App Mode == | ||
25 | |||
26 | Lorem | ||
27 | |||
28 | == Primary vs Secondary == | ||
29 | |||
30 | Lorem | ||
31 | |||
32 | == Security == | ||
33 | |||
34 | Lorem | ||
35 | |||
36 | = Control Paradigms = | ||
37 | |||
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. | ||
39 | |||
40 | |||
41 | The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-* | ||
42 | |||
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 | |||
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 | |||
49 | == Standalone == | ||
50 | |||
51 | Lorem | ||
52 | |||
53 | == Networked == | ||
54 | |||
55 | Lorem | ||
56 | |||
57 | === Networked with Default Program === | ||
58 | |||
59 | Lorem | ||
60 | |||
61 | === Networked with SHOWRUNNER™ === | ||
62 | |||
63 | Lorem | ||
64 | |||
65 | == Start-Up Considerations == | ||
66 | |||
67 | Lorem | ||
68 | |||
69 | == Processor Selection for Networked Systems == | ||
70 | |||
71 | Lorem | ||
72 | |||
73 | = Device Count Limitations = | ||
74 | |||
75 | Lorem | ||
76 | ))) |