Last modified by Alexander Mott on 2023/12/08 18:37

From version 4.3
edited by Alexander Mott
on 2023/03/24 18:03
Change comment: There is no comment for this version
To version 10.5
edited by Alexander Mott
on 2023/03/24 18:37
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -4,34 +4,72 @@
4 4  
5 5  (% class="row" %)
6 6  (((
7 -Crestron Zūm Wired is a distributed lighting control platform that utilizes advanced sensors and industry standard dimming protocols to provide automated control of a building's lighting.
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 8  
9 -= Standalone vs Networked Systems =
9 +The purpose of this article is to
10 10  
11 -== Start-Up Considerations for Standalone Systems ==
11 +(% class="box warningmessage" %)
12 +(((
13 +Add more to intro
14 +)))
12 12  
16 += Hardware Modes =
17 +
13 13  Lorem
14 14  
15 -== Processor Selection for Networked Systems ==
20 +== CNET Mode ==
16 16  
17 17  Lorem
18 18  
19 -= Hardware Modes =
24 +== App Mode ==
20 20  
21 21  Lorem
22 22  
23 -== CNET Mode ==
28 +== Primary vs Secondary ==
24 24  
25 25  Lorem
26 26  
27 -== App Mode ==
32 +== Security ==
28 28  
29 29  Lorem
30 30  
31 -== Primary vs Secondary ==
36 += Control Paradigms =
32 32  
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 +
33 33  Lorem
34 34  
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 +
35 35  = Device Count Limitations =
36 36  
37 37  Lorem
1679680613279-474.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -11.3 KB
Content
image1.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.MarkKohlmann
Size
... ... @@ -1,1 +1,0 @@
1 -43.8 KB
Content
image2.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.MarkKohlmann
Size
... ... @@ -1,1 +1,0 @@
1 -40.0 KB
Content