Wiki source code of Shades Integrations
Version 4.1 by Alexander Mott on 2024/06/14 21:38
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | (% class="row" %) |
| 2 | ((( | ||
| |
2.1 | 3 | (% class="box infomessage" %) |
| 4 | ((( | ||
| 5 | Note: page is under construction, check back later for updates | ||
| 6 | ))) | ||
| 7 | |||
| |
1.1 | 8 | (% class="col-xs-12 col-sm-8" %) |
| 9 | ((( | ||
| |
2.1 | 10 | Controlling shades from ShowRunnerCLC™ is a paid feature that can be purchased either with the initial [[ShowRunnerCLC™ order>>doc:showrunner™ Order Guide.showrunner™ Additional Features.Shades.WebHome]] or added after-the-fact as an additional charge. When shades control or integration is ordered for ShowRunnerCLC™, it is vital to ensure that the BOM includes any required hardware is also ordered. |
| |
1.1 | 11 | |
| |
2.1 | 12 | While we strive to always provide accurate and complete information, bear in mind that we cannot guarantee that any information provided here will be 100% accurate and up-to-date: always check manufacturer product specifications to verify features and compatibility prior to ordering hardware. |
| |
1.1 | 13 | |
| 14 | = Crestron Shade Controllers = | ||
| 15 | |||
| |
2.1 | 16 | Crestron shades are included in all ShowRunnerCLC™ orders, but hardware will not be fully defined in the configuration unless the required information is provided prior to configuration shipment. If the required information cannot be provided with the original order, it is recommended to order [[SR-SDC>>doc:showrunner™ Order Guide.showrunner™ Additional Features.Shades.SR-SDC.WebHome]] for additional after-order Crestron shades support. |
| |
1.1 | 17 | |
| |
2.1 | 18 | ShowRunnerCLC™ provides native support for most Crestron shade controllers as well as integration with shades controlled from third-party Crestron processors via Ethernet Inter-Systems Communication (EISC). If integration with a Crestron shades controller or system that is not detailed below is required, reach out to Chief Integrations directly to see about potentially adding support to ShowRunnerCLC™. |
| |
1.1 | 19 | |
| |
4.1 | 20 | == Supported Hardware == |
| |
1.1 | 21 | |
| |
4.1 | 22 | ShowRunnerCLC™ includes support for the following Crestron shade controllers: |
| |
1.1 | 23 | |
| |
4.1 | 24 | * C2N-SDC and C2N-SDC-DC |
| 25 | * CSC Series Controllers (discontinued) | ||
| 26 | * CSA-PWS10S-HUB-ENET (controlling QMT-series motors) | ||
| 27 | * DIN-2MC2 | ||
| 28 | * Ethernet Inter-System Communications (Crestron-to-Crestron) | ||
| |
1.1 | 29 | |
| |
4.1 | 30 | For any integrations over Ethernet, the lighting network must be configured such that the lighting control processor running ShowRunnerCLC™ can communicate with all required hardware. |
| |
1.1 | 31 | |
| |
4.1 | 32 | == Information Required == |
| 33 | |||
| 34 | In order to fully define shades in the ShowRunnerCLC™ configuration, the following information must be provided by the Agent. Incomplete information will result in incomplete hardware definitions in the shipped ShowRunnerCLC™ configuration. | ||
| 35 | |||
| 36 | Non-EISC shades: | ||
| 37 | |||
| 38 | * **(Required)** Quantity of shade controllers | ||
| 39 | * **(Required)** Quantity and location of each shade motor to be controlled | ||
| 40 | ** For all controllers, we must know which shade motor (i.e. window and room) is connected to each output | ||
| 41 | ** For systems with multiple CSA-PSW10S-HUB-ENET, we must know which HUB is the Cresnet primary | ||
| 42 | |||
| 43 | EISC shades: | ||
| 44 | |||
| 45 | * **(Required)** Type of EISC integration (TCP or UDP) | ||
| 46 | * **(Required)** IP Address and IP-ID of non-ShowRunnerCLC™ processor | ||
| 47 | * **(Required) **Joins to be used for shade control and feedback (see table below; not all features are required for all integrations) | ||
| 48 | |||
| 49 | (% style="width:632px" %) | ||
| 50 | |=Join|=(% style="width: 344px;" %)Description|=(% style="width: 6px;" %)Type|=(% style="width: 101px;" %)Direction | ||
| 51 | |JoinOpen|(% style="width:344px" %)Sends a digital pulse when open is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party | ||
| 52 | |JoinClose|(% style="width:344px" %)Sends a digital pulse when close is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party | ||
| 53 | |JoinStop|(% style="width:344px" %)Sends a digital pulse when stop is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party | ||
| 54 | |JoinPosition|(% style="width:344px" %)Sends an analog value when the position is changed (0-65535 = 0-100%)|(% style="width:6px" %)Analog|(% style="width:101px" %)To 3rd Party | ||
| 55 | |JoinPositionFeedback|(% style="width:344px" %)Receives an analog value for the current shade position (0-65535 = 0-100%)|(% style="width:6px" %)Analog|(% style="width:101px" %)From 3rd Party | ||
| 56 | |||
| |
1.1 | 57 | = Third-Party Shade Controllers = |
| 58 | |||
| |
2.1 | 59 | ShowRunnerCLC™ supports integrating with a wide range of common shade control manufacturers, but this integration is not included in basic ShowRunnerCLC™ orders and requires the [[SR-SDN>>doc:showrunner™ Order Guide.showrunner™ Additional Features.Shades.SR-SDN.WebHome]] additional feature. If integration with a shades manufacturer or system that is not detailed below is required, reach out to Chief Integrations directly to see about potentially adding support to ShowRunnerCLC™. |
| |
1.1 | 60 | |
| |
2.1 | 61 | == Common Integration Methods == |
| |
1.1 | 62 | |
| |
2.1 | 63 | While most third-party shade controllers have proprietary integration protocols specific to each manufacturer and model, there are common industry standards which dictate the wiring and hardware requirements to integrate third-party shades with ShowRunnerCLC™: |
| |
1.1 | 64 | |
| |
2.1 | 65 | * Contact closure (Relays) |
| 66 | ** No standard specified length limitation (individual shade manufacturers may specify cabling and distance limitations) | ||
| 67 | ** Relay control can be susceptible to voltage drop or EMF interference: it is highly recommended to locate the Crestron controlled relay as close as possible to the shades interface being controlled | ||
| 68 | * Serial RS-232 | ||
| 69 | ** 50' maximum distance per specification | ||
| 70 | ** Point-to-point communication mandates a one-to-one relationship of Crestron RS-232 interfaces to shade RS-232 interfaces (i.e. there must be one RS-232 port available on the Crestron system for every RS-232 shade interface; depending on the shades design, a single shades interface may control many shades so it may be possible that a system with many shades only requires one RS-232 connection to the Crestron system) | ||
| 71 | * Serial RS-485 | ||
| 72 | ** 4000' maximum distance per specification (individual shades manufacturers may specify lower cabling and distance limitations, and real-world conditions may reduce the actual maximum distance that can be achieved before system performance is noticeably impacted) | ||
| 73 | ** Multidrop communications allows for daisy-chain and star wiring topologies, up to 32 devices per Crestron RS-485 interface (shades manufacturers may specify lower device counts) | ||
| 74 | * TCP/IP communication (including HTTP/HTTPS, TelNet, etc.) | ||
| 75 | ** Standard [[Ethernet wiring limitations>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Ethernet Wiring Overview.WebHome]] apply | ||
| |
1.1 | 76 | |
| |
2.4 | 77 | Below is a non-exhaustive table showing which pieces of Crestron hardware have interfaces for each kind of integration: |
| |
1.1 | 78 | |
| |
2.2 | 79 | |=Hardware|=Relay Outputs|=RS-485 Serial Ports|=RS-232 Serial Ports |
| 80 | |C2N-IO|2|✖|1 | ||
| |
2.4 | 81 | |INET-IOEX-RYIO|2|✖|✖ |
| |
2.2 | 82 | |CP3N / CP4N|8|1*|3* |
| 83 | |DIN-IO8|8|✖|✖ | ||
| |
2.3 | 84 | |DIN-AP3 / DIN-AP4|4|2*|2* |
| 85 | |((( | ||
| 86 | GLPAC-DIMFLV4-PM / GLPAC-DIMFLV8-PM | ||
| |
2.4 | 87 | (PM models only) |
| |
2.3 | 88 | )))|4|✖|✖ |
| 89 | |RMC3 / RMC4|2|1*|1* | ||
| |
2.4 | 90 | |ZUM-HUB4|✖|✖|✖ |
| |
2.3 | 91 | |(% colspan="4" %)* Some serial ports are dual-purpose and can be //either// RS-485 //or// RS-232; other serial ports are //only// RS-232 |
| |
1.1 | 92 | |
| |
2.1 | 93 | == Contact Closure (Relays) == |
| |
1.1 | 94 | |
| |
2.1 | 95 | == Draper IntelliFlex I/O A\V Gateway == |
| |
1.1 | 96 | |
| |
2.1 | 97 | (% class="wikigeneratedid" %) |
| 98 | RS-232 or RS-485 integration supported | ||
| |
1.1 | 99 | |
| |
2.1 | 100 | == Lutron Sivoia QS == |
| |
1.1 | 101 | |
| |
2.1 | 102 | (% class="wikigeneratedid" id="HSivoiaQSRS-232" %) |
| 103 | RS-232 or TelNet integration supported | ||
| |
1.1 | 104 | |
| 105 | == Lutron Quantum == | ||
| 106 | |||
| |
2.1 | 107 | (% class="wikigeneratedid" id="HQuantumRS-232" %) |
| 108 | RS-232 or TelNet integration supported | ||
| |
1.1 | 109 | |
| 110 | == MechoNet Interface (MNI) == | ||
| 111 | |||
| |
2.1 | 112 | (% class="wikigeneratedid" id="HMNIRS-232" %) |
| 113 | Only RS-232 integration supported | ||
| |
1.1 | 114 | |
| 115 | == Mecho SolarTrac4 == | ||
| 116 | |||
| |
2.1 | 117 | (% class="wikigeneratedid" id="HSolarTrac4BACnet" %) |
| 118 | Only BACnet integration supported | ||
| |
1.1 | 119 | |
| 120 | == Nice DMBM == | ||
| 121 | |||
| |
2.1 | 122 | (% class="wikigeneratedid" id="HDMBMRS-232" %) |
| 123 | Only RS-232 integration supported | ||
| |
1.1 | 124 | |
| 125 | == Somfy Digital Network (SDN) == | ||
| 126 | |||
| 127 | === SDN RS-485 === | ||
| 128 | |||
| 129 | === SDN PoE Gateway === | ||
| 130 | |||
| 131 | === SDN UAI+ === | ||
| 132 | |||
| 133 | == Somfy URTSI II == | ||
| 134 | |||
| |
2.1 | 135 | (% class="wikigeneratedid" id="HURTSIIIRS-232" %) |
| 136 | RS-232 or RS-485 integration supported | ||
| |
1.1 | 137 | ))) |
| 138 | |||
| 139 | |||
| 140 | (% class="col-xs-12 col-sm-4" %) | ||
| 141 | ((( | ||
| 142 | {{box title="**CONTENTS**"}} | ||
| 143 | {{toc/}} | ||
| 144 | {{/box}} | ||
| 145 | ))) | ||
| 146 | ))) |