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 10.1
edited by Alexander Mott
on 2023/05/11 15:30
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,10 @@
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.
4 +)))
2 2  
6 +ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
7 +
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,97 @@
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]]
16 +*** Signals Provided per Area (signals vary by Area settings/configuration):
17 +**** Area Name
18 +**** Occupied
19 +**** Occupancy Enable/Disable
20 +**** Color Temp Auto
21 +**** Color Temp Manual Set and Feedback
22 +**** Area Master Raise/Lower
23 +**** Save Current Scene
24 +**** Recall Scene # and Current Scene Feedback
25 +**** Extended Scene Export option set
26 +***** Scene Count
27 +***** Scene Names
28 +**** Load Count
29 +**** Load Level Analogs
30 +**** Load Names
31 +**** Extended Load Export option set
32 +***** CCT Load type: Color Temp
33 +***** RGB[A|W]: Individual Color Channels
34 +**** Shade Count
35 +**** All Shade Open/Close
36 +**** Shade Name
37 +**** Shade Open/Close/Stop
38 +**** Ignore Fade Times option set
39 +***** 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.
41 +*** Exports devices with specific signals for each device type
42 +**** Occupancy Sensor
43 +***** Occupied
44 +***** Online Feedback
45 +**** Keyswitch
46 +***** Active Feedback
47 +**** Partition Sensor
48 +***** Combined Feedback
49 +**** Keypad
50 +***** Enable/Disable w/ Feedback
51 +***** Button Press Event
52 +***** Button Feedback Setting
53 +***** Extended Keypad Export option set
54 +****** Button Tap/Double Tap/Held Events
55 +**** Global Actions
56 +***** Activate
57 +**** Shade
58 +***** Open/Close/Stop
59 +**** Load
60 +***** Level Set and Feedback
61 +**** Photocell
62 +***** Sensor Reading
63 +**** Area
64 +***** Scene Set and Feedback
65 +*** Devices to be exported are defined in the configuration and are not changeable at run-time.
66 +
67 +(% class="wikigeneratedid" %)
68 +==== Processors with Control Subnets ====
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. These commands are the same for both 3-Series and 4-Series processors:
71 +
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)
74 +* ##isolatenetworks off##
75 +** Enables communications between the LAN and the Control Subnet, where the actual control processor is located
76 +
77 +==== VC-4 Specific Notes ====
78 +
79 +===== Prerequisites =====
80 +
81 +* VC-4 server installed
82 +* Recommended VC-4 server hardened per [[Crestron>>https://support.crestron.com/app/answers/detail/a_id/1001249/kw/harden%20VC-4]]
83 +** Will require SETCSAUTHENTICATION command on processor
84 +** VC-4 installer will need to provide username and password for processor to connect, this is used with SETCSAUTHENTICATION
85 +* ShowRunnerCLC™ running on a processor
86 +* EISC created in the ShowRunnerCLC™ config
87 +* AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4
88 +
89 +===== ShowRunnerCLC™ Config Settings =====
90 +
91 +* Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
92 +* Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
93 +* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
94 +
95 +===== Processor Settings =====
96 +
97 +* 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##
98 +* 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##
99 +* Reboot after entering the above settings
100 +
101 +(% class="box warningmessage" %)
102 +(((
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.
104 +)))
105 +
106 +(% class="box warningmessage" %)
107 +(((
108 +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.
109 +)))