Skip to Content
Last modified by Mark Kohlmann on 2024/11/19 23:23
From version 7.1
edited by Mark Kohlmann
on 2021/12/22 21:36
Change comment: There is no comment for this version
To version 11.1
edited by Alexander Mott
on 2023/05/11 15:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mark\.kohlmann@chiefintegrations\.com
1 +XWiki.alexander\.mott@chiefintegrations\.com
Content
... ... @@ -3,7 +3,7 @@
3 3  Note: Any changes to load hardware/scene quantity will require a regeneration of the EISC and will result in signal changes.
4 4  )))
5 5  
6 -ShowRunner provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
6 +ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
7 7  
8 8  * EISCs may be Classic, 3-Series, or Server/Client (VC-4) types
9 9  * EISCs can have their IP-ID and IP Address of the remote changed at run-time without a program restart
... ... @@ -63,3 +63,46 @@
63 63  **** Area
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 +
67 +==== Processors with Control Subnets ====
68 +
69 +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:
70 +
71 +* ##securegateway default##
72 +** Enables non-secure connections (CIP on port 41794) from the LAN side
73 +* ##isolatenetworks off##
74 +** Enables communications between the LAN and the Control Subnet, where the actual control processor is located
75 +
76 +==== VC-4 Specific Notes ====
77 +
78 +===== Prerequisites =====
79 +
80 +* VC-4 server installed
81 +* Recommended VC-4 server hardened per [[Crestron>>https://support.crestron.com/app/answers/detail/a_id/1001249/kw/harden%20VC-4]]
82 +** Will require SETCSAUTHENTICATION command on processor
83 +** VC-4 installer will need to provide username and password for processor to connect, this is used with SETCSAUTHENTICATION
84 +* ShowRunnerCLC™ running on a processor
85 +* EISC created in the ShowRunnerCLC™ config
86 +* AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4
87 +
88 +===== ShowRunnerCLC™ Config Settings =====
89 +
90 +* Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
91 +* Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
92 +* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
93 +
94 +===== Processor Settings =====
95 +
96 +* 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##
97 +* 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##
98 +* Reboot after entering the above settings
99 +
100 +(% class="box warningmessage" %)
101 +(((
102 +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.
103 +)))
104 +
105 +(% class="box warningmessage" %)
106 +(((
107 +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.
108 +)))