Skip to Content
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 2.1
edited by Mark Kohlmann
on 2021/06/02 21:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Ethernet Intersystem Communications Export (Crestron)
1 +Ethernet Intersystem Communications (Crestron)
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ Integrations Guide.Integration Options.WebHome
1 +SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Appendix.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
1 +XWiki.mark\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,15 +1,5 @@
1 -(% class="box warningmessage" %)
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:
1 +ShowRunner provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
4 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"]]
9 -)))
10 -
11 -ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
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
15 15  * An RSD file will be built for each EISC and a URL will be displayed on the touchscreen to retrieve it
... ... @@ -18,131 +18,7 @@
18 18  *** Provides a standardized interface for controlling areas
19 19  *** Area selection may be changed at run-time
20 20  *** [[AV Integration Demo>>url:https://files.chiefintegrations.com/s/Di4aypEKX7APn8n]]
21 -*** Signals Provided per Area (signals vary by Area settings/configuration):
22 -**** Area Name
23 -**** Occupied
24 -**** Occupancy Enable/Disable
25 -**** Color Temp Auto
26 -**** Color Temp Manual Set and Feedback
27 -**** Area Master Raise/Lower
28 -**** Save Current Scene
29 -**** Recall Scene # and Current Scene Feedback
30 -**** Extended Scene Export option set
31 -***** Scene Count
32 -***** Scene Names
33 -**** Load Count
34 -**** Load Level Analogs
35 -**** Load Names
36 -**** Extended Load Export option set
37 -***** CCT Load type: Color Temp
38 -***** RGB[A|W]: Individual Color Channels
39 -**** Shade Count
40 -**** All Shade Open/Close
41 -**** Shade Name
42 -**** Shade Open/Close/Stop
43 -**** Ignore Fade Times option set
44 -***** Fade Times are not sent out, only final value.  Reduces traffic.
45 45  ** Device Export
46 -*** Exports devices with specific signals for each device type
47 -**** Occupancy Sensor
48 -***** Occupied
49 -***** Online Feedback
50 -**** Keyswitch
51 -***** Active Feedback
52 -**** Partition Sensor
53 -***** Combined Feedback
54 -**** Keypad
55 -***** Enable/Disable w/ Feedback
56 -***** Button Press Event
57 -***** Button Feedback Setting
58 -***** Extended Keypad Export option set
59 -****** Button Tap/Double Tap/Held Events
60 -**** Global Actions
61 -***** Activate
62 -**** Shade
63 -***** Open/Close/Stop
64 -**** Load
65 -***** Level Set and Feedback
66 -**** Photocell
67 -***** Sensor Reading
68 -**** Area
69 -***** Scene Set and Feedback
70 -*** Devices to be exported are defined in the configuration and are not changeable at run-time.
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 -==== VC-4 Specific Notes ====
111 -
112 -===== Prerequisites =====
113 -
114 -* VC-4 server installed
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
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
120 -* AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4
121 -
122 -===== ShowRunnerCLC™ Config Settings (Exporting from a ShowRunnerCLC™ VC-4) =====
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 -* Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
131 -* Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
132 -* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
133 -
134 -===== Processor Settings =====
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##
138 -* Reboot after entering the above settings
139 -
140 -(% class="box warningmessage" %)
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.
143 -)))
144 -
145 -(% class="box warningmessage" %)
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.
148 -)))
12 +*** Exports devices with specific parameters for each device type
13 +*** Devices to be exported are defined in the configuration and are not changeable at run-time
14 +* Any changes to load hardware/scene quantity will require a regeneration of the EISC and will result in signal changes.
MicrosoftTeams-image.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -186.5 KB
Content