Changes for page Ethernet Intersystem Communications Export (Crestron)
Last modified by Mark Kohlmann on 2024/11/19 23:23
From 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
To version 15.2
edited by Alexander Mott
on 2023/09/28 16:12
on 2023/09/28 16:12
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,6 +1,11 @@ 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. 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"]] 4 4 ))) 5 5 6 6 ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems. ... ... @@ -64,13 +64,41 @@ 64 64 ***** Scene Set and Feedback 65 65 *** Devices to be exported are defined in the configuration and are not changeable at run-time. 66 66 67 -(% class="wikigeneratedid" %) 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 + 68 68 ==== Processors with Control Subnets ==== 69 69 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. Thesecommandsethe samefor both3-Series and4-Series processors: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: 71 71 72 72 * ##securegateway default## 73 -** Enables non-secure connections (CIP on port 41794) from the LAN side instead of requiring a secure connection (SCIP on port 41796)106 +** Enables non-secure connections (CIP on port 41794) from the LAN side 74 74 * ##isolatenetworks off## 75 75 ** Enables communications between the LAN and the Control Subnet, where the actual control processor is located 76 76 ... ... @@ -86,8 +86,13 @@ 86 86 * EISC created in the ShowRunnerCLC™ config 87 87 * AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4 88 88 89 -===== ShowRunnerCLC™ Config Settings ===== 122 +===== ShowRunnerCLC™ Config Settings (Exporting from a ShowRunnerCLC™ VC-4) ===== 90 90 124 +* Define EiscType in config: ##"EiscType": "EiscServer"## 125 +* Everything else defined as normal 126 + 127 +===== ShowRunnerCLC™ Config Settings (Importing from a third-party VC-4) ===== 128 + 91 91 * Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"## 92 92 * Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"## 93 93 * IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
- MicrosoftTeams-image.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,0 +1,1 @@ 1 +186.5 KB - Content