Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 15.1
edited by Alexander Mott
on 2023/03/27 20:26
Change comment: There is no comment for this version
To version 20.1
edited by Alexander Mott
on 2023/12/08 18:37
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 +**General Overview and Design Considerations
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.
... ... @@ -101,6 +101,11 @@
101 101  
102 102  == Networked ==
103 103  
101 +(% class="box errormessage" %)
102 +(((
103 +section incomplete
104 +)))
105 +
104 104  Networked systems are generally preferred over standalone systems for most applications. Networked systems, and in particular networked systems with custom programming, are able to meet a much wider variety of sequences compared to standalone systems. Additionally, start-up and maintenance can be simplified, and certain aspects completed remotely, compared to standalone systems.
105 105  
106 106  In general, the drawbacks of any networked system are:
... ... @@ -119,13 +119,14 @@
119 119  * Able to meet a wider range of sequences compared to standalone systems
120 120  ** Scheduling capabilities
121 121  ** BMS/BACnet integration
122 -** (% class="box warningmessage" %)
123 -(((
124 -add more
125 -)))
126 126  
127 127  === Networked with Default Program ===
128 128  
127 +(% class="box errormessage" %)
128 +(((
129 +section incomplete
130 +)))
131 +
129 129  Some benefits of using the default program are:
130 130  
131 131  *
... ... @@ -139,23 +139,26 @@
139 139  
140 140  === Networked with Custom Program ===
141 141  
142 -Some benefits of using a custom program such as SHOWRUNNER™ are:
145 +(% class="box errormessage" %)
146 +(((
147 +section incomplete
148 +)))
143 143  
144 -*
150 +Some of the general benefits of using a custom program are:
145 145  
146 -Some drawbacks of using a custom program such as SHOWRUNNER™ are:
147 -
148 148  *
149 149  
154 +The primary downside to using a custom program is that it is necessary to actually write a custom program for the system. With the SHOWRUNNER™ platform however, this downside is averted as it comes with a suite of tools to simplify configuration and commissioning easier compared to other custom programs. For more information, see our [[Crestron Zūm Wired and SHOWRUNNER™>>doc:Design Guide.Hardware Design Guide.Crestron Zum Wired.Crestron Zum Wired Overview.WebHome||anchor="HTheSHOWRUNNER2122Advantage"]] page.
155 +
150 150  = Hardware Design Limitations =
151 151  
152 -There are a handful of limitations to keep in mind when designing Zūm Wired systems, with different restrictions applying to Zūm Net and Zūm Link:
158 +There are a handful of limitations to keep in mind when designing Zūm Wired systems, with different restrictions applying to Zūm Net and Zūm Link.
153 153  
154 154  Zūm Net limitations:
155 155  
156 156  * Do not exceed 100m or 328' between subsequent ZUMNET-JBOX-* devices, or between the first ZUMNET-JBOX and the network switch
157 157  * Do not exceed 20 ZUMNET-JBOX-* devices on a single run of Zūm Net
158 -* Do not "loop" Zūm Net cables (i.e., cables should start at the network switch and end at the last ZUMNET-JBOX, without a returning cable from the last device back to the switch)
164 +* Do not "loop" Zūm Net cables. ZUMNET-JBOX-* devices should be daisy chained together, with the first device on the run connected to the network switch and no home-run connecting the end-of-line device back to the network switch.
159 159  
160 160  Zūm Link limitations:
161 161  
... ... @@ -167,4 +167,6 @@
167 167  ** Other ZUMLINK-OCC-* sensors are rated at 25mA of power consumption each
168 168  ** ZUMLINK-KP keypads do not have a listed power consumption, but designing for approximately 20mA is safe
169 169  * Available power on the Zūm Link bus can be increased by adding additional ZUMLILNK-JBOX-* devices, or by adding a separate power pack to provide power for non-system sensors or Cresnet devices on the Zūm Link bus
176 +* Do not "loop" Zūm Link cables. ZUMLINK-* devices should be daisy chained together, with no home-run connecting the end-of-line device back to the ZUMNET-JBOX-* controller for the room
177 +* Do not connect the Zūm Link busses of two separate ZUMNET-JBOX-* devices. There can only be one Primary ZUMNET-JBOX per Zūm Link bus, and any ZUMNET-JBOX-* devices intended to be operated as Secondary devices should instead be replaced with the corresponding ZUMLINK-JBOX-* model
170 170  )))