Skip to Content
Last modified by Mark Kohlmann on 2024/11/19 23:23
From version 16.1
edited by Alexander Mott
on 2023/09/28 16:25
Change comment: There is no comment for this version
To version 24.1
edited by Mark Kohlmann
on 2024/11/19 23:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
1 +XWiki.mark\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,16 +1,21 @@
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:
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:
4 4  
5 -* "Disconnect signal from Etherenet ISC symbol in program."
5 +* "Disconnect signal from Ethernet ISC symbol in program."
6 6  * "Change Locally: Update signal name in EISC ISC symbol only."
7 7  
8 -[[image:MicrosoftTeams-image.png||height="413" width="394"]]
8 +[[image:MicrosoftTeams-image.png||queryString="width=394&height=413" height="413" width="394"]]
9 9  )))
10 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 +
11 11  ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
12 12  
13 -* EISCs may be Classic, 3-Series, or Server/Client (VC-4) types
18 +* EISCs may be Classic, 3-Series, or Server/Client types
14 14  * EISCs can have their IP-ID and IP Address of the remote changed at run-time without a program restart
15 15  * An RSD file will be built for each EISC and a URL will be displayed on the touchscreen to retrieve it
16 16  * There are 2 EISC modes and only one mode is supported on an EISC definition, multiple EISCs may be defined
... ... @@ -123,26 +123,94 @@
123 123  
124 124  * Define EiscType in config: ##"EiscType": "EiscServer"##
125 125  * Everything else defined as normal
126 -* RSD file will be available in "/opt/crestron/virtualcontrol/RunningPrograms/**[ROOMID]**/Html"
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
127 127  
128 -===== ShowRunnerCLC™ Config Settings (Importing from a third-party VC-4) =====
137 +===== ShowRunnerCLC™ Config Settings (Importing from a third-party VC-4, ShowRunnerCLC™ on Processor) =====
129 129  
130 130  * Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
131 -* Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
132 -* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
140 +* Define Vc4RoomId in config: ##"Vc4RoomId": "**VC4ROOMID**"##
141 +* IpAddressOrHostname will not be used, instead VCSERVERADDR console command will be used instead
133 133  
134 134  ===== Processor Settings =====
135 135  
136 -* 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##
137 -* 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##
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**##
138 138  * Reboot after entering the above settings
139 139  
140 140  (% class="box warningmessage" %)
141 141  (((
142 -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.
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.
143 143  )))
144 144  
145 145  (% class="box warningmessage" %)
146 146  (((
147 -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.
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.
148 148  )))
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