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 7.2
edited by Alexander Mott
on 2023/12/04 20:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,54 +10,96 @@
10 10  
11 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"
13 +CEN-GWEXERs for the first time, it may be necessary to manually change the connection type from "Auto" to "SSL/TLS". It is also necessary to manually edit the CEN-GWEXER's address book entry so that the connection protocol is "SSL/TLS" when a CEN-GWEXER is added to the address book using Device Discovery tool export.
14 14  
15 15  Whether connected to the CEN-GWEXER via USB or Ethernet, the process to configure the static IP addresses is the same:
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##
17 +* Open Text Console in Toolbox and connect to the CEN-GWEXER
18 +** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect
19 +* Run the following commands to configure the CEN-GWEXER's static IP settings (example is for a **10.0.0.0(% style="color:darkgoldenrod" %)/24(%%)** subnet, with a static IP address of (% style="color:blue" %)**10.0.0.12**(%%), an IP-ID of (% style="color:olive" %)**C1**(%%), and a target processor IP address of (% style="color:orange" %)**10.0.0.10**(%%), and a device hostname of (% style="color:purple" %)**GWEXER-L1**(%%))
20 20  ** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)##
21 21  ** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)##
22 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
23 +** Disable DHCP: ##dhcp off##
24 +** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
25 +** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)##
26 +** Reboot the CEN-GWEXER: ##reboot##
27 +* Repeat for all CEN-GWEXERs on the job
27 27  
28 28  = SSL Setup =
29 29  
30 -Lorem
31 +Crestron devices that support SSL require the use of a secure connection between the processor and the device. In order to establish this secure connection, the processor must have authentication enabled and there must be a user on the processor with "Connects" group permissions.
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
33 +Configure the Connects user on the processor:
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)
35 +* Ensure the processor has [[its IP configured and authentication enabled>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome||anchor="HIPConfiguration"]]
36 +** Verify the processor has authentication enabled by running the command: ##auth## without any parameters
37 +* Create a user by running the following commands, replacing the "username" and "password" with your desired credentials
38 +** ##adduser -N:username -P:password##
39 +** ##addusertogroup -N:username -G:Connects##
40 +* Verify that the user has been created by running the command: ##listusers##
41 +* This process only needs to be performed once per processor on the jobsite
38 38  
43 +Configure the CS authentication on the CEN-GWEXER:
44 +
45 +* Run the following command, replacing the "username" and "password" with the credentials of the Connects user from the previous step
46 +** ##setcsauth -N:username -P:password##
47 +* Repeat this process for every CEN-GWEXER on the jobsite
48 +
39 39  = RF Channel =
40 40  
41 -Lorem
51 +Crestron wireless devices have 16 non-overlapping channels numbered 11-26 to prevent and avoid RF interference either from other appliances in the building (such as microwaves or Wi-Fi routers) or from other Crestron devices that are attempting to communicate with different CEN-GWEXERs.
42 42  
43 -~/~/"RFCHAnnel [#]" set rf channel for gwexer
53 +By default, all CEN-GWEXERs will ship with the same RF channel, so for jobs where interference may be an issue it is necessary to manually change the RF channel of the CEN-GWEXERs. When selecting which RF channel to use for each CEN-GWEXER, it is best to avoid using the same RF channel for any CEN-GWEXERs that are adjacent to each other (whether they are adjacent on the same floor or whether they are adjacent on top of/below each other by virtue of being installed in the same location on different floors). See Crestron's [[RF Products Best Practices guide>>https://www.crestron.com/getmedia/3b3588d1-9356-4d4b-a2df-b3ac1c6fff14/mg_bp_installation_setup_crestron_rf_products]] for more details on RF channel selection.
44 44  
55 +* If using Text Console, run the command: ##rfchannel [#]##
56 +** Replace "[#]" with the desired RF channel
57 +* If using the Gateway Configuration tool:
58 +** Connect to the CEN-GWEXER in another tool such as Text Console
59 +** Navigate to Functions > Gateway Configuration... to open the tool
60 +** At the top left, under "RF Channel", ensure "Fixed" is selected and then choose a channel
61 +** The Gateway Configuration window will become nonresponsive while the RF channel is being applied to the gateway
62 +** Close the tool once the change has been applied
63 +* Once the RF channel has been updated, verify it by running the command: ##rfchannel## without any parameters
64 +
45 45  = Acquiring Devices =
46 46  
67 +(% class="box warningmessage" %)
68 +(((
69 +**When acquiring wireless hardware on jobs with multiple CEN-GWEXERs, it is very important that only one gateway is in acquire mode at a time.** 
70 +Once you are done acquiring devices to one gateway, ensure that you take the gateway out of acquire mode before you begin acquiring devices to the next gateway.
71 +Attempting to acquire devices while multiple gateways are actively in acquire mode may result in wireless hardware being acquired to the incorrect gateway.
72 +)))
73 +
74 +Unlike wired Cresnet devices such as DIN-CENCN-2s or processors which can poll the connected Cresnet and report all devices that are currently connected, CEN-GWEXERs and other wireless gateways must first acquire the wireless Crestron devices. Acquiring wireless Crestron devices involves putting the gateway into acquire mode and then performing a physical button press sequence on each of the wireless devices to be acquired. This process is described in detail below:
75 +
76 +* Put the CEN-GWEXER into acquire mode using one of the methods below:
77 +** If using Text Console, run the command: ##acquire start##
78 +*** Devices will indicate their TSID in the Text Console window as they are acquired
79 +** If using the Gateway Configuration tool:
80 +*** Connect to the CEN-GWEXER in another tool such as Text Console
81 +*** Navigate to Functions > Gateway Configuration... to open the tool
82 +*** At the bottom left, click "Start Acquire"
83 +*** [[image:1701720163760-996.png||height="271" width="316"]]
84 +*** Wait for the confirmation dialog and click "OK" to close the confirmation dialog
85 +*** Previously acquired devices will be displayed with black text, while newly acquired devices will populate with blue text
86 +*** Using the Gateway Configuration tool to acquire hardware may be preferable to using Text Console as acquired devices will report their Serial Number as they are acquired instead of just their TSID
87 +* Acquire all necessary devices to the gateway
88 +** The process for acquiring a wireless device to a gateway varies for each model, but generally the procedure is as follows:
89 +** Press the
90 +* Take the CEN-GWEXER out of acquire mode
91 +** If using Text Console, run the command: ##acquire stop##
92 +** If
93 +*
94 +*
95 +* Once devices have been acquired, use the text console command: reportnetdev to view the network ID
96 +
47 47  ~/~/1-2-3-hold on 4 until all lights blink, then release
48 48  top light will blink slowly a few times and then hold solid or start blinking rapidly
49 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 50  
51 -== Text Console ==
52 -
53 -~/~/"acquire start" and "acquire stop"
54 -
55 55  ~/~/"rep" to show acquired devices
56 56  
57 -== Gateway Configuration Tool ==
58 -
59 -~/~/Connect > functions > gateway configuration for better acquiring tool
60 -
61 61  = Moving/Removing Devices (Unacquiring Devices) =
62 62  
63 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.
1701720163760-996.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,0 +1,1 @@
1 +12.1 KB
Content