Changes for page **General Overview and Design Considerations
Last modified by Alexander Mott on 2023/12/08 18:37
To version 3.1
edited by Alexander Mott
on 2023/03/24 17:50
on 2023/03/24 17:50
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,76 +1,45 @@ 1 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}} 2 -{{toc/}} 3 -{{/box}} 4 - 5 -(% class="row" %) 1 +(% class="box errormessage" %) 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). 3 +n/a 4 +))) 8 8 9 -The purpose of this article is to explain various important concepts that must be understood in order to design a system that meets the requirements of all project stakeholders. 10 - 11 -= System Overview and Hardware Modes = 12 - 13 -Zūm Wired systems consist of ZUMNET-JBOX-* room controllers and a number of connected ZUMLINK-* devices. ZUMLINK-* devices can be ZUMLINK-JBOX-* load controllers, ZUMLINK-OCC-* presence detectors, or ZUMLINK-KP-R-W keypads (wall switches). ZUMNET-JBOX-* and ZUMLINK-JBOX-* devices have additional inputs for third-party presence detectors, 0-10V analog photocells, and contact-closure local override. 14 - 15 -== App Mode == 16 - 17 -Lorem 18 - 19 -== CNET Mode == 20 - 21 -Lorem 22 - 23 -== Primary vs Secondary Mode == 24 - 25 -(% class="box infomessage" %) 6 +(% class="box warningmessage" %) 26 26 ((( 27 - Note that prior to .puf firmware v1.03.27 (device firmware v1.002.00026), these were referred to as "master" and "slave" mode. As of February, 2023, ZUMNET-JBOX-* are still shipping on this older firmware, and so the older commands must be used to initially change the mode prior to updating device firmware.8 +n/a 28 28 ))) 29 29 30 -ZUMNET-JBOX-* devices can be set to be either the primary room controller or a secondary load controller. As of February, 2023, ZUMNET-JBOX-* 31 - 32 -* In Primary 33 - 34 -While in secondary mode, the ZUMNET-JBOX-* acts as if it were cannot detect any devices on its 35 - 36 -== Security == 37 - 11 +(% class="row" %) 12 +((( 13 +(% class="col-xs-12 col-sm-8" %) 14 +((( 38 38 Lorem 39 39 40 -= Control Paradigms = 17 +See //[[Figure 1>>WebHome||anchor="HFigure1"]]// for details. 18 +See //[[Figure 2>>WebHome||anchor="HFigure2"]]// for details. 41 41 42 - Designsfor Zūm Wired systemsare broadly categorized as either "standalone" or "networked" designs. Both standalone and networkedsystems should be designed with one ZUMNET-JBOX-* per room or logical control space connectedto a number of ZUMLINK-* deviceswithin 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.20 += Hardware Modes = 43 43 44 - 45 -The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-* 46 - 47 -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, 48 - 49 -Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program". 50 - 51 -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. 52 - 53 -== Standalone == 54 - 55 55 Lorem 56 56 57 -== N etworked ==24 +== CNET Mode == 58 58 59 59 Lorem 60 60 61 -== =Networkedwith DefaultProgram===28 +== App Mode == 62 62 63 63 Lorem 64 64 65 -== =Networked withSHOWRUNNER™===32 +== Primary vs Secondary == 66 66 67 67 Lorem 68 68 36 += Standalone vs Networked = 37 + 69 69 == Start-Up Considerations == 70 70 71 71 Lorem 72 72 73 -= =Processor Selection for Networked Systems ==42 += Processor Selection for Networked Systems = 74 74 75 75 Lorem 76 76 ... ... @@ -78,3 +78,24 @@ 78 78 79 79 Lorem 80 80 ))) 50 + 51 + 52 +(% class="col-xs-12 col-sm-4" %) 53 +((( 54 +{{box title="**CONTENTS**"}} 55 +{{toc/}} 56 +{{/box}} 57 + 58 +(% class="wikigeneratedid" id="HFigure1" %) 59 +((( 60 +[[image:Templates.Article.Template.WebHome@image1.jpg]] 61 +//Figure 1: [[Sea>>https://commons.wikimedia.org/wiki/File:Isle_of_Icacos_II.jpg]]// 62 +))) 63 + 64 +(% class="wikigeneratedid" id="HFigure2" %) 65 +((( 66 +[[image:Templates.Article.Template.WebHome@image2.jpg]] 67 +//Figure 2: [[Waves>>https://commons.wikimedia.org/wiki/File:Culebra_-_Playa_de_Flamenco.jpg]]// 68 +))) 69 +))) 70 +)))
- 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