Skip to Content
Last modified by Mark Kohlmann on 2024/11/19 23:23
From version 2.1
edited by Mark Kohlmann
on 2021/06/02 21:49
Change comment: There is no comment for this version
To version 13.1
edited by Alexander Mott
on 2023/05/16 16:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Ethernet Intersystem Communications (Crestron)
1 +Ethernet Intersystem Communications Export (Crestron)
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ User Guide & Wiki.SHOWRUNNER™ Appendix.WebHome
1 +SHOWRUNNER™ Integrations Guide.Integration Options.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mark\.kohlmann@chiefintegrations\.com
1 +XWiki.alexander\.mott@chiefintegrations\.com
Content
... ... @@ -1,5 +1,15 @@
1 -ShowRunner provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
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, make sure the appropriate options are selected:
2 2  
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 +
3 3  * EISCs may be Classic, 3-Series, or Server/Client (VC-4) types
4 4  * EISCs can have their IP-ID and IP Address of the remote changed at run-time without a program restart
5 5  * An RSD file will be built for each EISC and a URL will be displayed on the touchscreen to retrieve it
... ... @@ -8,7 +8,96 @@
8 8  *** Provides a standardized interface for controlling areas
9 9  *** Area selection may be changed at run-time
10 10  *** [[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.
11 11  ** Device Export
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.
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 +==== Processors with Control Subnets ====
73 +
74 +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:
75 +
76 +* ##securegateway default##
77 +** Enables non-secure connections (CIP on port 41794) from the LAN side
78 +* ##isolatenetworks off##
79 +** Enables communications between the LAN and the Control Subnet, where the actual control processor is located
80 +
81 +==== VC-4 Specific Notes ====
82 +
83 +===== Prerequisites =====
84 +
85 +* VC-4 server installed
86 +* Recommended VC-4 server hardened per [[Crestron>>https://support.crestron.com/app/answers/detail/a_id/1001249/kw/harden%20VC-4]]
87 +** Will require SETCSAUTHENTICATION command on processor
88 +** VC-4 installer will need to provide username and password for processor to connect, this is used with SETCSAUTHENTICATION
89 +* ShowRunnerCLC™ running on a processor
90 +* EISC created in the ShowRunnerCLC™ config
91 +* AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4
92 +
93 +===== ShowRunnerCLC™ Config Settings =====
94 +
95 +* Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
96 +* Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
97 +* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
98 +
99 +===== Processor Settings =====
100 +
101 +* 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##
102 +* 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##
103 +* Reboot after entering the above settings
104 +
105 +(% class="box warningmessage" %)
106 +(((
107 +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.
108 +)))
109 +
110 +(% class="box warningmessage" %)
111 +(((
112 +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.
113 +)))
MicrosoftTeams-image.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +186.5 KB
Content