Changes for page **General Overview and Design Considerations
Last modified by Alexander Mott on 2023/12/08 18:37
From version 14.20
edited by Alexander Mott
on 2023/03/27 20:11
on 2023/03/27 20:11
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -88,13 +88,12 @@ 88 88 89 89 == Standalone == 90 90 91 - Standalone Zūm Wired designsconsist of completelyindependent Zūm Rooms. Each Zūm Room hasa singleZUMNET-JBOX-*withanynumber of ZUMLINK-* devicesconnected to it. There isnoZūmNetconnecting individual rooms, and there is noprocessorrequired. This results inasystem which has a reduced hardware cost and cantheoreticallybecommissioned and configured entirely by the electrical contractor, however there aresomeimportantdrawbacks to consider.91 +Completely standalone Zūm Wired designs are possible, but they have some important benefits and drawbacks to consider. 92 92 93 - Theprimarybenefits of a standalone Zūm Wired system are:93 +Some benefits of a standalone Zūm Wired system are: 94 94 95 95 * Reduced installation time and cost as no Zūm Net cabling is required between rooms 96 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 98 99 99 Some drawbacks of a standalone Zūm Wired system are: 100 100 ... ... @@ -102,42 +102,20 @@ 102 102 ** ZUMNET-JBOX-* devices must be manually set to Zūm App mode 103 103 ** ZUMNET-JBOX-* devices must be manually set to Primary mode 104 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 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 106 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 106 +* No scheduling capabilities 116 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) 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 117 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 118 * Potential security concerns if the default PINs are not changed during start-up 119 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.116 +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 143 Some benefits of using the default program are: ... ... @@ -146,7 +146,7 @@ 146 146 147 147 Some drawbacks of using the default program are: 148 148 149 -* Requires a ZUM-HUB4 processor (other types of processors can only be used with a custom program)126 +* Requires a ZUM-HUB4 processor 150 150 * Limited support for Cresnet devices on the Zūm Link bus (n**o support?**) 151 151 * Limited scheduling capabilities 152 152