Wiki source code of *Design Considerations
Version 10.3 by Alexander Mott on 2023/03/24 18:27
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 platform that utilizes advanced sensors and industry standard dimming protocols to provide automated control of a building's lighting. | ||
| 8 | |||
| 9 | |||
| 10 | |||
| 11 | |||
| 12 | |||
| 13 | |||
| 14 | |||
| 15 | |||
| 16 | |||
| 17 | (% class="box warningmessage" %) | ||
| 18 | ((( | ||
| 19 | Add more to intro | ||
| 20 | ))) | ||
| 21 | |||
| 22 | = Hardware Modes = | ||
| 23 | |||
| 24 | Lorem | ||
| 25 | |||
| 26 | == CNET Mode == | ||
| 27 | |||
| 28 | Lorem | ||
| 29 | |||
| 30 | == App Mode == | ||
| 31 | |||
| 32 | Lorem | ||
| 33 | |||
| 34 | == Primary vs Secondary == | ||
| 35 | |||
| 36 | Lorem | ||
| 37 | |||
| 38 | = Control Paradigms = | ||
| 39 | |||
| 40 | Designs for Zūm Wired systems can be broadly described as being either "standalone" or "networked". Both standalone and networked applications will be designed to have at least one ZUNET-JBOX-* per room with a number of connected ZUMLINK-* devices. In networked systems, there is also a control processor which provides centralized control of the entire system. This processo | ||
| 41 | |||
| 42 | |||
| 43 | The difference between the two is that in a networked system there will be Zūm Net cabling connecting each ZUMNET-JBOX-* | ||
| 44 | |||
| 45 | 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, | ||
| 46 | |||
| 47 | Networked systems can be further subdivided into "Networked with Default Program" or "Networked with Custom Program". | ||
| 48 | |||
| 49 | 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. | ||
| 50 | |||
| 51 | == Standalone == | ||
| 52 | |||
| 53 | Lorem | ||
| 54 | |||
| 55 | == Networked == | ||
| 56 | |||
| 57 | Lorem | ||
| 58 | |||
| 59 | === Networked with Default Program === | ||
| 60 | |||
| 61 | Lorem | ||
| 62 | |||
| 63 | === Networked with SHOWRUNNER™ === | ||
| 64 | |||
| 65 | Lorem | ||
| 66 | |||
| 67 | == Start-Up Considerations == | ||
| 68 | |||
| 69 | Lorem | ||
| 70 | |||
| 71 | == Processor Selection for Networked Systems == | ||
| 72 | |||
| 73 | Lorem | ||
| 74 | |||
| 75 | = Device Count Limitations = | ||
| 76 | |||
| 77 | Lorem | ||
| 78 | ))) |