Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 10.6
edited by Alexander Mott
on 2023/03/24 18:42
Change comment: (Autosaved)
To version 7.1
edited by Alexander Mott
on 2023/03/24 18:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,68 +4,66 @@
4 4  
5 5  (% class="row" %)
6 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).
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.
8 8  
9 -The purpose of this article is to explain
10 10  
11 11  
12 12  
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 14  
15 -= ZUMNET-JBOX Hardware Modes =
16 16  
17 -Lorem
18 18  
19 -== CNET Mode ==
20 20  
21 -Lorem
22 22  
23 -== App Mode ==
17 +(% class="box warningmessage" %)
18 +(((
19 +Add more to intro
20 +)))
24 24  
25 -Lorem
22 += Control Paradigms =
26 26  
27 -== Primary vs Secondary ==
24 +Zūm Wired systems can be designed as either standalone or networked applications.
28 28  
29 -Lorem
26 +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,
30 30  
31 -== Security ==
28 +== Standalone ==
32 32  
33 33  Lorem
34 34  
35 -= Control Paradigms =
32 +== Networked ==
36 36  
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.
34 +Lorem
38 38  
36 +=== Networked with Default Program ===
39 39  
40 -The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
38 +Lorem
41 41  
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,
40 +=== Networked with SHOWRUNNER™ ===
43 43  
44 -Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
42 +Lorem
45 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.
44 += Standalone vs Networked Systems =
47 47  
48 -== Standalone ==
46 +== Start-Up Considerations ==
49 49  
50 50  Lorem
51 51  
52 -== Networked ==
50 +== Processor Selection for Networked Systems ==
53 53  
54 54  Lorem
55 55  
56 -=== Networked with Default Program ===
54 += Hardware Modes =
57 57  
58 58  Lorem
59 59  
60 -=== Networked with SHOWRUNNER™ ===
58 +== CNET Mode ==
61 61  
62 62  Lorem
63 63  
64 -== Start-Up Considerations ==
62 +== App Mode ==
65 65  
66 66  Lorem
67 67  
68 -== Processor Selection for Networked Systems ==
66 +== Primary vs Secondary ==
69 69  
70 70  Lorem
71 71  
1679680613279-474.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +11.3 KB
Content
image1.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.MarkKohlmann
Size
... ... @@ -1,0 +1,1 @@
1 +43.8 KB
Content
image2.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.MarkKohlmann
Size
... ... @@ -1,0 +1,1 @@
1 +40.0 KB
Content