Skip to Content
Last modified by Mark Kohlmann on 2024/11/19 23:23
From version 20.1
edited by Mark Kohlmann
on 2024/08/01 17:36
Change comment: There is no comment for this version
To version 9.1
edited by Scott Kohlmann
on 2023/04/20 21:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mark\.kohlmann@chiefintegrations\.com
1 +XWiki.scott\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,11 +1,6 @@
1 1  (% class="box warningmessage" %)
2 2  (((
3 -Note: Any changes to load hardware/scene quantity 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:
4 -
5 -* "Disconnect signal from Etherenet 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"]]
3 +Note: Any changes to load hardware/scene quantity will require a regeneration of the EISC and will result in signal changes.
9 9  )))
10 10  
11 11  ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
... ... @@ -69,44 +69,6 @@
69 69  ***** Scene Set and Feedback
70 70  *** Devices to be exported are defined in the configuration and are not changeable at run-time.
71 71  
72 -==== Creating Remote Connections through the UI ====
73 -
74 -* Open the Setting (Gear icon in upper right corner) screen from the main page
75 -* Select Crestron Integration
76 -* To add and edit a new connection:
77 -** press the + Add at the bottom left corner of the page
78 -** In the left column select the connection you want to edit
79 -** In the middle column enter:
80 -*** Connection label
81 -*** IP Address of the AV Processor
82 -*** IP ID
83 -** Additional features can be selected:
84 -*** Ignore Fade Times
85 -*** Extended Load Export
86 -*** Extended Scene Export
87 -** EISC Type:
88 -*** Classic (2-Series Compatible)
89 -*** 3-series TCP EISC
90 -** In the right column select all areas needed
91 -** Save by clicking on the Check mark that appears to the right or "Settings:" in the middle column
92 -** Saving will generate an RSD File URL at the bottom of the middle column
93 -*** http:~/~/10.0.0.10/ShowRunner/RSDs/IP-ID0xF1Lighting_Interface.rsd
94 -*** 10.0.0.10 = Lighting system Processor IP Address
95 -*** IP-ID0xF1 = Lighting system Processor IP Table entry for AV integration
96 -** RSD file can also be retrieved from the Toolbox File Manager app
97 -*** Open File Manager
98 -*** Select Internal Flash/HTML/ShowRunner/RSDs
99 -*** all generated RSD files will be available in this folder
100 -
101 -==== Processors with Control Subnets ====
102 -
103 -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:
104 -
105 -* ##securegateway default##
106 -** Enables non-secure connections (CIP on port 41794) from the LAN side
107 -* ##isolatenetworks off##
108 -** Enables communications between the LAN and the Control Subnet, where the actual control processor is located
109 -
110 110  ==== VC-4 Specific Notes ====
111 111  
112 112  ===== Prerequisites =====
... ... @@ -119,98 +119,24 @@
119 119  * EISC created in the ShowRunnerCLC™ config
120 120  * AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4
121 121  
122 -===== ShowRunnerCLC™ Config Settings (Exporting from a ShowRunnerCLC™ VC-4) =====
79 +===== ShowRunnerCLC™ Config Settings =====
123 123  
124 -* Define EiscType in config: ##"EiscType": "EiscServer"##
125 -* Everything else defined as normal
126 -* RSD file will be available in "/opt/crestron/virtualcontrol/RunningPrograms/**[ROOMID]**/Html/ShowRunner/RSDs/"
127 -* When importing the RSD to the AV program, the following steps need to be taken:
128 -** In the configuration tab, right-click the imported EISC and select "Replace"
129 -** Replace the imported RSD with a "VC-4 EISC Client"
130 -** 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
131 -
132 -===== ShowRunnerCLC™ Config Settings (Importing from a third-party VC-4, ShowRunnerCLC™ on Processor) =====
133 -
134 134  * Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
135 -* Define Vc4RoomId in config: ##"Vc4RoomId": "**VC4ROOMID**"##
136 -* IpAddressOrHostname will not be used, instead VCSERVERADDR console command will be used instead
82 +* Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
83 +* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
137 137  
138 138  ===== Processor Settings =====
139 139  
140 -* 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**##
141 -* 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**##
87 +* 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##
88 +* 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##
142 142  * Reboot after entering the above settings
143 143  
144 144  (% class="box warningmessage" %)
145 145  (((
146 -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.
93 +ShowRunnerCLC™ will generate the RSD file as an EISC type, the SIMPL Windows programmer will need to convert the symbol to an //EISC Server//.  At the time of this writing, Crestron does not allow import/export of RSD files for //EISC Client//, //EISC Server,// and //Virtual Control EISC Client// types.
147 147  )))
148 148  
149 149  (% class="box warningmessage" %)
150 150  (((
151 -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.
98 +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.
152 152  )))
153 -
154 -(% class="box errormessage" %)
155 -(((
156 -Crestron Processors cannot use the VirtualControlEiscClient to multiple different VC-4 instances, firmware limitation of VCSERVERADDR command
157 -)))
158 -
159 -(% class="box errormessage" %)
160 -(((
161 -Crestron Processors cannot use multiple Control System Authentication (setcsauthentication) settings, firmware limitation of SETCSAUTHENTICATION command
162 -)))
163 -
164 -==== EISC Settings by Topology ====
165 -
166 -The following table defines the EISC types to use between ShowRunnerCLC™ and an AV program when they are connecting to each other.
167 -
168 -IP Address Requirements:
169 -//EISC Packed// and //3-Series TCP/IP EISC// need both processors to know each other's IP Address.
170 -//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.
171 -
172 -|=EISC Created By|=ShowRunner Host Type|=ShowRunner EISC Type|=AV Processor Host Type|=AV EISC Type
173 -|ShowRunner|Processor|(((
174 -EiscPacked* ~*~*~*~*
175 -
176 -ThreeSeriesEisc*
177 -
178 -EiscServer
179 -)))|Processor|(((
180 -SR Setting //EiscPacked//:
181 -Ethernet Intersystem Communications* ~*~*~*~*
182 -Ethernet Intersystem Communications (Packed)* ~*~*~*~*
183 -\\SR Setting //ThreeSeriesEisc//:
184 -3-Series TCP/IP Ethernet Intersystem Communications*
185 -
186 -SR Settings //EiscServer//:
187 -EISC Client*
188 -)))
189 -|ShowRunner|Processor|EiscServer|VC-4 Room|EISC Client*
190 -|ShowRunner|VC-4 Room|EiscServer|Processor|VC-4 EISC Client* ~*~*
191 -|ShowRunner|VC-4 Room|EiscServer|VC-4 Room|VC-4 EISC Client* ~*~*
192 -|AV Program|Processor|(((
193 -EiscPacked* ~*~*~*~*
194 -
195 -ThreeSeriesEisc*
196 -
197 -EiscServer
198 -)))|Processor|(((
199 -SR Setting //EiscPacked//:
200 -Ethernet Intersystem Communications* ~*~*~*~*
201 -Ethernet Intersystem Communications (Packed)* ~*~*~*~*
202 -\\SR Setting //ThreeSeriesEisc//:
203 -3-Series TCP/IP Ethernet Intersystem Communications*
204 -
205 -SR Settings //EiscServer//:
206 -EISC Client*
207 -)))
208 -|AV Program|Processor|VirtualControlEiscClient* ~*~**|VC-4 Room|EiscServer
209 -|AV Program|VC-4 Room|EiscClient*|Processor|EiscServer
210 -|AV Program|VC-4 Room|VirtualControlEiscClient* ~*~**|VC-4 Room|EiscServer
211 -
212 -Notes:
213 -~* Must configure IP Address of Remote Processor
214 -~** Must configure VC-4 RoomID for connection in symbol definition
215 -~*~*~* Must configure "Vc4RoomId" property in SR Config set to the ROOMID of the remote VC-4 instance
216 -~*~*~** 2-Series processor compatible
MicrosoftTeams-image.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -186.5 KB
Content