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

Summary

Details

Page properties
Content
... ... @@ -88,29 +88,8 @@
88 88  
89 89  == Standalone ==
90 90  
91 -Completely standalone Zūm Wired designs are possible, but they have some important benefits and drawbacks to consider.
91 +Lorem
92 92  
93 -Some benefits of a standalone Zūm Wired system are:
94 -
95 -* Reduced installation time and cost as no Zūm Net cabling is required between rooms
96 -* Reduced hardware cost as no ZUM-HUB4 or networking hardware is required
97 -
98 -Some drawbacks of a standalone Zūm Wired system are:
99 -
100 -* As of 2/2023, ZUMNET-JBOX-* devices ship with factory settings that are incompatible with an App only startup, resulting in extra expense to configure and update devices prior to installation or extra time spent during startup to accomplish these tasks post-installation:
101 -** ZUMNET-JBOX-* devices must be manually set to Zūm App mode
102 -** ZUMNET-JBOX-* devices must be manually set to Primary mode
103 -** Updating firmware with the Crestron Zūm App is not possible with out-of-the-box firmware and must be initially done through Toolbox
104 -* ZUMNET-JBOX-* devices can only be connected to and configured via the App if there is a ZUMLINK-KP on their Zūm Link bus
105 -** During start-up, a technician must bring a ZUMLINK-KP to connect to the ZUMNET-JBOX in order to configure any rooms that were designed without a ZUMLINK-KP
106 -* No scheduling capabilities
107 -* 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)
108 -* No support for Cresnet devices
109 -* No support for third-party integrations beyond the override contact-closure relay at each ZUMNET/ZUMLINK-JBOX and the relay output of any *-RLY model occupancy sensors
110 -* No support for DMX control
111 -* 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
112 -* Potential security concerns if the default PINs are not changed during start-up
113 -
114 114  == Networked ==
115 115  
116 116  Lorem
... ... @@ -117,44 +117,21 @@
117 117  
118 118  === Networked with Default Program ===
119 119  
120 -Some benefits of using the default program are:
99 +Lorem
121 121  
122 -*
123 -
124 -Some drawbacks of using the default program are:
125 -
126 -* Requires a ZUM-HUB4 processor
127 -* Limited support for Cresnet devices on the Zūm Link bus (n**o support?**)
128 -* Limited scheduling capabilities
129 -
130 130  === Networked with Custom Program ===
131 131  
132 -Some benefits of using a custom program such as SHOWRUNNER™ are:
103 +Lorem
133 133  
134 -*
105 +== Start-Up Considerations ==
135 135  
136 -Some drawbacks of using a custom program such as SHOWRUNNER™ are:
107 +Lorem
137 137  
138 -*
109 +== Processor Selection for Networked Systems ==
139 139  
140 -= Hardware Design Limitations =
111 +Lorem
141 141  
142 -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:
113 += Device Count Limitations =
143 143  
144 -Zūm Net limitations:
145 -
146 -* Do not exceed 100m or 328' between subsequent ZUMNET-JBOX-* devices, or between the first ZUMNET-JBOX and the network switch
147 -* Do not exceed 20 ZUMNET-JBOX-* devices on a single run of Zūm Net
148 -* 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)
149 -
150 -Zūm Link limitations:
151 -
152 -* Do not exceed 31 ZUMLINK-* and Cresnet devices on a single ZUMNET-JBOX-* device
153 -* Do not exceed 85mA of 24VDC power consumption per ZUMNET/ZUMLINK-JBOX-* device on the Zūm Link bus
154 -** Each ZUMNET/ZUMLINK-JBOX-* is limited to 85mA of 24VDC output shared across their Zūm Link ports and sensor inputs
155 -** Power is shared between ZUMNET/ZUMLINK-JBOX-* devices on a single Zūm Link bus, so adding more ZUMNET/ZUMLINK-JBOX-* devices to a network increases the available power
156 -** ZUMLINK-IR-QUATTRO-HD-DLS/RLY occupancy sensors are rated at 32mA of power consumption
157 -** Other ZUMLINK-OCC-* sensors are rated at 25mA of power consumption each
158 -** ZUMLINK-KP keypads do not have a listed power consumption, but designing for approximately 20mA is safe
159 -* 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
115 +Lorem
160 160  )))