Last modified by Mark Kohlmann on 2024/11/19 23:23

From version 17.1
edited by Alexander Mott
on 2023/10/02 15:26
Change comment: There is no comment for this version
To version 8.1
edited by Mark Kohlmann
on 2022/09/30 19:41
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,14 +1,9 @@
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||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 -ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
6 +ShowRunner provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
12 12  
13 13  * EISCs may be Classic, 3-Series, or Server/Client (VC-4) types
14 14  * EISCs can have their IP-ID and IP Address of the remote changed at run-time without a program restart
... ... @@ -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 =====
... ... @@ -113,20 +113,14 @@
113 113  
114 114  * VC-4 server installed
115 115  * Recommended VC-4 server hardened per [[Crestron>>https://support.crestron.com/app/answers/detail/a_id/1001249/kw/harden%20VC-4]]
116 -** Will require SETCSAUTHENTICATION command on processor
73 +** [[​​​​​​​>>https://support.crestron.com/app/answers/detail/a_id/1001249/kw/harden%20VC-4]]Will require SETCSAUTHENTICATION command on processor
117 117  ** VC-4 installer will need to provide username and password for processor to connect, this is used with SETCSAUTHENTICATION
118 -* ShowRunnerCLC™ running on a processor
119 -* EISC created in the ShowRunnerCLC™ config
75 +* showrunner running on a processor
76 +* EISC created in the showrunner 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 +===== showrunner 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 -
128 -===== ShowRunnerCLC™ Config Settings (Importing from a third-party VC-4) =====
129 -
130 130  * Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
131 131  * Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
132 132  * IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
... ... @@ -139,10 +139,10 @@
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.
93 +showrunner 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.
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.
98 +showrunner 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  )))
MicrosoftTeams-image.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -186.5 KB
Content