Changes for page Shades Integrations

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: 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.
...	...	@@ -47,7 +47,7 @@
47	47	|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
48	48	|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
49	49
50		-= Third-Party Shade Integrations =
	57	+= Third-Party Shade Controllers =
51	51
52	52	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™.
53	53
...	...	@@ -67,7 +67,7 @@
67	67	* TCP/IP communication (including HTTP/HTTPS, TelNet, etc.)
68	68	** Standard [[Ethernet wiring limitations>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Troubleshooting.Ethernet Wiring Overview.WebHome]] apply
69	69
70		-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:
71	71
72	72	|=Hardware|=Relay Outputs|=RS-485 Serial Ports|=RS-232 Serial Ports
73	73	|C2N-IO|2|✖|1
...	...	@@ -85,29 +85,6 @@
85	85
86	86	== Contact Closure (Relays) ==
87	87
88		-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:
89		-
90		-* Open: close relay 1
91		-* Close: close relay 2
92		-* Stop: close both relays simultaneously
93		-
94		-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.
95		-
96		-=== Hardware Requirements ===
97		-
98		-* 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)
99		-* Two Crestron output relays must be available for each zone of shades to be controlled
100		-** 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
101		-* 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		-
103		-=== Information Requirements ===
104		-
105		-* **(Required)** Quantity and location of Crestron devices to be used for contact closure shade control
106		-* **(Required)** Quantity and locations of shade zones to be controlled
107		-* **(Required)** Information associating each shade zone with a relay pair
108		-** 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
109		-** 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		-
111	111	== Draper IntelliFlex I/O A\V Gateway ==
112	112
113	113	(% class="wikigeneratedid" %)
...	...	@@ -123,37 +123,11 @@
123	123	(% class="wikigeneratedid" id="HQuantumRS-232" %)
124	124	RS-232 or TelNet integration supported
125	125
126		-== MechoNet Network Interface (MNI) ==
	110	+== MechoNet Interface (MNI) ==
127	127
128		-(% class="wikigeneratedid" %)
129		-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.
	112	+(% class="wikigeneratedid" id="HMNIRS-232" %)
	113	+Only RS-232 integration supported
130	130
131		-=== Hardware Requirements ===
132		-
133		-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:
134		-
135		-* For RS-232 integration:
136		-** One RS-232 port on the ShowRunnerCLC™ system must be available for each MNI to be integrated
137		-** 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
138		-* For contact closure integration:
139		-** 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**
140		-** 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)
141		-* For RS-485 or IR integration, reach out to Chief Integrations for potentially adding these integrations
142		-
143		-=== Information Requirements ===
144		-
145		-Specific information requirements depend on which method of integration is required:
146		-
147		-* **(Required) **Whether integration is being done through RS-232 or contact closures
148		-* For RS-232 integration:
149		-** **(Required) **MechoNet motors must be addressed in such a way that it is possible to control them per the SOO
150		-*** MechoNet devices are assigned three-part Zone, Group, Node addresses similar to an IPv4 address (e.g. a ZGN address
151		-** **(Required) **MechoNet zone, group, node (ZGN) address for each shade motor to be controlled
152		-** (Required)
153		-* For contact closure integration:
154		-** **(Required)** all information specified in the [[general contact closure>>doc:SHOWRUNNER™ Integrations Guide.Integration Options.Shades Integrations.WebHome||anchor="HInformationRequirements"]] section above
155		-** **(Required)** which shades are controlled by which motor output on each MNI, and which Crestron relays those outputs are expected to correspond to
156		-
157	157	== Mecho SolarTrac4 ==
158	158
159	159	(% class="wikigeneratedid" id="HSolarTrac4BACnet" %)
...	...	@@ -185,5 +185,4 @@
185	185	{{toc/}}
186	186	{{/box}}
187	187	)))
188		-
189		-
	146	+)))