Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 20.1
edited by Alexander Mott
on 2023/12/08 18:37
Change comment: There is no comment for this version
To version 17.1
edited by Alexander Mott
on 2023/03/28 16:04
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
... ... @@ -98,11 +98,6 @@
98 98  
99 99  == Networked ==
100 100  
101 -(% class="box errormessage" %)
102 -(((
103 -section incomplete
104 -)))
105 -
106 106  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.
107 107  
108 108  In general, the drawbacks of any networked system are:
... ... @@ -121,14 +121,13 @@
121 121  * Able to meet a wider range of sequences compared to standalone systems
122 122  ** Scheduling capabilities
123 123  ** BMS/BACnet integration
124 -
125 -=== Networked with Default Program ===
126 -
127 -(% class="box errormessage" %)
119 +** (% class="box warningmessage" %)
128 128  (((
129 -section incomplete
121 +add more
130 130  )))
131 131  
124 +=== Networked with Default Program ===
125 +
132 132  Some benefits of using the default program are:
133 133  
134 134  *
... ... @@ -142,11 +142,6 @@
142 142  
143 143  === Networked with Custom Program ===
144 144  
145 -(% class="box errormessage" %)
146 -(((
147 -section incomplete
148 -)))
149 -
150 150  Some of the general benefits of using a custom program are:
151 151  
152 152  *
... ... @@ -155,13 +155,13 @@
155 155  
156 156  = Hardware Design Limitations =
157 157  
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.
147 +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:
159 159  
160 160  Zūm Net limitations:
161 161  
162 162  * Do not exceed 100m or 328' between subsequent ZUMNET-JBOX-* devices, or between the first ZUMNET-JBOX and the network switch
163 163  * Do not exceed 20 ZUMNET-JBOX-* devices on a single run of Zūm Net
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.
153 +* 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)
165 165  
166 166  Zūm Link limitations:
167 167  
... ... @@ -173,6 +173,4 @@
173 173  ** Other ZUMLINK-OCC-* sensors are rated at 25mA of power consumption each
174 174  ** ZUMLINK-KP keypads do not have a listed power consumption, but designing for approximately 20mA is safe
175 175  * 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
178 178  )))