Wiki source code of *Design Considerations
Version 10.7 by Alexander Mott on 2023/03/24 18:47
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{box cssClass="floatinginfobox" title="**CONTENTS**"}} | ||
| 2 | {{toc/}} | ||
| 3 | {{/box}} | ||
| 4 | |||
| 5 | (% class="row" %) | ||
| 6 | ((( | ||
| 7 | Crestron Zūm Wired is a distributed lighting control system that has various global and local control options. Zūm Wired uses industry standard dimming protocols (DALI, 0-10V, and phase dimming) and advanced sensors to provide automated control of a building or facility's lighting. With certain designs, it is also possible to integrate control over DMX fixtures, building management systems, and other third-party devices (such as motorized shades and HVAC). | ||
| 8 | |||
| 9 | The purpose of this article is to explain various important concepts that must be understood in order to design a system that meets the requirements of all project stakeholders. | ||
| 10 | |||
| 11 | = System Overview and Hardware Modes = | ||
| 12 | |||
| 13 | Zūm Wired systems consist of ZUMNET-JBOX-* room controllers and a number of connected ZUMLINK-* devices. ZUMLINK-* devices can be ZUMLINK-JBOX-* load controllers, ZUMLINK-OCC-* presence detectors, or ZUMLINK-KP-R-W keypads (wall switches). ZUMNET-JBOX-* and ZUMLINK-JBOX-* devices have additional inputs for third-party/non-system presence detectors, 0-10V photocells | ||
| 14 | |||
| 15 | == CNET Mode == | ||
| 16 | |||
| 17 | Lorem | ||
| 18 | |||
| 19 | == App Mode == | ||
| 20 | |||
| 21 | Lorem | ||
| 22 | |||
| 23 | == Primary vs Secondary == | ||
| 24 | |||
| 25 | Lorem | ||
| 26 | |||
| 27 | == Security == | ||
| 28 | |||
| 29 | Lorem | ||
| 30 | |||
| 31 | = Control Paradigms = | ||
| 32 | |||
| 33 | Designs for Zūm Wired systems are broadly categorized as either "standalone" or "networked" designs. Both standalone and networked systems should be designed with one ZUMNET-JBOX-* per room or logical control space connected to a number of ZUMLINK-* devices within that same space. In networked systems, there is also a control processor which provides centralized control of the entire system. ZUMNET-JBOX-* must be daisy-chained together with Zūm Net and then connected back to the processor. In standalone applications, there is no processor and no Zūm Net cabling connecting different rooms to each other. | ||
| 34 | |||
| 35 | |||
| 36 | The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-* | ||
| 37 | |||
| 38 | In standalone applications, each room has one ZUMNET-JBOX-* with a number of connected ZUMLINK-* devices. There is no Zūm Net connecting different rooms, | ||
| 39 | |||
| 40 | Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program". | ||
| 41 | |||
| 42 | Depending on which control paradigm is selected, there will be various impacts to the hardware cost, start-up cost, start-up complexity, ease of maintenance, control capabilities, integration with third-party systems, available user interfaces, and the ability to meet a provided sequence of operations. | ||
| 43 | |||
| 44 | == Standalone == | ||
| 45 | |||
| 46 | Lorem | ||
| 47 | |||
| 48 | == Networked == | ||
| 49 | |||
| 50 | Lorem | ||
| 51 | |||
| 52 | === Networked with Default Program === | ||
| 53 | |||
| 54 | Lorem | ||
| 55 | |||
| 56 | === Networked with SHOWRUNNER™ === | ||
| 57 | |||
| 58 | Lorem | ||
| 59 | |||
| 60 | == Start-Up Considerations == | ||
| 61 | |||
| 62 | Lorem | ||
| 63 | |||
| 64 | == Processor Selection for Networked Systems == | ||
| 65 | |||
| 66 | Lorem | ||
| 67 | |||
| 68 | = Device Count Limitations = | ||
| 69 | |||
| 70 | Lorem | ||
| 71 | ))) |