Changes for page Ethernet Intersystem Communications Export (Crestron)
Last modified by Mark Kohlmann on 2024/11/19 23:23
From version 19.1
edited by Alexander Mott
on 2023/12/15 20:24
on 2023/12/15 20:24
Change comment:
There is no comment for this version
To version 10.1
edited by Alexander Mott
on 2023/05/11 15:30
on 2023/05/11 15:30
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- 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||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,41 +69,13 @@ 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 - 67 +(% class="wikigeneratedid" %) 101 101 ==== Processors with Control Subnets ==== 102 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 isnecessaryto eithersetupCWSusers and enable a secure(SCIP onport 41796) EISCor run thefollowing commands:70 +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. These commands are the same for both 3-Series and 4-Series processors: 104 104 105 105 * ##securegateway default## 106 -** Enables non-secure connections (CIP on port 41794) from the LAN side 73 +** Enables non-secure connections (CIP on port 41794) from the LAN side instead of requiring a secure connection (SCIP on port 41796) 107 107 * ##isolatenetworks off## 108 108 ** Enables communications between the LAN and the Control Subnet, where the actual control processor is located 109 109 ... ... @@ -119,21 +119,11 @@ 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)=====89 +===== 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 135 * Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"## 136 -* IpAddressOrHostname will not beused, instead VCSERVERADDRconsole commandwill be used instead93 +* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead 137 137 138 138 ===== Processor Settings ===== 139 139 ... ... @@ -143,7 +143,7 @@ 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 thecorrecttype. At the time of this writing, Crestron does not allow import/export of RSD files for //EISC Client//, //EISC Server,// and //VC-4EISC Client// types.103 +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" %)
- MicrosoftTeams-image.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -186.5 KB - Content