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 2.1
edited by Alexander Mott
on 2023/03/24 16:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,27 +4,26 @@
1 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 -{{toc/}}
3 -{{/box}}
4 4  
2 +(% class="box errormessage" %)
3 +(((
4 +n/a
5 +)))
6 +(% class="box warningmessage" %)
7 +(((
8 +n/a
9 +)))
10 +
5 5  (% class="row" %)
6 6  (((
7 -Crestron Zūm Wired is a locally
13 +(% class="col-xs-12 col-sm-8" %)
14 +(((
15 +Lorem
8 8  
17 +See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details.
18 +See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details.
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.
20 += Overview =
11 11  
22 +Lorem
12 12  
13 -
14 -
15 -
16 -
17 -
18 -
19 -
20 -(% class="box warningmessage" %)
21 -(((
22 -Add more to intro
23 -)))
24 -
25 25  = Hardware Modes =
26 26  
27 27  Lorem
... ... @@ -38,44 +38,39 @@
38 38  
39 39  Lorem
40 40  
41 -= Control Paradigms =
40 += Standalone vs Networked =
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 +== Start-Up Considerations ==
44 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 56  Lorem
57 57  
58 -== Networked ==
46 += Processor Selection for Networked Systems =
59 59  
60 60  Lorem
61 61  
62 -=== Networked with Default Program ===
50 += Device Count Limitations =
63 63  
64 -Lorem
52 +Lorem
65 65  
66 -=== Networked with SHOWRUNNER™ ===
54 +)))
67 67  
68 -Lorem
69 69  
70 -== Start-Up Considerations ==
57 +(% class="col-xs-12 col-sm-4" %)
58 +(((
59 +{{box title="**CONTENTS**"}}
60 +{{toc/}}
61 +{{/box}}
71 71  
72 -Lorem
63 +(% class="wikigeneratedid" id="HFigure1" %)
64 +(((
65 +[[image:Templates.Article.Template.WebHome@image1.jpg]]
66 +//Figure 1: [[Sea>>https://commons.wikimedia.org/wiki/File:Isle_of_Icacos_II.jpg]]//
67 +)))
73 73  
74 -== Processor Selection for Networked Systems ==
75 -
76 -Lorem
77 -
78 -= Device Count Limitations =
79 -
80 -Lorem
69 +(% class="wikigeneratedid" id="HFigure2" %)
70 +(((
71 +[[image:Templates.Article.Template.WebHome@image2.jpg]]
72 +//Figure 2: [[Waves>>https://commons.wikimedia.org/wiki/File:Culebra_-_Playa_de_Flamenco.jpg]]//
81 81  )))
74 +)))
75 +)))
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