Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 13.1
edited by Alexander Mott
on 2023/03/24 20:09
Change comment: Uploaded new attachment "1679688568997-208.png", version {1}
To version 10.2
edited by Alexander Mott
on 2023/03/24 18:22
Change comment: (Autosaved)

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -*General Overview and Design Considerations
1 +*Design Considerations
Content
... ... @@ -4,55 +4,46 @@
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 various important concepts that must be understood in order to design a system that meets the requirements of all project stakeholders.
10 10  
11 -= System Overview and Hardware Modes =
12 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 14  
15 -ZUMNET-JBOX-* room controllers can be operated in App mode or CNET mode, with an additional setting to be either the Primary room controller or a Secondary load controller.
16 16  
17 -== App Mode ==
18 18  
19 -Lorem
20 20  
21 -== CNET Mode ==
22 22  
23 -Lorem
24 24  
25 -== Primary vs Secondary Mode ==
26 -
27 -(% class="box infomessage" %)
17 +(% class="box warningmessage" %)
28 28  (((
29 -Note: the terminology used for these modes was modified in .puf firmware v1.03.27 (device firmware v1.002.00026). Hardware delivered with older firmware will require the use of different commands to change modes during start-up.
19 +Add more to intro
30 30  )))
31 31  
32 -ZUMNET-JBOX-* devices can be set to be either the Primary room controller or a Secondary load controller. There must only be one Primary ZUMNET-JBOX on a given Zūm Link bus, and in a networked system the Primary ZUMNET-JBOX is the one that should be connected to the Zūm Net.
22 += Hardware Modes =
33 33  
34 -* In Primary mode, the ZUMNET-JBOX acts as the Zūm Link host, and is able to detect all connected Zūm Link devices. If connected to in Crestron Toolbox, a Primary ZUMNET-JBOX can be used to view and manually address any connected ZUMLINK-* devices. While in App mode, a ZUMNET-JBOX in Primary mode is the logical room controller for the space and is the device that should be used for configuration via the Zūm App.
35 -* In Secondary mode, the ZUMNET-JBOX acts as if it were a ZUMLINK-JBOX. It does not process any room control logic, and when connected to via Crestron Toolbox it will not be able to see any other ZUMLINK-* devices. Using Secondary mode is rare, and should only be used in cases where a spare ZUMNET-JBOX is being used to add a load to another ZUMNET-JBOX or replace a ZUMLINK-JBOX that has been lost or damaged.
24 +Lorem
36 36  
37 -As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* preconfigured in Secondary mode, though this may change in the future.
26 +== CNET Mode ==
38 38  
39 -== Security Considerations ==
28 +Lorem
40 40  
41 -Although unlikely, it is technically possible that
30 +== App Mode ==
42 42  
43 -= Control Paradigms =
32 +Lorem
44 44  
45 -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 +== Primary vs Secondary ==
46 46  
36 +Lorem
47 47  
48 -The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
38 += Control Paradigms =
49 49  
50 -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 +Designs for Zūm Wired systems can be broadly described as being either "standalone" or "networked". Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
51 51  
52 -Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
42 +Depending on which control paradigm is selected, there are varied impacts to cost of hardware, cost and complexity of start-up, ease of maintenance, and control capabilities.
53 53  
54 -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.
55 55  
45 +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,
46 +
56 56  == Standalone ==
57 57  
58 58  Lorem
1679688568997-208.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.9 KB
Content