Skip to Content
Last modified by Alexander Mott on 2023/12/08 18:37
From version 14.22
edited by Alexander Mott
on 2023/03/27 20:18
Change comment: (Autosaved)
To version 14.7
edited by Alexander Mott
on 2023/03/27 19:18
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -88,78 +88,28 @@
88 88  
89 89  == Standalone ==
90 90  
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.
91 +Lorem
92 92  
93 -The primary 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 -* Theoretically possible to start-up using only the Crestron Zūm App, with no programming or specialty software required
98 -
99 -Some drawbacks of a standalone Zūm Wired system are:
100 -
101 -* 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:
102 -** ZUMNET-JBOX-* devices must be manually set to Zūm App mode
103 -** ZUMNET-JBOX-* devices must be manually set to Primary mode
104 -** Updating firmware with the Crestron Zūm App is not possible with out-of-the-box firmware and must be initially done through Toolbox
105 -* ZUMNET-JBOX-* devices can only be connected to via the App if there is a ZUMLINK-KP on their Zūm Link bus
106 -** 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
107 -* Firmware updates through the Zūm App can consume a large amount of time on-site
108 -** Only one room can be updated at a time using the Zūm App, and it is not possible to do anything else while the room is updating
109 -** The time required to update a room's firmware varies depending on the number of ZUMLINK devices in the room
110 -* Standalone systems are limited compared to Networked systems in terms of what sequences can be met
111 -** No scheduling capabilities
112 -** 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
113 -** No support for DMX control
114 -** Any future modifications to the sequence requires reconfiguration through the Zūm App
115 -* No support for Cresnet devices
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 -* 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 -* Potential security concerns if the default PINs are not changed during start-up
119 -
120 120  == Networked ==
121 121  
122 -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.
95 +Lorem
123 123  
124 -In general, the drawbacks of any networked system are:
125 -
126 -* Requires additional hardware (at minimum a processor and a network switch for the Zūm Net)
127 -* Requires additional Zūm Net cabling between rooms
128 -* Additional start-up time required to configure the program
129 -
130 -All networked systems have the following benefits:
131 -
132 -* Some aspects of start-up can be accomplished remotely if there is remote access to the lighting network
133 -* Updating firmware and modifying hardware configurations can be accomplished over Zūm Net
134 -** Loadscripts can be written to simultaneous update firmware for up to 10 rooms
135 -*** These can be run remotely if there is remote access to the lighting network, or scheduled by the technician to execute after working hours in order to free up time on-site
136 -** Loadscripts can be written to bulk modify hardware settings (such as changing from Secondary to Primary modes) and configure IP settings (such as changing hostnames or updating IP tables)
137 -* Able to meet a wider range of sequences compared to standalone systems
138 -** Scheduling capabilities
139 -** BMS/BACnet integration
140 -
141 141  === Networked with Default Program ===
142 142  
143 -Some benefits of using the default program are:
99 +Lorem
144 144  
145 -*
146 -
147 -Some drawbacks of using the default program are:
148 -
149 -* Requires a ZUM-HUB4 processor (other types of processors can only be used with a custom program)
150 -* Limited support for Cresnet devices on the Zūm Link bus (n**o support?**)
151 -* Limited scheduling capabilities
152 -
153 153  === Networked with Custom Program ===
154 154  
155 -Some benefits of using a custom program such as SHOWRUNNER™ are:
103 +Lorem
156 156  
157 -*
105 +== Start-Up Considerations ==
158 158  
159 -Some drawbacks of using a custom program such as SHOWRUNNER™ are:
107 +Lorem
160 160  
161 -*
109 +== Processor Selection for Networked Systems ==
162 162  
111 +Lorem
112 +
163 163  = Hardware Design Limitations =
164 164  
165 165  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: