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
on 2024/06/17 16:16
Change comment:
There is no comment for this version
To version 7.1
edited by Alexander Mott
on 2024/06/14 22:31
on 2024/06/14 22:31
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,3 +1,10 @@ 1 +(% class="row" %) 2 +((( 3 +(% class="box infomessage" %) 4 +((( 5 +Note: this page is currently 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 forthenon-ShowRunnerCLC™ processor46 +* **(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,21 +56,15 @@ 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 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): ... ... @@ -131,36 +131,9 @@ 131 131 132 132 == MechoNet Network Interface (MNI) == 133 133 134 -(% class="wikigeneratedid" %) 135 - MechoShade'sMechoNet NetworkInterface(MNI) allows integrating control of MechoNet hardware with third-partysystems suchas ShowRunnerCLC™througha variety ofdifferentmeans. ShowRunnerCLC™ currentlyonlysupportsusing RS-232 or contact closure integrations:reachoutto ChiefIntegrationsforpricingif RS-485orIR integrations arerequired.135 +(% class="wikigeneratedid" id="HMNIRS-232" %) 136 +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) 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 - 169 +)))