Skip to Content
Last modified by Mark Kohlmann on 2024/11/19 23:23
From version 9.1
edited by Scott Kohlmann
on 2023/04/20 21:25
Change comment: There is no comment for this version
To version 5.2
edited by Mark Kohlmann
on 2021/07/14 16:24
Change comment: Update document after refactoring.

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.Integration Options.WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.scott\.kohlmann@chiefintegrations\.com
1 +XWiki.mark\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,10 +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.
4 -)))
1 +ShowRunner provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
5 5  
6 -ShowRunnerCLC™ provides Ethernet Intersystem Communications interfaces for integration with 3rd party Crestron systems.
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
10 10  * An RSD file will be built for each EISC and a URL will be displayed on the touchscreen to retrieve it
... ... @@ -62,38 +62,9 @@
62 62  ***** Sensor Reading
63 63  **** Area
64 64  ***** Scene Set and Feedback
65 -*** Devices to be exported are defined in the configuration and are not changeable at run-time.
60 +*** Devices to be exported are defined in the configuration and are not changeable at run-tim
66 66  
67 -==== VC-4 Specific Notes ====
68 -
69 -===== Prerequisites =====
70 -
71 -* VC-4 server installed
72 -* Recommended VC-4 server hardened per [[Crestron>>https://support.crestron.com/app/answers/detail/a_id/1001249/kw/harden%20VC-4]]
73 -** Will require SETCSAUTHENTICATION command on processor
74 -** VC-4 installer will need to provide username and password for processor to connect, this is used with SETCSAUTHENTICATION
75 -* ShowRunnerCLC™ running on a processor
76 -* EISC created in the ShowRunnerCLC™ config
77 -* AV program running on VC-4, AV programmer will need to provide the ROOM ID from VC-4
78 -
79 -===== ShowRunnerCLC™ Config Settings =====
80 -
81 -* Define EiscType in config: ##"EiscType": "VirtualControlEiscClient"##
82 -* Define Vc4RoomId in config: ##"Vc4RoomId": "VC4ROOMID"##
83 -* IpAddressOrHostname will not used, instead VCSERVERADDR will be used instead
84 -
85 -===== Processor Settings =====
86 -
87 -* 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##
88 -* 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##
89 -* Reboot after entering the above settings
90 -
91 91  (% class="box warningmessage" %)
92 92  (((
93 -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.
64 +Note: Any changes to load hardware/scene quantity will require a regeneration of the EISC and will result in signal changes.
94 94  )))
95 -
96 -(% class="box warningmessage" %)
97 -(((
98 -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.
99 -)))