Skip to Content
Last modified by Mark Kohlmann on 2024/11/19 23:23
From version 23.1
edited by Mark Kohlmann
on 2024/11/19 23:22
Change comment: There is no comment for this version
To version 1.1
edited by Mark Kohlmann
on 2021/06/02 21:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Ethernet Intersystem Communications xport (Crestron)
1 +Ethernet Intersystem Communications (Crestron)
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ Integrations Guide.Integration Options.WebHome
1 +SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Appendix.WebHome
Content
... ... @@ -1,221 +1,13 @@
1 -(% class="box warningmessage" %)
2 -(((
3 -Note: For AV Integration EISCs, any changes to load or shade/shade group quantity, ExtendedSceneExport, or ExtendedLoadExport settings will require a regeneration of the EISC and will result in signal changes. When importing a new or updated RSD file to the A/V program, ensure the appropriate options are selected:
1 +ShowRunner provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
4 4  
5 -* "Disconnect signal from Ethernet ISC symbol in program."
6 -* "Change Locally: Update signal name in EISC ISC symbol only."
7 -
8 -[[image:MicrosoftTeams-image.png||queryString="width=394&height=413" height="413" width="394"]]
9 -)))
10 -
11 -(% class="box errormessage" %)
12 -(((
13 -Chief Integrations does not recommend using the 3-Series TCP/IP Ethernet Intersystem Communications (ThreeSeriesEisc).  We have reports of this type locking up SIMPL Windows programs attempting to integrate with showrunner™ on 4-series processors.  3-Series EISCs try to negotiate who is the server and who is the client.  Use the table below for recommendations on EISC types.
14 -)))
15 -
16 -ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
17 -
18 -* EISCs may be Classic, 3-Series, or Server/Client types
3 +* EISCs may be Classic, 3-Series, or Server/Client (VC-4) types
19 19  * EISCs can have their IP-ID and IP Address of the remote changed at run-time without a program restart
20 20  * An RSD file will be built for each EISC and a URL will be displayed on the touchscreen to retrieve it
21 21  * There are 2 EISC modes and only one mode is supported on an EISC definition, multiple EISCs may be defined
22 22  ** AV Integration
23 23  *** Provides a standardized interface for controlling areas
24 -*** Area selection may be changed at run-time
25 -*** [[AV Integration Demo>>url:https://files.chiefintegrations.com/s/Di4aypEKX7APn8n]]
26 -*** Signals Provided per Area (signals vary by Area settings/configuration):
27 -**** Area Name
28 -**** Occupied
29 -**** Occupancy Enable/Disable
30 -**** Color Temp Auto
31 -**** Color Temp Manual Set and Feedback
32 -**** Area Master Raise/Lower
33 -**** Save Current Scene
34 -**** Recall Scene # and Current Scene Feedback
35 -**** Extended Scene Export option set
36 -***** Scene Count
37 -***** Scene Names
38 -**** Load Count
39 -**** Load Level Analogs
40 -**** Load Names
41 -**** Extended Load Export option set
42 -***** CCT Load type: Color Temp
43 -***** RGB[A|W]: Individual Color Channels
44 -**** Shade Count
45 -**** All Shade Open/Close
46 -**** Shade Name
47 -**** Shade Open/Close/Stop
48 -**** Ignore Fade Times option set
49 -***** Fade Times are not sent out, only final value.  Reduces traffic.
9 +*** Areas may be selected at run-time
10 +***
50 50  ** Device Export
51 -*** Exports devices with specific signals for each device type
52 -**** Occupancy Sensor
53 -***** Occupied
54 -***** Online Feedback
55 -**** Keyswitch
56 -***** Active Feedback
57 -**** Partition Sensor
58 -***** Combined Feedback
59 -**** Keypad
60 -***** Enable/Disable w/ Feedback
61 -***** Button Press Event
62 -***** Button Feedback Setting
63 -***** Extended Keypad Export option set
64 -****** Button Tap/Double Tap/Held Events
65 -**** Global Actions
66 -***** Activate
67 -**** Shade
68 -***** Open/Close/Stop
69 -**** Load
70 -***** Level Set and Feedback
71 -**** Photocell
72 -***** Sensor Reading
73 -**** Area
74 -***** Scene Set and Feedback
75 -*** Devices to be exported are defined in the configuration and are not changeable at run-time.
76 -
77 -==== Creating Remote Connections through the UI ====
78 -
79 -* Open the Setting (Gear icon in upper right corner) screen from the main page
80 -* Select Crestron Integration
81 -* To add and edit a new connection:
82 -** press the + Add at the bottom left corner of the page
83 -** In the left column select the connection you want to edit
84 -** In the middle column enter:
85 -*** Connection label
86 -*** IP Address of the AV Processor
87 -*** IP ID
88 -** Additional features can be selected:
89 -*** Ignore Fade Times
90 -*** Extended Load Export
91 -*** Extended Scene Export
92 -** EISC Type:
93 -*** Classic (2-Series Compatible)
94 -*** 3-series TCP EISC
95 -** In the right column select all areas needed
96 -** Save by clicking on the Check mark that appears to the right or "Settings:" in the middle column
97 -** Saving will generate an RSD File URL at the bottom of the middle column
98 -*** http:~/~/10.0.0.10/ShowRunner/RSDs/IP-ID0xF1Lighting_Interface.rsd
99 -*** 10.0.0.10 = Lighting system Processor IP Address
100 -*** IP-ID0xF1 = Lighting system Processor IP Table entry for AV integration
101 -** RSD file can also be retrieved from the Toolbox File Manager app
102 -*** Open File Manager
103 -*** Select Internal Flash/HTML/ShowRunner/RSDs
104 -*** all generated RSD files will be available in this folder
105 -
106 -==== Processors with Control Subnets ====
107 -
108 -When integrating a 3-Series EISC with a processor that has both a LAN port and a Control Subnet using a connection over the LAN, there are some additional settings that need to be enabled in order for the integration to work correctly. It is necessary to either set up CWS users and enable a secure (SCIP on port 41796) EISC or run the following commands:
109 -
110 -* ##securegateway default##
111 -** Enables non-secure connections (CIP on port 41794) from the LAN side
112 -* ##isolatenetworks off##
113 -** Enables communications between the LAN and the Control Subnet, where the actual control processor is located
114 -
115 -==== VC-4 Specific Notes ====
116 -
117 -===== Prerequisites =====
118 -
119 -* VC-4 server installed
120 -* Recommended VC-4 server hardened per [[Crestron>>https://support.crestron.com/app/answers/detail/a_id/1001249/kw/harden%20VC-4]]
121 -** Will require SETCSAUTHENTICATION command on processor
122 -** VC-4 installer will need to provide username and password for processor to connect, this is used with SETCSAUTHENTICATION
123 -* ShowRunnerCLC™ running on a processor
124 -* EISC created in the ShowRunnerCLC™ config
125 -* AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4
126 -
127 -===== ShowRunnerCLC™ Config Settings (Exporting from a ShowRunnerCLC™ VC-4) =====
128 -
129 -* Define EiscType in config: ##"EiscType": "EiscServer"##
130 -* Everything else defined as normal
131 -* RSD file will be available in "/opt/crestron/virtualcontrol/RunningPrograms/**[ROOMID]**/Html/ShowRunner/RSDs/"
132 -* When importing the RSD to the AV program, the following steps need to be taken:
133 -** In the configuration tab, right-click the imported EISC and select "Replace"
134 -** Replace the imported RSD with a "VC-4 EISC Client"
135 -** In the device settings for the VC-4 EISC Client, under the IP Net Address tab, add the Room ID for the ShowRunnerCLC™ program on the VC-4
136 -
137 -===== ShowRunnerCLC™ Config Settings (Importing from a third-party VC-4, ShowRunnerCLC™ on Processor) =====
138 -
139 -* Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
140 -* Define Vc4RoomId in config: ##"Vc4RoomId": "**VC4ROOMID**"##
141 -* IpAddressOrHostname will not be used, instead VCSERVERADDR console command will be used instead
142 -
143 -===== Processor Settings =====
144 -
145 -* Use console command VCSERVERADDR (or processor configuration pages) to add the VC-4 server IP address or hostname. Example: ##VCSERVERADDR **my-vc-4-server.mycorpnet.com**##
146 -* If security (hardening) is enabled use console command SETCSAUTHENTICATION to enroll the credentials used to login to VC-4. Example: ##SETCSAUTHENTICATION -n:**vc4user** -p:**vc4password**##
147 -* Reboot after entering the above settings
148 -
149 -(% class="box warningmessage" %)
150 -(((
151 -ShowRunnerCLC™ will generate the RSD file as an EISC type, the SIMPL Windows programmer will need to convert the symbol to the correct type. At the time of this writing, Crestron does not allow import/export of RSD files for //EISC Client//, //EISC Server,// and //VC-4 EISC Client// types.
152 -)))
153 -
154 -(% class="box warningmessage" %)
155 -(((
156 -ShowRunnerCLC™ uses analog join 4001 on normal EISCs to confirm the logic is fully online.  Join 4001 is not available on //EISC Client//, //EISC Server,// and //Virtual Control EISC Client// types so 4000 is used instead.
157 -)))
158 -
159 -(% class="box errormessage" %)
160 -(((
161 -Crestron Processors cannot use the VirtualControlEiscClient to multiple different VC-4 instances, firmware limitation of VCSERVERADDR command
162 -)))
163 -
164 -(% class="box errormessage" %)
165 -(((
166 -Crestron Processors cannot use multiple Control System Authentication (setcsauthentication) settings, firmware limitation of SETCSAUTHENTICATION command
167 -)))
168 -
169 -==== EISC Settings by Topology ====
170 -
171 -The following table defines the EISC types to use between ShowRunnerCLC™ and an AV program when they are connecting to each other.
172 -
173 -IP Address Requirements:
174 -//EISC Packed// and //3-Series TCP/IP EISC// need both processors to know each other's IP Address.
175 -//EISC Server// accepts EISC connections from an //EISC Client// or a //VC-4 EISC Client.//  Only the EISC Client side must know the IP address of the EISC Server.
176 -
177 -|=EISC Created By|=ShowRunner Host Type|=ShowRunner EISC Type|=AV Processor Host Type|=AV EISC Type
178 -|ShowRunner|Processor|(((
179 -EiscPacked* ~*~*~*~*
180 -
181 -ThreeSeriesEisc*
182 -
183 -EiscServer
184 -)))|Processor|(((
185 -SR Setting //EiscPacked//:
186 -Ethernet Intersystem Communications* ~*~*~*~*
187 -Ethernet Intersystem Communications (Packed)* ~*~*~*~*
188 -\\SR Setting //ThreeSeriesEisc//:
189 -3-Series TCP/IP Ethernet Intersystem Communications*
190 -
191 -SR Settings //EiscServer//:
192 -EISC Client*
193 -)))
194 -|ShowRunner|Processor|EiscServer|VC-4 Room|EISC Client*
195 -|ShowRunner|VC-4 Room|EiscServer|Processor|VC-4 EISC Client* ~*~*
196 -|ShowRunner|VC-4 Room|EiscServer|VC-4 Room|VC-4 EISC Client* ~*~*
197 -|AV Program|Processor|(((
198 -EiscPacked* ~*~*~*~*
199 -
200 -ThreeSeriesEisc*
201 -
202 -EiscServer
203 -)))|Processor|(((
204 -SR Setting //EiscPacked//:
205 -Ethernet Intersystem Communications* ~*~*~*~*
206 -Ethernet Intersystem Communications (Packed)* ~*~*~*~*
207 -\\SR Setting //ThreeSeriesEisc//:
208 -3-Series TCP/IP Ethernet Intersystem Communications*
209 -
210 -SR Settings //EiscServer//:
211 -EISC Client*
212 -)))
213 -|AV Program|Processor|VirtualControlEiscClient* ~*~**|VC-4 Room|EiscServer
214 -|AV Program|VC-4 Room|EiscClient*|Processor|EiscServer
215 -|AV Program|VC-4 Room|VirtualControlEiscClient* ~*~**|VC-4 Room|EiscServer
216 -
217 -Notes:
218 -~* Must configure IP Address of Remote Processor
219 -~** Must configure VC-4 RoomID for connection in symbol definition
220 -~*~*~* Must configure "Vc4RoomId" property in SR Config set to the ROOMID of the remote VC-4 instance
221 -~*~*~** 2-Series processor compatible
12 +*** Exports devices with specific parameters for each device type
13 +*** Devices to be exported are defined in the configuration
MicrosoftTeams-image.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -186.5 KB
Content