Wiki source code of *Design Considerations
Version 10.4 by Alexander Mott on 2023/03/24 18:32
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 locally | ||
8 | |||
9 | |||
10 | distributed lighting control platform that utilizes advanced sensors and industry standard dimming protocols to provide automated control of a building's lighting. | ||
11 | |||
12 | |||
13 | |||
14 | |||
15 | |||
16 | |||
17 | |||
18 | |||
19 | |||
20 | (% class="box warningmessage" %) | ||
21 | ((( | ||
22 | Add more to intro | ||
23 | ))) | ||
24 | |||
25 | = Hardware Modes = | ||
26 | |||
27 | Lorem | ||
28 | |||
29 | == CNET Mode == | ||
30 | |||
31 | Lorem | ||
32 | |||
33 | == App Mode == | ||
34 | |||
35 | Lorem | ||
36 | |||
37 | == Primary vs Secondary == | ||
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 | ))) |