Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 10.4
edited by Alexander Mott
on 2023/03/24 18:32
Change comment: (Autosaved)
To version 8.1
edited by Alexander Mott
on 2023/03/24 18:14
Change comment: Deleted image "1679680613279-474.png"

Summary

Details

Page properties
Content
... ... @@ -4,10 +4,9 @@
4 4  
5 5  (% class="row" %)
6 6  (((
7 -Crestron Zūm Wired is a locally
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 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 11  
12 12  
13 13  
... ... @@ -15,63 +15,56 @@
15 15  
16 16  
17 17  
18 -
19 -
20 20  (% class="box warningmessage" %)
21 21  (((
22 22  Add more to intro
23 23  )))
24 24  
25 -= Hardware Modes =
22 += Control Paradigms =
26 26  
27 -Lorem
24 +Zūm Wired systems can be designed as either standalone or networked applications.
28 28  
29 -== CNET Mode ==
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  
28 +== Standalone ==
29 +
31 31  Lorem
32 32  
33 -== App Mode ==
32 +== Networked ==
34 34  
35 35  Lorem
36 36  
37 -== Primary vs Secondary ==
36 +=== Networked with Default Program ===
38 38  
39 39  Lorem
40 40  
41 -= Control Paradigms =
40 +=== Networked with SHOWRUNNER™ ===
42 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.
42 +Lorem
44 44  
44 += Standalone vs Networked Systems =
45 45  
46 -The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
46 +== Start-Up Considerations ==
47 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 56  Lorem
57 57  
58 -== Networked ==
50 +== Processor Selection for Networked Systems ==
59 59  
60 60  Lorem
61 61  
62 -=== Networked with Default Program ===
54 += Hardware Modes =
63 63  
64 64  Lorem
65 65  
66 -=== Networked with SHOWRUNNER™ ===
58 +== CNET Mode ==
67 67  
68 68  Lorem
69 69  
70 -== Start-Up Considerations ==
62 +== App Mode ==
71 71  
72 72  Lorem
73 73  
74 -== Processor Selection for Networked Systems ==
66 +== Primary vs Secondary ==
75 75  
76 76  Lorem
77 77  
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