Wiki source code of Shades Integrations

Version 8.1 by Alexander Mott on 2024/06/14 23:13

Hide last authors
Alexander Mott 1.1 1 (% class="col-xs-12 col-sm-8" %)
2 (((
Alexander Mott 2.1 3 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.
Alexander Mott 1.1 4
Alexander Mott 2.1 5 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.
Alexander Mott 1.1 6
7 = Crestron Shade Controllers =
8
Alexander Mott 2.1 9 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.
Alexander Mott 1.1 10
Alexander Mott 2.1 11 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™.
Alexander Mott 1.1 12
Alexander Mott 4.1 13 == Supported Hardware ==
Alexander Mott 1.1 14
Alexander Mott 4.1 15 ShowRunnerCLC™ includes support for the following Crestron shade controllers:
Alexander Mott 1.1 16
Alexander Mott 4.1 17 * C2N-SDC and C2N-SDC-DC
18 * CSC Series Controllers (discontinued)
19 * CSA-PWS10S-HUB-ENET (controlling QMT-series motors)
20 * DIN-2MC2
21 * Ethernet Inter-System Communications (Crestron-to-Crestron)
Alexander Mott 1.1 22
Alexander Mott 4.1 23 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.
Alexander Mott 1.1 24
Alexander Mott 4.1 25 == Information Required ==
26
27 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.
28
29 Non-EISC shades:
30
31 * **(Required)** Quantity of shade controllers
32 * **(Required)** Quantity and location of each shade motor to be controlled
33 ** For all controllers, we must know which shade motor (i.e. window and room) is connected to each output
34 ** For systems with multiple CSA-PSW10S-HUB-ENET, we must know which HUB is the Cresnet primary
35
36 EISC shades:
37
38 * **(Required)** Type of EISC integration (TCP or UDP)
39 * **(Required)** IP Address and IP-ID of non-ShowRunnerCLC™ processor
40 * **(Required) **Joins to be used for shade control and feedback (see table below; not all features are required for all integrations)
41
42 (% style="width:632px" %)
43 |=Join|=(% style="width: 344px;" %)Description|=(% style="width: 6px;" %)Type|=(% style="width: 101px;" %)Direction
44 |JoinOpen|(% style="width:344px" %)Sends a digital pulse when open is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
45 |JoinClose|(% style="width:344px" %)Sends a digital pulse when close is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
46 |JoinStop|(% style="width:344px" %)Sends a digital pulse when stop is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
47 |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
48 |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
49
Alexander Mott 5.1 50 = Third-Party Shade Integrations =
Alexander Mott 1.1 51
Alexander Mott 2.1 52 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™.
Alexander Mott 1.1 53
Alexander Mott 2.1 54 == Common Integration Methods ==
Alexander Mott 1.1 55
Alexander Mott 2.1 56 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™:
Alexander Mott 1.1 57
Alexander Mott 2.1 58 * Contact closure (Relays)
59 ** No standard specified length limitation (individual shade manufacturers may specify cabling and distance limitations)
60 ** 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
61 * Serial RS-232
62 ** 50' maximum distance per specification
63 ** 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)
64 * Serial RS-485
65 ** 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)
66 ** 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)
67 * TCP/IP communication (including HTTP/HTTPS, TelNet, etc.)
68 ** Standard [[Ethernet wiring limitations>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Ethernet Wiring Overview.WebHome]] apply
Alexander Mott 1.1 69
Alexander Mott 5.5 70 Below is a non-exhaustive table showing which pieces of Crestron hardware have interfaces for each kind of integration (all processors are capable of TCP/IP integration provided the network has been configured correctly):
Alexander Mott 1.1 71
Alexander Mott 2.2 72 |=Hardware|=Relay Outputs|=RS-485 Serial Ports|=RS-232 Serial Ports
73 |C2N-IO|2|✖|1
Alexander Mott 2.4 74 |INET-IOEX-RYIO|2|✖|✖
Alexander Mott 2.2 75 |CP3N / CP4N|8|1*|3*
76 |DIN-IO8|8|✖|✖
Alexander Mott 2.3 77 |DIN-AP3 / DIN-AP4|4|2*|2*
78 |(((
79 GLPAC-DIMFLV4-PM / GLPAC-DIMFLV8-PM
Alexander Mott 2.4 80 (PM models only)
Alexander Mott 2.3 81 )))|4|✖|✖
82 |RMC3 / RMC4|2|1*|1*
Alexander Mott 2.4 83 |ZUM-HUB4|✖|✖|✖
Alexander Mott 2.3 84 |(% colspan="4" %)* Some serial ports are dual-purpose and can be //either// RS-485 //or// RS-232; other serial ports are //only// RS-232
Alexander Mott 1.1 85
Alexander Mott 2.1 86 == Contact Closure (Relays) ==
Alexander Mott 1.1 87
Alexander Mott 7.1 88 ShowRunnerCLC™ can use output relays on Crestron hardware to control shades provided that the shades controller is capable of accepting a contact closure input for third-party control of the shades. All contact closure shade integrations are assumed to use two relays per shade zone with standard outputs as follows:
Alexander Mott 5.2 89
Alexander Mott 7.1 90 * Open: close relay 1
91 * Close: close relay 2
92 * Stop: close both relays simultaneously
93
94 Shade motors must be wired accordingly by the EC or the shades contractor (Chief Integrations technicians do not touch wiring). If the shades interfaces cannot be controlled this way, contact Chief Integrations to see about possibilities for support for shade controls using either a single relay or three or more relays per zone.
95
Alexander Mott 5.3 96 === Hardware Requirements ===
Alexander Mott 5.2 97
Alexander Mott 7.1 98 * Crestron devices with output relays must be specified (refer to [[the above table>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.Shades Integrations.WebHome||anchor="HCommonIntegrationMethods"]] for commonly specified hardware)
Alexander Mott 5.5 99 * Two Crestron output relays must be available for each zone of shades to be controlled
Alexander Mott 5.4 100 ** Depending on the shade hardware and the job requirements, it may be possible to combine multiple shades to be controlled together onto a single pair of Crestron relays
Alexander Mott 7.1 101 * It is recommended that shade interfaces be installed as close as possible to the Crestron relays controlling them to prevent issues from voltage drop or EMF interference in the wiring between the relay and the shade interface
Alexander Mott 5.3 102
Alexander Mott 5.2 103 === Information Requirements ===
104
Alexander Mott 6.1 105 * **(Required)** Quantity and location of Crestron devices to be used for contact closure shade control
106 * **(Required)** Quantity and locations of shade zones to be controlled
Alexander Mott 7.1 107 * **(Required)** Information associating each shade zone with a relay pair
108 ** If C2N-IO or other in-field relay modules are being used, then we must know which shade(s) in which room(s) are controlled by each C2N-IO
109 ** If a processor or other in-panel modules are being used, then we must know which shade(s) in which room(s) are controlled by relays 1 & 2, which are controlled by relays 3 & 4, etc. for each module
Alexander Mott 5.3 110
Alexander Mott 2.1 111 == Draper IntelliFlex I/O A\V Gateway ==
Alexander Mott 1.1 112
Alexander Mott 2.1 113 (% class="wikigeneratedid" %)
114 RS-232 or RS-485 integration supported
Alexander Mott 1.1 115
Alexander Mott 2.1 116 == Lutron Sivoia QS ==
Alexander Mott 1.1 117
Alexander Mott 2.1 118 (% class="wikigeneratedid" id="HSivoiaQSRS-232" %)
119 RS-232 or TelNet integration supported
Alexander Mott 1.1 120
121 == Lutron Quantum ==
122
Alexander Mott 2.1 123 (% class="wikigeneratedid" id="HQuantumRS-232" %)
124 RS-232 or TelNet integration supported
Alexander Mott 1.1 125
Alexander Mott 5.2 126 == MechoNet Network Interface (MNI) ==
Alexander Mott 1.1 127
Alexander Mott 7.2 128 (% class="wikigeneratedid" %)
129 Mecho Shade's MechoNet Network Interface (MNI) allows integrating control of MechoNet hardware with third-party systems such as ShowRunnerCLC™ through a variety of different means. ShowRunnerCLC™ currently only supports using RS-232 or contact closure integrations: reach out to Chief Integrations for pricing if RS-485 or IR integrations are required.
130
Alexander Mott 2.1 131 (% class="wikigeneratedid" id="HMNIRS-232" %)
Alexander Mott 6.1 132 RS-232 or contact closure integration supported (reach out to Chief Integrations if RS-485 integration is required; contact closure integration is only available if Mecho wall switch ports are not being used)
Alexander Mott 1.1 133
Alexander Mott 7.2 134 === Hardware Requirements ===
135
136 Specific hardware requirements depend on which method of integration is required:
137
138
139 === Information Requirements ===
140
141 Specific information requirements depend on which method of integration is required:
142
Alexander Mott 8.1 143 * **(Required) **Whether integration is being done through RS-232 or contact closures
Alexander Mott 7.2 144 * For RS-232 integration:
145 * For contact closure integration:
Alexander Mott 8.1 146 ** (Required) the same information as specified in the [[contact closure section above>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.Shades Integrations.WebHome||anchor="HContactClosure%28Relays%29"]] f
Alexander Mott 7.2 147
Alexander Mott 1.1 148 == Mecho SolarTrac4 ==
149
Alexander Mott 2.1 150 (% class="wikigeneratedid" id="HSolarTrac4BACnet" %)
151 Only BACnet integration supported
Alexander Mott 1.1 152
153 == Nice DMBM ==
154
Alexander Mott 2.1 155 (% class="wikigeneratedid" id="HDMBMRS-232" %)
156 Only RS-232 integration supported
Alexander Mott 1.1 157
158 == Somfy Digital Network (SDN) ==
159
160 === SDN RS-485 ===
161
162 === SDN PoE Gateway ===
163
164 === SDN UAI+ ===
165
166 == Somfy URTSI II ==
167
Alexander Mott 2.1 168 (% class="wikigeneratedid" id="HURTSIIIRS-232" %)
169 RS-232 or RS-485 integration supported
Alexander Mott 1.1 170 )))
171
172
173 (% class="col-xs-12 col-sm-4" %)
174 (((
175 {{box title="**CONTENTS**"}}
176 {{toc/}}
177 {{/box}}
178 )))
Alexander Mott 7.2 179
180