Skip to Content

Changes for page Crestron RF Gateway Setup

Last modified by Alexander Mott on 2025/03/12 17:16
From version 6.1
edited by Alexander Mott
on 2023/12/04 18:14
Change comment: There is no comment for this version
To version 2.1
edited by Alexander Mott
on 2023/07/10 14:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -CEN-GWEXER Setup
1 +*CEN-GWEXER Setup
Content
... ... @@ -2,69 +2,28 @@
2 2  {{toc/}}
3 3  {{/box}}
4 4  
5 -CEN-GWEXERs are a two-way radiofrequency (RF) transceivers that allow Crestron infinetEX and Extended Range wireless devices to communicate with the control processor over Ethernet. They are for Crestron wireless systems what [[DIN-CENCN-2s>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.DIN-CENCN-2 Setup.WebHome]] are for wired Cresnet systems.
5 +Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
6 6  
7 -For SHOWRUNNER™ installations, the IP address of the CEN-GWEXER does not matter as long as it is in the same range as the processor and does not conflict with any other devices on the network. Instead, CEN-GWEXERs are identified to the processor via their IP-ID. Note that which infinetEX devices are landed at which CEN-GWEXER matters, and if devices are moved between CEN-GWEXERs then the configuration will need to be updated (see below). Chief Integrations typically provides an SRTakeoff.xlsx spreadsheet with an IP Table tab that lists all the CEN-GWEXER IP-IDs in the program. If no takeoff is provided, then the processor's IP table can be checked by running the ##ipt -t ##command from the processor after the configuration is loaded. DIN-CENCN-2's will typically have IP-IDs in the "##Cx##" range.
7 += Initial Connection =
8 8  
9 -= IP Configuration =
9 +Lorem
10 10  
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]]).
11 +== IP Configuration ==
12 12  
13 -CEN-GWEXERs  for the first time, it may be necessary to manually change the connection type from "Auto" to "SSL"
13 +Lorem
14 14  
15 -Whether connected to the CEN-GWEXER via USB or Ethernet, the process to configure the static IP addresses is the same:
15 +== Sub 2 ==
16 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
17 +Lorem
27 27  
28 -= SSL Setup =
19 += Other Notes =
29 29  
30 30  Lorem
31 31  
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
23 +== RF Channel ==
35 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 -
39 -= RF Channel =
40 -
41 41  Lorem
42 42  
43 -~/~/"RFCHAnnel [#]" set rf channel for gwexer
27 +== Unacquiring Devices ==
44 44  
45 -= Acquiring Devices =
46 -
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
50 -
51 -== Text Console ==
52 -
53 -~/~/"acquire start" and "acquire stop"
54 -
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 -
63 -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.
64 -
65 -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:
66 -
67 -* ##unacquirebytsid [TSID] 0##
68 -* ##unacquirebytsid [TSID] 1##
69 -
70 -Once all of the necessary TSIDs have been unacquired, use the ##reboot## command to reboot the gateway and complete the unacquire process.
29 +Lorem