Skip to Content

Changes for page Shades Integrations

Last modified by Alexander Mott on 2024/06/17 18:07
From version 12.1
edited by Alexander Mott
on 2024/06/17 16:16
Change comment: There is no comment for this version
To version 5.4
edited by Alexander Mott
on 2024/06/14 22:11
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -1,3 +1,10 @@
1 +(% class="row" %)
2 +(((
3 +(% class="box infomessage" %)
4 +(((
5 +Note: page is under construction, check back later for updates
6 +)))
7 +
1 1  (% class="col-xs-12 col-sm-8" %)
2 2  (((
3 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.
... ... @@ -36,7 +36,7 @@
36 36  EISC shades:
37 37  
38 38  * **(Required)** Type of EISC integration (TCP or UDP)
39 -* **(Required)** IP Address and IP-ID for the non-ShowRunnerCLC™ processor
46 +* **(Required)** IP Address and IP-ID of non-ShowRunnerCLC™ processor
40 40  * **(Required) **Joins to be used for shade control and feedback (see table below; not all features are required for all integrations)
41 41  
42 42  (% style="width:632px" %)
... ... @@ -56,24 +56,18 @@
56 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™:
57 57  
58 58  * Contact closure (Relays)
59 -** Shades are controlled by ShowRunnerCLC™-controlled contact closure relays
60 -** Typically requires two relays per shade motor or collection of shade motors to be controlled (one relay for "open" and one relay for "close")
61 -** No standard specified length limitation for wiring (individual shade manufacturers may specify cabling and distance limitations)
66 +** No standard specified length limitation (individual shade manufacturers may specify cabling and distance limitations)
62 62  ** 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
63 63  * Serial RS-232
64 -** Shades are controlled by a ShowRunnerCLC™-controlled serial communications port through wiring which adheres to RS-232 specification
65 65  ** 50' maximum distance per specification
66 66  ** 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)
67 67  * Serial RS-485
68 -** Shades are controlled by a ShowRunnerCLC™-controlled serial communications port through wiring which adheres to RS-485 specification
69 69  ** 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)
70 70  ** 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)
71 71  * TCP/IP communication (including HTTP/HTTPS, TelNet, etc.)
72 -** Shades are controlled by ShowRunnerCLC™ through the LAN port using standard Ethernet cabling and TCP/IP (% style="display:none" %) (%%)communications protocols(% style="display:none" %)  
73 -** ShowRunnerCLC™ processor and shades interface must be able to communicate with each other, typically requiring either that the shades interface and lighting processor are  located on the same LAN/VLAN or that the building IT be involved to ensure that communications are possible between the two systems
74 74  ** Standard [[Ethernet wiring limitations>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Ethernet Wiring Overview.WebHome]] apply
75 75  
76 -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):
77 +Below is a non-exhaustive table showing which pieces of Crestron hardware have interfaces for each kind of integration:
77 77  
78 78  |=Hardware|=Relay Outputs|=RS-485 Serial Ports|=RS-232 Serial Ports
79 79  |C2N-IO|2|✖|1
... ... @@ -91,28 +91,23 @@
91 91  
92 92  == Contact Closure (Relays) ==
93 93  
94 -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:
95 +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.
95 95  
96 -* Open: close relay 1
97 -* Close: close relay 2
98 -* Stop: close both relays simultaneously
99 -
100 -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.
101 -
102 102  === Hardware Requirements ===
103 103  
104 -* 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)
105 -* Two Crestron output relays must be available for each zone of shades to be controlled
99 +* Crestron devices with output relays must be specified (refer to table above for commonly specified hardware)
100 +* Two Crestron relays must be available for each zone of shades to be controlled
106 106  ** 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
107 -* 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
102 +* Standard command outputs are as follows:
103 +** Open: close relay 1
104 +** Close: close relay 2
105 +** Stop: close both relays simultaneously
106 +* 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 in the wiring between the relay and the shade interface
108 108  
109 109  === Information Requirements ===
110 110  
111 -* **(Required)** Quantity and location of Crestron devices to be used for contact closure shade control
112 -* **(Required)** Quantity and locations of shade zones to be controlled
113 -* **(Required)** Information associating each shade zone with a relay pair
114 -** 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
115 -** 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
110 +* (Required) Quantity and location of Crestron devices to be used for contact closure shade control
111 +* (Required) Quantity and location of shades to be controlled
116 116  
117 117  == Draper IntelliFlex I/O A\V Gateway ==
118 118  
... ... @@ -131,36 +131,9 @@
131 131  
132 132  == MechoNet Network Interface (MNI) ==
133 133  
134 -(% class="wikigeneratedid" %)
135 -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 +(% class="wikigeneratedid" id="HMNIRS-232" %)
131 +Only RS-232 integration supported (contact closure available if Mecho wall switch ports are not used)
136 136  
137 -=== Hardware Requirements ===
138 -
139 -Refer to [[the above table>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.Shades Integrations.WebHome||anchor="HCommonIntegrationMethods"]] for general hardware compatibility. MNI-specific details are below depending on how shades are being integrated:
140 -
141 -* For RS-232 integration:
142 -** One RS-232 port on the ShowRunnerCLC™ system must be available for each MNI to be integrated
143 -** Depending on how the MechoNet system is designed, it may be possible to control many shades through a single RS-232 integration provided that any additional MNI and controlled MechoNet hardware is networked together and configured on the MechoNet side
144 -* For contact closure integration:
145 -** Contact closure integration utilizes the MNI switch input ports: **it is not possible to use contact closure integration if Mecho switches are installed to control the shades**
146 -** Two relays must be available for each Mecho motor to be controlled (it is possible to control multiple Mecho motors from a single relay pair provided that the MNI switch ports are wired in parallel)
147 -* For RS-485 or IR integration, reach out to Chief Integrations for potentially adding these integrations
148 -
149 -=== Information Requirements ===
150 -
151 -Specific information requirements depend on which method of integration is required:
152 -
153 -* **(Required)** Specify whether integration is being done through RS-232 or contact closures
154 -* For RS-232 integration:
155 -** **(Required) **MechoNet devices must be addressed so that it is possible to control them per the SOO using their Zone, Group, Node addresses
156 -*** MechoNet devices are assigned three-part Zone, Group, Node addresses similar to an IPv4 address with 3 parts instead of 4
157 -*** e.g. a ZGN address of 128.151.253 represents a device in zone 128, group 151, and node 253
158 -** **(Required) **ZGN addresses must be provided for all shades to be controlled
159 -** **(Required)** location for each shade to be controlled so that they can be assigned to the correct areas in ShowRunnerCLC™
160 -* For contact closure integration:
161 -** **(Required)** all information specified in the [[general contact closure>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.Shades Integrations.WebHome||anchor="HInformationRequirements"]] section above
162 -** **(Required)** indicate which Crestron relays correspond to each motor on each MNI, and which shades are controlled by each motor
163 -
164 164  == Mecho SolarTrac4 ==
165 165  
166 166  (% class="wikigeneratedid" id="HSolarTrac4BACnet" %)
... ... @@ -192,5 +192,4 @@
192 192  {{toc/}}
193 193  {{/box}}
194 194  )))
195 -
196 -
164 +)))