Changes for page Crestron RF Gateway Setup

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -8,26 +8,58 @@
8	8
9	9	= IP Configuration =
10	10
11		-Lorem
	11	+Typically, each CEN-GWEXER will need to be initially configured via USB (micro USB), unless their MAC addresses are already known and the lighting network has a DHCP server (either by running DHCP server software on your computer, or if the processor has a control subnet or is running the [[ShowRunner™ DHCP Server>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]).
12	12
	13	+CEN-GWEXERs  for the first time, it may be necessary to manually change the connection type from "Auto" to "SSL"
	14	+
	15	+Whether connected to the CEN-GWEXER via USB or Ethernet, the process to configure the static IP addresses is the same:
	16	+
	17	+* Open Text Console in Toolbox and connect **to the DIN-CENCN-2**
	18	+* Run the following commands to configure the DIN-CENCN-2's IP settings (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a CENCN-2 IP address of (% style="color:blue" %)**10.0.0.12**(%%), a CENCN-2 IP-ID of (% style="color:olive" %)**D1**(%%), a processor IP address of (% style="color:orange" %)**10.0.0.10**(%%), and a hostname of (% style="color:purple" %)**CENCN-L1**(%%))
	19	+** Disable DHCP: ##dhcp off##
	20	+** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)##
	21	+** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)##
	22	+** Set default gateway: ##defr 0 **10.0.0.1**##
	23	+** Update IP table: ##addm (% style="color:olive" %)**D1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
	24	+** Set hostname: ##host (% style="color:purple" %)**CENCN-L1**(%%)##
	25	+** Reboot the DIN-CENCN-2: ##reboot##
	26	+* Repeat for all DIN-CENCN-2s on the job
	27	+
13	13	= SSL Setup =
14	14
15	15	Lorem
16	16
	32	+~/~/https:~/~/wiki.chiefintegrations.com/SHOWRUNNER%E2%84%A2%20User%20Guide%20%26%20Wiki/SHOWRUNNER%E2%84%A2%20Appendix/SSL%20User%20Configuration/
	33	+SSL setup on proc
	34	+SSL setup on devices
	35	+
	36	+~/~/Need to manually set SSL/TSL method for connecting to gwexer with auth enabled
	37	+- also need to update address book if gwexer are added to address book (defaults to ctp)
	38	+
17	17	= RF Channel =
18	18
19	19	Lorem
20	20
21		-= Useful Commands and Other Notes =
	43	+~/~/"RFCHAnnel [#]" set rf channel for gwexer
22	22
23		-Lorem
	45	+= Acquiring Devices =
24	24
25		-== Acquiring Devices ==
	47	+~/~/1-2-3-hold on 4 until all lights blink, then release
	48	+top light will blink slowly a few times and then hold solid or start blinking rapidly
	49	+if rapid blinking, cancel acquire and make sure that rf gateway is in acquire mode and device is in range then repeat to put device into acquire mode
26	26
27		-Lorem
	51	+== Text Console ==
28	28
29		-== Moving/Removing Devices (Unacquiring Devices) ==
	53	+~/~/"acquire start" and "acquire stop"
30	30
	55	+~/~/"rep" to show acquired devices
	56	+
	57	+== Gateway Configuration Tool ==
	58	+
	59	+~/~/Connect > functions > gateway configuration for better acquiring tool
	60	+
	61	+= Moving/Removing Devices (Unacquiring Devices) =
	62	+
31	31	When a wireless Crestron device is acquired to a new gateway using the typical acquiring process described above, it will automatically forget the previously connected gateway. The gateway itself, however, must manually "forget" the previously connected device before a newly acquired and addressed device will function correctly. This is necessary whether the originally connected device is moved or if the originally corrected device has failed and is being replaced.
32	32
33	33	To unacquire a device from a gateway, it is necessary to run the below commands, replacing "[TSID]" with either the 4-byte hexadecimal TSID of a single device or "all" to forget all previously acquired devices. Devices do not need to be online in order to be acquired (e.g., a failed device can still be unacquired using this method). While only one of these commands needs to be run per device, it is not documented which command (ending in "0" or "1") is required for each model, so it is generally advisable to run both commands for each device to be unacquired: