Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 14.23
edited by Alexander Mott
on 2023/03/27 20:23
Change comment: (Autosaved)
To version 16.1
edited by Alexander Mott
on 2023/03/28 14:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,20 +16,15 @@
16 16  
17 17  == App Mode ==
18 18  
19 -(% class="box warningmessage" %)
20 -(((
21 -add more here
22 -)))
19 +Using ZUMNET-JBOX-* devices in App Mode means that the majority of the room logic is handled by the [[Primary>>WebHome||anchor="HPrimaryvsSecondaryMode"]] ZUMNET-JBOX-* for the room. This room logic must be configured over Bluetooth using the Crestron Zūm App. In [[Standalone>>WebHome||anchor="HStandalone"]] systems, the Primary ZUMNET-JBOX for each room is the only device handling control logic, whereas [[Networked>>WebHome||anchor="HNetworked"]] systems also have a centralized control processor which handles additional functions such as scheduling and coordinating controls between rooms and third party systems.
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.
25 -
26 26  == CNET Mode ==
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.
23 +Using ZUMNET-JBOX-* devices in CNET Mode is only possible on a [[networked system with a custom program>>WebHome||anchor="HNetworkedwithCustomProgram"]]. While in CNET Mode, ZUMNET-JBOX-* devices suspend any local logic and act as a "dumb" Cresnet-to-Ethernet bridge with a built-in load controller. Instead of receiving communications from Zūm Link devices and deciding what each device should do, the ZUMNET-JBOX simply passes the information on to the control processor to do all the thinking. While in CNET Mode, ZUMNET-JBOX-* devices cannot be connected to through the Zūm App, and any attached ZUMLINK-KP or ZUMLINK-OCC-* sensors will not work without the processor.
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.
25 +The benefit of using CNET Mode with a custom program over App Mode is that it allows for the control processor to have direct control over all hardware in the system. This enables a custom program to meet a significantly wider range of sequences than App Mode. Additionally, CNET Mode offers increased security over App Mode as it is not possible to connect to a device with the Crestron Zūm App while it is in CNET Mode.
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.
27 +The main drawbacks of using CNET Mode are the added hardware and installation costs that come with requiring a networked system and custom program. Systems running on outdated firmware have the additional drawback of losing all local controls in the event that connection to the control processor is lost, but this risk has been addressed with the introduction of the [[Zūm Mode Auto Switch>>WebHome||anchor="HZ16BmModeAutoSwitch"]] feature.
33 33  
34 34  //As of February, 2023, Crestron is shipping all ZUMNET-JBOX-* devices preconfigured in CNET mode, though this may change in the future.//
35 35  
... ... @@ -37,10 +37,12 @@
37 37  
38 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.
39 39  
40 -Enabling this feature eliminates the biggest drawback of designing a system to use ZUMNET-JBOX-* devices in CNET Mode.
35 +Enabling this feature eliminates one of the biggest risks of designing a system to use ZUMNET-JBOX-* devices in CNET Mode by enabling the system to use local logic as a backup in the event of a loss of connection to the control processor.
41 41  
42 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.//
43 43  
39 +//Any configuration changes made through the Zūm App should be made while the control processor is disconnected: the easiest ways to accomplish this are to either disconnect the Cat5e/Cat6 cable at the processor or use Text Console commands to temporarily suspend the custom program on the processor.//
40 +
44 44  == Security Considerations ==
45 45  
46 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.
... ... @@ -63,29 +63,10 @@
63 63  
64 64  = Control Paradigms =
65 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.
63 +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 standalone systems, there is no central control processor and no Zūm Net cabling connecting rooms to each other, which reduces the cost and complexity of the installation but also comes with some of its own limitations. Networked systems, by contrast, do have a control processor which provides centralized control of the entire system. Zūm Net cabling is used to daisy-chain ZUMNET-JBOX-* devices together and then connect them to the lighting network for control by the processor.
67 67  
65 +Networked systems can be further subdivided into those that use the default program included with ZUM-HUB4 processors and those that use a custom program, such as SHOWRUNNER™. The below sections cover in detail the advantages and disadvantages of each control paradigm.
68 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 89  == Standalone ==
90 90  
91 91  Standalone Zūm Wired designs consist of completely independent Zūm Rooms. Each Zūm Room has a single ZUMNET-JBOX-* with any number of ZUMLINK-* devices connected to it. There is no Zūm Net connecting individual rooms, and there is no processor required. This results in a system which has a reduced hardware cost and can theoretically be commissioned and configured entirely by the electrical contractor, however there are some important drawbacks to consider.
... ... @@ -116,6 +116,7 @@
116 116  * No cross-room control capabilities (i.e., ZUMLINK-* keypads and occupancy sensors are restricted to controlling loads that are attached to the same ZUMNET-JBOX as they are)
117 117  * No possibility for remote support or management, as the only way to connect to any of the devices is by being using the Zūm App, which requires being within Bluetooth range of the device
118 118  * Potential security concerns if the default PINs are not changed during start-up
97 +* Not possible to provide a graphical UI (touch screen)
119 119  
120 120  == Networked ==
121 121  
... ... @@ -137,6 +137,10 @@
137 137  * Able to meet a wider range of sequences compared to standalone systems
138 138  ** Scheduling capabilities
139 139  ** BMS/BACnet integration
119 +** (% class="box warningmessage" %)
120 +(((
121 +add more
122 +)))
140 140  
141 141  === Networked with Default Program ===
142 142  
... ... @@ -149,6 +149,7 @@
149 149  * Requires a ZUM-HUB4 processor (other types of processors can only be used with a custom program)
150 150  * Limited support for Cresnet devices on the Zūm Link bus (n**o support?**)
151 151  * Limited scheduling capabilities
135 +* N**o end-user UI availa**ble
152 152  
153 153  === Networked with Custom Program ===
154 154