Changes for page Shades Integrations

Summary

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

Details

Page properties

Content

...	...	@@ -2,7 +2,7 @@
2	2	(((
3	3	(% class="box infomessage" %)
4	4	(((
5		-Note: page is under construction, check back later for updates
	5	+Note: this page is currently under construction, check back later for updates
6	6	)))
7	7
8	8	(% class="col-xs-12 col-sm-8" %)
...	...	@@ -17,16 +17,45 @@
17	17
18	18	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™.
19	19
20		-== C2N-SDC(-DC) ==
	20	+== Supported Hardware ==
21	21
22		-== CSA-PWS10S-HUB-ENET ==
	22	+ShowRunnerCLC™ includes support for the following Crestron shade controllers:
23	23
24		-== DIN-2MC2 ==
	24	+* C2N-SDC and C2N-SDC-DC
	25	+* CSC Series Controllers (discontinued)
	26	+* CSA-PWS10S-HUB-ENET (controlling QMT-series motors)
	27	+* DIN-2MC2
	28	+* Ethernet Inter-System Communications (Crestron-to-Crestron)
25	25
26		-== Ethernet Inter-Systems Communication (EISC) ==
	30	+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.
27	27
28		-= Third-Party Shade Controllers =
	32	+== Information Required ==
29	29
	34	+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.
	35	+
	36	+Non-EISC shades:
	37	+
	38	+* **(Required)** Quantity of shade controllers
	39	+* **(Required)** Quantity and location of each shade motor to be controlled
	40	+** For all controllers, we must know which shade motor (i.e. window and room) is connected to each output
	41	+** For systems with multiple CSA-PSW10S-HUB-ENET, we must know which HUB is the Cresnet primary
	42	+
	43	+EISC shades:
	44	+
	45	+* **(Required)** Type of EISC integration (TCP or UDP)
	46	+* **(Required)** IP Address and IP-ID of non-ShowRunnerCLC™ processor
	47	+* **(Required) **Joins to be used for shade control and feedback (see table below; not all features are required for all integrations)
	48	+
	49	+(% style="width:632px" %)
	50	+|=Join|=(% style="width: 344px;" %)Description|=(% style="width: 6px;" %)Type|=(% style="width: 101px;" %)Direction
	51	+|JoinOpen|(% style="width:344px" %)Sends a digital pulse when open is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
	52	+|JoinClose|(% style="width:344px" %)Sends a digital pulse when close is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
	53	+|JoinStop|(% style="width:344px" %)Sends a digital pulse when stop is triggered|(% style="width:6px" %)Digital|(% style="width:101px" %)To 3rd Party
	54	+|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
	55	+|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
	56	+
	57	+= Third-Party Shade Integrations =
	58	+
30	30	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™.
31	31
32	32	== Common Integration Methods ==
...	...	@@ -45,7 +45,7 @@
45	45	* TCP/IP communication (including HTTP/HTTPS, TelNet, etc.)
46	46	** Standard [[Ethernet wiring limitations>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Ethernet Wiring Overview.WebHome]] apply
47	47
48		-Below is a non-exhaustive table showing which pieces of Crestron hardware have interfaces for each kind of integration:
	77	+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):
49	49
50	50	|=Hardware|=Relay Outputs|=RS-485 Serial Ports|=RS-232 Serial Ports
51	51	|C2N-IO|2|✖|1
...	...	@@ -63,6 +63,29 @@
63	63
64	64	== Contact Closure (Relays) ==
65	65
	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. All contact closure shade integrations are assumed to use two relays per shade zone with standard outputs as follows:
	96	+
	97	+* Open: close relay 1
	98	+* Close: close relay 2
	99	+* Stop: close both relays simultaneously
	100	+
	101	+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.
	102	+
	103	+=== Hardware Requirements ===
	104	+
	105	+* 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)
	106	+* Two Crestron output relays must be available for each zone of shades to be controlled
	107	+** 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
	108	+* 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
	109	+
	110	+=== Information Requirements ===
	111	+
	112	+* **(Required)** Quantity and location of Crestron devices to be used for contact closure shade control
	113	+* **(Required)** Quantity and locations of shade zones to be controlled
	114	+* **(Required)** Information associating each shade zone with a relay pair
	115	+** 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
	116	+** 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
	117	+
66	66	== Draper IntelliFlex I/O A\V Gateway ==
67	67
68	68	(% class="wikigeneratedid" %)
...	...	@@ -78,10 +78,10 @@
78	78	(% class="wikigeneratedid" id="HQuantumRS-232" %)
79	79	RS-232 or TelNet integration supported
80	80
81		-== MechoNet Interface (MNI) ==
	133	+== MechoNet Network Interface (MNI) ==
82	82
83	83	(% class="wikigeneratedid" id="HMNIRS-232" %)
84		-Only RS-232 integration supported
	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)
85	85
86	86	== Mecho SolarTrac4 ==
87	87