Changes for page Shades Integrations

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,11 +1,16 @@
1		-(% class="box warningmessage" %)
	1	+(% class="row" %)
2	2	(((
3		-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.
	3	+(% class="box infomessage" %)
	4	+(((
	5	+Note: page is under construction, check back later for updates
4	4	)))
	7	+
5	5	(% class="col-xs-12 col-sm-8" %)
6	6	(((
7	7	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.
8	8
	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.
	13	+
9	9	= Crestron Shade Controllers =
10	10
11	11	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.
...	...	@@ -12,45 +12,16 @@
12	12
13	13	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™.
14	14
15		-== Supported Hardware ==
	20	+== C2N-SDC(-DC) ==
16	16
17		-ShowRunnerCLC™ includes support for the following Crestron shade controllers:
	22	+== CSA-PWS10S-HUB-ENET ==
18	18
19		-* C2N-SDC and C2N-SDC-DC
20		-* CSC Series Controllers (discontinued)
21		-* CSA-PWS10S-HUB-ENET (controlling QMT-series motors)
22		-* DIN-2MC2
23		-* Ethernet Inter-System Communications (Crestron-to-Crestron)
	24	+== DIN-2MC2 ==
24	24
25		-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.
	26	+== Ethernet Inter-Systems Communication (EISC) ==
26	26
27		-== Information Required ==
	28	+= Third-Party Shade Controllers =
28	28
29		-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.
30		-
31		-Non-EISC shades:
32		-
33		-* **(Required)** Quantity of shade controllers
34		-* **(Required)** Quantity and location of each shade motor to be controlled
35		-** For all controllers, we must know which shade motor (i.e. window and room) is connected to each output
36		-** For systems with multiple CSA-PSW10S-HUB-ENET, we must know which HUB is the Cresnet primary
37		-
38		-EISC shades:
39		-
40		-* **(Required)** Type of EISC integration (TCP or UDP)
41		-* **(Required)** IP Address and IP-ID for the non-ShowRunnerCLC™ processor
42		-* **(Required) **Joins to be used for shade control and feedback (see table below; not all features are required for all integrations)
43		-
44		-(% style="width:632px" %)
45		-|=Join|=(% style="width: 344px;" %)Description|=(% style="width: 6px;" %)Type|=(% style="width: 101px;" %)Direction
46		-|JoinOpen|(% style="width:344px" %)Sends a digital pulse when open is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
47		-|JoinClose|(% style="width:344px" %)Sends a digital pulse when close is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
48		-|JoinStop|(% style="width:344px" %)Sends a digital pulse when stop is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
49		-|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
50		-|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
51		-
52		-= Third-Party Shade Integrations =
53		-
54	54	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™.
55	55
56	56	== Common Integration Methods ==
...	...	@@ -58,24 +58,18 @@
58	58	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™:
59	59
60	60	* Contact closure (Relays)
61		-** Shades are controlled by ShowRunnerCLC™-controlled contact closure relays
62		-** Typically requires two relays per shade motor or collection of shade motors to be controlled (one relay for "open" and one relay for "close")
63		-** No standard specified length limitation for wiring (individual shade manufacturers may specify cabling and distance limitations)
	37	+** No standard specified length limitation (individual shade manufacturers may specify cabling and distance limitations)
64	64	** 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
65	65	* Serial RS-232
66		-** Shades are controlled by a ShowRunnerCLC™-controlled serial communications port through wiring which adheres to RS-232 specification
67	67	** 50' maximum distance per specification
68	68	** 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)
69	69	* Serial RS-485
70		-** Shades are controlled by a ShowRunnerCLC™-controlled serial communications port through wiring which adheres to RS-485 specification
71	71	** 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)
72	72	** 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)
73	73	* TCP/IP communication (including HTTP/HTTPS, TelNet, etc.)
74		-** Shades are controlled by ShowRunnerCLC™ through the LAN port using standard Ethernet cabling and TCP/IP (% style="display:none" %) (%%)communications protocols(% style="display:none" %)
75		-** 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
76	76	** Standard [[Ethernet wiring limitations>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Ethernet Wiring Overview.WebHome]] apply
77	77
78		-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):
	48	+Below is a non-exhaustive table showing which pieces of Crestron hardware have interfaces for each kind of integration:
79	79
80	80	|=Hardware|=Relay Outputs|=RS-485 Serial Ports|=RS-232 Serial Ports
81	81	|C2N-IO|2|✖|1
...	...	@@ -93,29 +93,6 @@
93	93
94	94	== Contact Closure (Relays) ==
95	95
96		-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:
97		-
98		-* Open: close relay 1
99		-* Close: close relay 2
100		-* Stop: close both relays simultaneously
101		-
102		-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.
103		-
104		-=== Hardware Requirements ===
105		-
106		-* 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)
107		-* Two Crestron output relays must be available for each zone of shades to be controlled
108		-** 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
109		-* 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
110		-
111		-=== Information Requirements ===
112		-
113		-* **(Required)** Quantity and location of Crestron devices to be used for contact closure shade control
114		-* **(Required)** Quantity and locations of shade zones to be controlled
115		-* **(Required)** Information associating each shade zone with a relay pair
116		-** 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
117		-** 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
118		-
119	119	== Draper IntelliFlex I/O A\V Gateway ==
120	120
121	121	(% class="wikigeneratedid" %)
...	...	@@ -131,38 +131,11 @@
131	131	(% class="wikigeneratedid" id="HQuantumRS-232" %)
132	132	RS-232 or TelNet integration supported
133	133
134		-== MechoNet Network Interface (MNI) ==
	81	+== MechoNet Interface (MNI) ==
135	135
136		-(% class="wikigeneratedid" %)
137		-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.
	83	+(% class="wikigeneratedid" id="HMNIRS-232" %)
	84	+Only RS-232 integration supported
138	138
139		-=== Hardware Requirements ===
140		-
141		-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:
142		-
143		-* For RS-232 integration:
144		-** One RS-232 port on the ShowRunnerCLC™ system must be available for each MNI to be integrated
145		-** 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
146		-* For contact closure integration:
147		-** 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**
148		-** 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)
149		-* For RS-485 or IR integration, reach out to Chief Integrations for potentially adding these integrations
150		-
151		-=== Information Requirements ===
152		-
153		-Specific information requirements depend on which method of integration is required:
154		-
155		-* **(Required)** Specify whether integration is being done through RS-232 or contact closures
156		-* For RS-232 integration:
157		-** **(Required) **MechoNet devices must be addressed so that it is possible to control them per the SOO using their Zone, Group, Node addresses
158		-*** MechoNet devices are assigned three-part Zone, Group, Node addresses similar to an IPv4 address with 3 parts instead of 4
159		-*** e.g. a ZGN address of 128.151.253 represents a device in zone 128, group 151, and node 253
160		-** **(Required) **ZGN addresses must be provided for all shades to be controlled
161		-** **(Required)** location for each shade to be controlled so that they can be assigned to the correct areas in ShowRunnerCLC™
162		-* For contact closure integration:
163		-** **(Required)** all information specified in the [[general contact closure>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.Shades Integrations.WebHome||anchor="HInformationRequirements"]] section above
164		-** **(Required)** indicate which Crestron relays correspond to each motor on each MNI, and which shades are controlled by each motor
165		-
166	166	== Mecho SolarTrac4 ==
167	167
168	168	(% class="wikigeneratedid" id="HSolarTrac4BACnet" %)
...	...	@@ -194,5 +194,4 @@
194	194	{{toc/}}
195	195	{{/box}}
196	196	)))
197		-
198		-
	117	+)))