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

Summary

Details

Page properties
Content
... ... @@ -98,6 +98,11 @@
98 98  
99 99  == Networked ==
100 100  
101 +(% class="box errormessage" %)
102 +(((
103 +section incomplete
104 +)))
105 +
101 101  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.
102 102  
103 103  In general, the drawbacks of any networked system are:
... ... @@ -116,13 +116,14 @@
116 116  * Able to meet a wider range of sequences compared to standalone systems
117 117  ** Scheduling capabilities
118 118  ** BMS/BACnet integration
119 -** (% class="box warningmessage" %)
120 -(((
121 -add more
122 -)))
123 123  
124 124  === Networked with Default Program ===
125 125  
127 +(% class="box errormessage" %)
128 +(((
129 +section incomplete
130 +)))
131 +
126 126  Some benefits of using the default program are:
127 127  
128 128  *
... ... @@ -136,23 +136,26 @@
136 136  
137 137  === Networked with Custom Program ===
138 138  
139 -Some benefits of using a custom program such as SHOWRUNNER™ are:
145 +(% class="box errormessage" %)
146 +(((
147 +section incomplete
148 +)))
140 140  
141 -*
150 +Some of the general benefits of using a custom program are:
142 142  
143 -Some drawbacks of using a custom program such as SHOWRUNNER™ are:
144 -
145 145  *
146 146  
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 +
147 147  = Hardware Design Limitations =
148 148  
149 -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.
150 150  
151 151  Zūm Net limitations:
152 152  
153 153  * Do not exceed 100m or 328' between subsequent ZUMNET-JBOX-* devices, or between the first ZUMNET-JBOX and the network switch
154 154  * Do not exceed 20 ZUMNET-JBOX-* devices on a single run of Zūm Net
155 -* 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.
156 156  
157 157  Zūm Link limitations:
158 158  
... ... @@ -164,4 +164,6 @@
164 164  ** Other ZUMLINK-OCC-* sensors are rated at 25mA of power consumption each
165 165  ** ZUMLINK-KP keypads do not have a listed power consumption, but designing for approximately 20mA is safe
166 166  * 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
167 167  )))