Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 14.1
edited by Alexander Mott
on 2023/03/24 20:59
Change comment: There is no comment for this version
To version 5.2
edited by Alexander Mott
on 2023/03/24 18:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -*General Overview and Design Considerations
1 +*Design Considerations
Content
... ... @@ -4,109 +4,58 @@
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 -
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 -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 -
17 -== App Mode ==
18 -
19 19  (% class="box warningmessage" %)
20 20  (((
21 -add more here
11 +Add more to intro
22 22  )))
23 23  
24 -If devices in App Mode are being used as part of a networked system running a custom program, then any configuration changes made through the Zūm App should be made while the device is disconnected from the processor. The easiest ways to accomplish this are to either disconnect the Cat5e/Cat6 cable at the processor, or stop the program running on the processor using Text Console commands.
14 += Control Paradigms =
25 25  
26 -== CNET Mode ==
16 +Zūm Wired systems can be designed as either standalone or networked applications.
27 27  
28 -Using ZUMNET-JBOX-* devices in CNET Mode is only possible on a networked system with a processor that is running a custom program. While in CNET Mode, ZUMNET-JBOX-* devices do not process any local logic and cannot be connected to through the Zūm App in order to be configured. This is because while in CNET Mode, ZUMNET-JBOX act as a "dumb" Cresnet-to-Ethernet bridge with a built-in load controller. They report all Zūm Link traffic back to the control processor and do not do any "thinking" on their own. Any attached ZUMLINK-KP or ZUMLINK-OCC-* devices will not work without the processor if the ZUMNET-JBOX is in CNET 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,
29 29  
30 -CNET Mode has some benefits over App Mode. Compared to App Mode, CNET Mode offers direct control of all hardware which enables the system to meet a wider range of sequences. Additionally, CNET Mode offers increased security as it is not possible to connect to a device with the Zūm App while it is in CNET Mode.
20 +== Standalone ==
31 31  
32 -The two main drawbacks of using CNET Mode are the requirement for a networked system with a custom program and the loss of local control in the event that connection to the control processor is lost, however the introduction of the Zūm Mode Auto Switch feature in .puf firmware v1.04.05 (device firmware v1.004.00005) has eliminated this second drawback by enabling devices to automatically switch between CNET and Zūm Modes when connection to the processor is lost or regained.
22 +Lorem
33 33  
34 -//As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured in CNET mode, though this may change in the future.//
24 +== Networked ==
35 35  
36 -== Zūm Mode Auto Switch ==
26 +Lorem
37 37  
38 -Zūm Mode Auto Switch is a feature introduced in November of 2022 with .puf firmware v1.04.05 (device firmware 1.004.00005). This feature is intended to address concerns that arose from projects using custom programs with ZUMNET-JBOX-* devices in CNET Mode. Previously, if a device in CNET Mode lost connection to the processor, then it would be impossible to maintain any sort of control over the lighting. With Zūm Mode Auto Switch enabled, a ZUMNET-JBOX running in CNET Mode will automatically switch to App Mode and process local logic in the event that it loses connection to the processor.
28 +=== Networked with Default Program ===
39 39  
40 -Enabling this feature eliminates the biggest drawback of designing a system to use ZUMNET-JBOX-* devices in CNET Mode.
30 +Lorem
41 41  
42 -//As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured with Zūm Mode Auto Switch disabled, as this feature is only intended to be used with systems that are running custom programs.//
32 +=== Networked with SHOWRUNNER™ ===
43 43  
44 -== Security Considerations ==
34 +Lorem
45 45  
46 -Any ZUMNET-JBOX that is running in App Mode with an attached ZUMLINK-KP can be connected to via the Crestron Zūm App, which is publicly available in the Google Play store. Although unlikely, it is technically possible that a bad actor could download the Zūm App and interfere with the lighting controls. Crestron ships all ZUMNET-JBOX-* devices with a default PIN that is intended to be changed during commissioning, however there is no guarantee that the technician who configured the Zūm Wired hardware knew or remembered to do this.
36 += Standalone vs Networked Systems =
47 47  
48 -One way to counteract this security risk is to design the system to operate with the ZUMNET-JBOX-* devices in CNET Mode. In CNET Mode, it is impossible to connect to any devices using the Zūm App. Leaving the Zūm Mode Auto Switch function disabled will add another layer of security in exchange for a loss of localized control when the system is experiencing issues, as devices will stay in CNET Mode even when connection to the control processor is lost.
38 +== Start-Up Considerations ==
49 49  
50 -== Primary vs Secondary Mode ==
51 -
52 -(% class="box infomessage" %)
53 -(((
54 -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.
55 -)))
56 -
57 -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.
58 -
59 -* 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.
60 -* 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.
61 -
62 -//As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured in Secondary mode, however they have announced their intention to begin shipping hardware on newer firmware preconfigured in Primary mode.//
63 -
64 -= Control Paradigms =
65 -
66 -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.
67 -
68 -
69 -(% class="box warningmessage" %)
70 -(((
71 -The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-*
72 -)))
73 -
74 -(% class="box warningmessage" %)
75 -(((
76 -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,
77 -)))
78 -
79 -(% class="box warningmessage" %)
80 -(((
81 -Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program".
82 -)))
83 -
84 -(% class="box warningmessage" %)
85 -(((
86 -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.
87 -)))
88 -
89 -== Standalone ==
90 -
91 91  Lorem
92 92  
93 -== Networked ==
42 +== Processor Selection for Networked Systems ==
94 94  
95 95  Lorem
96 96  
97 -=== Networked with Default Program ===
46 += Hardware Modes =
98 98  
99 99  Lorem
100 100  
101 -=== Networked with Custom Program ===
50 +== CNET Mode ==
102 102  
103 103  Lorem
104 104  
105 -== Start-Up Considerations ==
54 +== App Mode ==
106 106  
107 107  Lorem
108 108  
109 -== Processor Selection for Networked Systems ==
58 +== Primary vs Secondary ==
110 110  
111 111  Lorem
112 112  
1679688568997-208.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -6.9 KB
Content
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