Shades Integrations

(% class="box warningmessage" %)

(((

**NOTICE: Always check manufacturer product specifications to verify features and compatibility prior to ordering hardware.**

4

While we at Chief Integrations strive to provide accurate and complete information, we cannot guarantee that the information provided here will always be 100% accurate and up-to-date.

5

)))

6

7

(% class="col-xs-12 col-sm-8" %)

8

(((

9

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.

10

11

= Crestron Shade Controllers =

12

13

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.

14

15

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™.

16

17

== Supported Hardware ==

18

19

ShowRunnerCLC™ includes support for the following Crestron shade controllers:

20

21

* C2N-SDC and C2N-SDC-DC

22

* CSC Series Controllers (discontinued)

23

* CSA-PWS10S-HUB-ENET (controlling QMT-series motors)

24

* DIN-2MC2

25

* Ethernet Inter-System Communications (Crestron-to-Crestron)

26

27

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.

28

29

== Information Required ==

30

31

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.

Non-EISC shades:

* **(Required)** Quantity of shade controllers

36

* **(Required)** Quantity and location of each shade motor to be controlled

37

** For all controllers, we must know which shade motor (i.e. window and room) is connected to each output

38

** For systems with multiple CSA-PSW10S-HUB-ENET, we must know which HUB is the Cresnet primary

EISC shades:

* **(Required)** Type of EISC integration (TCP or UDP)

43

* **(Required)** IP Address and IP-ID for the non-ShowRunnerCLC™ processor

44

* **(Required) **Joins to be used for shade control and feedback (see table below; not all features are required for all integrations)

45

46

(% style="width:632px" %)

47

|=Join|=(% style="width: 344px;" %)Description|=(% style="width: 6px;" %)Type|=(% style="width: 101px;" %)Direction

48

|JoinOpen|(% style="width:344px" %)Sends a digital pulse when open is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party

49

|JoinClose|(% style="width:344px" %)Sends a digital pulse when close is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party

50

|JoinStop|(% style="width:344px" %)Sends a digital pulse when stop is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party

51

|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

52

|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

53

54

= Third-Party Shade Integrations =

55

56

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™.

57

58

== Common Integration Methods ==

59

60

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™:

61

62

* Contact closure (Relays)

63

** Shades are controlled by ShowRunnerCLC™-controlled contact closure relays

64

** Typically requires two relays per shade motor or collection of shade motors to be controlled (one relay for "open" and one relay for "close")

65

** No standard specified length limitation for wiring (individual shade manufacturers may specify cabling and distance limitations)

66

** 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

67

* Serial RS-232

68

** Shades are controlled by a ShowRunnerCLC™-controlled serial communications port through wiring which adheres to RS-232 specification

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

** Shades are controlled by a ShowRunnerCLC™-controlled serial communications port through wiring which adheres to RS-485 specification

73

** 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)

74

** 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)

75

* TCP/IP communication (including HTTP/HTTPS, TelNet, etc.)

76

** Shades are controlled by ShowRunnerCLC™ through the LAN port using standard Ethernet cabling and TCP/IP (% style="display:none" %) (%%)communications protocols(% style="display:none" %)

77

** 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

78

** Standard [[Ethernet wiring limitations>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Ethernet Wiring Overview.WebHome]] apply

79

80

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):

81

82

|=Hardware|=Relay Outputs|=RS-485 Serial Ports|=RS-232 Serial Ports

83

|C2N-IO|2|✖|1

84

|INET-IOEX-RYIO|2|✖|✖

85

|CP3N / CP4N|8|1*|3*

86

|DIN-IO8|8|✖|✖

87

|DIN-AP3 / DIN-AP4|4|2*|2*

88

|(((

89

GLPAC-DIMFLV4-PM / GLPAC-DIMFLV8-PM

(PM models only)

)))|4|✖|✖

|RMC3 / RMC4|2|1*|1*

|ZUM-HUB4|✖|✖|✖

|(% colspan="4" %)* Some serial ports are dual-purpose and can be //either// RS-485 //or// RS-232; other serial ports are //only// RS-232

95

96

== Contact Closure (Relays) ==

97

98

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:

99

100

* Open: close relay 1

101

* Close: close relay 2

102

* Stop: close both relays simultaneously

103

104

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.

105

106

=== Hardware Requirements ===

107

108

* 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)

109

* Two Crestron output relays must be available for each zone of shades to be controlled

110

** 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

111

* 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

112

113

=== Information Requirements ===

114

115

* **(Required)** Quantity and location of Crestron devices to be used for contact closure shade control

116

* **(Required)** Quantity and locations of shade zones to be controlled

117

* **(Required)** Information associating each shade zone with a relay pair

118

** 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

119

** 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

120

121

== Draper IntelliFlex I/O A\V Gateway ==

122

123

(% class="wikigeneratedid" %)

124

RS-232 or RS-485 integration supported

125

126

== Lutron Sivoia QS (Quantum) ==

127

128

(% class="wikigeneratedid" id="HSivoiaQSRS-232" %)

129

RS-232 or TelNet integration supported

130

131

== MechoNet Network Interface (MNI) ==

132

133

(% class="wikigeneratedid" %)

134

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.

135

136

=== Hardware Requirements ===

137

138

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:

139

140

* For RS-232 integration:

141

** One RS-232 port on the ShowRunnerCLC™ system must be available for each MNI to be integrated

142

** 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 are networked together and configured on the MechoNet side

143

* For contact closure integration:

144

** 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**

145

** 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)

146

* For RS-485 or IR integration, reach out to Chief Integrations for potentially adding these integrations

147

148

=== Information Requirements ===

149

150

Specific information requirements depend on which method of integration is required:

151

152

* **(Required)** Specify whether integration is being done through RS-232 or contact closures

153

* For RS-232 integration:

154

** **(Required) **MechoNet devices must be addressed so that it is possible to control them per the SOO using their Zone, Group, Node addresses

155

*** MechoNet devices are assigned three-part Zone, Group, Node addresses similar to an IPv4 address with 3 parts instead of 4

156

*** e.g. a ZGN address of 128.151.253 represents a device in zone 128, group 151, and node 253

157

** **(Required) **ZGN addresses must be provided for all shades to be controlled

158

** **(Required)** location for each shade to be controlled so that they can be assigned to the correct areas in ShowRunnerCLC™

159

* For contact closure integration:

160

** **(Required)** all information specified in the [[general contact closure>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.Shades Integrations.WebHome||anchor="HInformationRequirements"]] section above

161

** **(Required)** indicate which Crestron relays correspond to each motor on each MNI, and which shades are controlled by each motor

162

163

== Mecho SolarTrac4 ==

164

165

(% class="wikigeneratedid" id="HSolarTrac4BACnet" %)

166

Only BACnet integration supported

167

168