Changes for page **General Overview and Design Considerations
Last modified by Alexander Mott on 2023/12/08 18:37
To version 6.1
edited by Alexander Mott
on 2023/03/24 18:13
on 2023/03/24 18:13
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -4,66 +4,58 @@ 4 4 5 5 (% class="row" %) 6 6 ((( 7 -Crestron Zūm Wired is a system thathas variousglobal andlocal control options. Zūm Wireduses industry standard dimming protocols(DALI, 0-10V, and phase dimming) and advanced sensorsto provide automated control of a buildingor 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 various important concepts that must be understood in order to design a system that meets the requirements of all project stakeholders. 9 +(% class="box warningmessage" %) 10 +((( 11 +Add more to intro 12 +))) 10 10 11 -= System Overviewand Hardware Modes =14 += Control Paradigms = 12 12 13 -Zūm Wired systems c onsist of ZUMNET-JBOX-* room controllersanda numberof connectedZUMLINK-* devices. ZUMLINK-* devices canbeZUMLINK-JBOX-* loadcontrollers,ZUMLINK-OCC-* presence detectors,or ZUMLINK-KP-R-W keypads(wall switches). ZUMNET-JBOX-*andZUMLINK-JBOX-* devices have additionalinputs forthird-party presencedetectors,0-10Vanalogphotocells, andcontact-closure local override.16 +Zūm Wired systems can be designed as either standalone or networked applications. 14 14 15 - ==App Mode==18 +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, 16 16 20 +== Standalone == 21 + 17 17 Lorem 18 18 19 -== CNET Mode ==24 +== Networked == 20 20 21 21 Lorem 22 22 23 -== Primaryvs SecondaryMode==28 +=== Networked with Default Program === 24 24 25 - ZUMNET-JBOX-* devices can be set tobe eithertheprimary room controller or a secondary load controller.30 +Lorem 26 26 27 -N otehat on older versions of firmware, these modes werereferredto as "master" and "slave" mode. The terminologywas updatedin .puf v1.03.27 (device firmware v1.002.00026), butas of February, 2023 theFW32 +=== Networked with SHOWRUNNER™ === 28 28 29 -== Security == 30 - 31 31 Lorem 32 32 33 -= Control Paradigms =36 += Standalone vs Networked Systems = 34 34 35 - Designsfor Zūm Wired systemsare 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.38 +== Start-Up Considerations == 36 36 37 - 38 -The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-* 39 - 40 -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, 41 - 42 -Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program". 43 - 44 -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. 45 - 46 -== Standalone == 47 - 48 48 Lorem 49 49 50 -== Networked == 42 +== Processor Selection for Networked Systems == 51 51 52 52 Lorem 53 53 54 -= ==Networkedith Default Program===46 += Hardware Modes = 55 55 56 56 Lorem 57 57 58 -== =Networkedwith SHOWRUNNER™===50 +== CNET Mode == 59 59 60 60 Lorem 61 61 62 -== Start-UpConsiderations==54 +== App Mode == 63 63 64 64 Lorem 65 65 66 -== Pr ocessor Selectionfor NetworkedSystems==58 +== Primary vs Secondary == 67 67 68 68 Lorem 69 69
- 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