Skip to Content

Changes for page Crestron RF Gateway Setup

Last modified by Alexander Mott on 2025/03/12 17:16
From version 7.2
edited by Alexander Mott
on 2023/12/04 20:11
Change comment: There is no comment for this version
To version 10.1
edited by Alexander Mott
on 2024/02/09 00:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -10,8 +10,24 @@
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/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.
13 +When connecting to a CEN-GWEXER 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 +== DHCP Configuration ==
16 +
17 +If the lighting network is a managed network with a permanent DHCP server (or if it is on the Control Subnet of a CP4N, ZUM-HUB4, or other Crestron processor with a dedicated Control Subnet), then the hardware can be left in DHCP mode and only the IP table and hostname should be updated:
18 +
19 +* Connect to the CEN-GWEXER via Ethernet or USB (process is the same either way)
20 +* Open Text Console in Toolbox and connect to the CEN-GWEXER
21 +** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect
22 +* Run the following commands to configure the CEN-GWEXER's IP table and hostname
23 +** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
24 +** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)##
25 +** Reboot the CEN-GWEXER: ##reboot##
26 +* At this point, it is a good idea to [[update the device firmware>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Updating Firmware.WebHome]]
27 +* Repeat for all CEN-GWEXERs on the job
28 +
29 +== Static Configuration ==
30 +
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 17  * Open Text Console in Toolbox and connect to the CEN-GWEXER
... ... @@ -24,6 +24,7 @@
24 24  ** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
25 25  ** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)##
26 26  ** Reboot the CEN-GWEXER: ##reboot##
43 +* At this point, it is a good idea to [[update the device firmware>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Updating Firmware.WebHome]]
27 27  * Repeat for all CEN-GWEXERs on the job
28 28  
29 29  = SSL Setup =
... ... @@ -62,7 +62,7 @@
62 62  ** Close the tool once the change has been applied
63 63  * Once the RF channel has been updated, verify it by running the command: ##rfchannel## without any parameters
64 64  
65 -= Acquiring Devices =
82 += Acquiring and Addressing Devices =
66 66  
67 67  (% class="box warningmessage" %)
68 68  (((
... ... @@ -84,22 +84,25 @@
84 84  *** Wait for the confirmation dialog and click "OK" to close the confirmation dialog
85 85  *** Previously acquired devices will be displayed with black text, while newly acquired devices will populate with blue text
86 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
104 +* The process for acquiring a wireless device to a gateway varies for each model, but generally the procedure is as follows:
105 +** Press the "setup" button (top button for keypads) in the sequence press-press-press-hold
106 +** Do not release the button until the setup LED (top feedback LED for keypads) begins blinking slowly
107 +*** If the setup LED turns steady, then the device was acquired successfully
108 +*** If the setup LED begins to rapidly blink, then the acquire failed
109 +**** Press the "setup" button again to cancel acquire
110 +**** Attempt to acquire the device again
111 +**** If the device fails to acquire a second time: verify that the correct gateway is in acquire mode, verify that no other gateways are in acquire mode, verify that the desired gateway is close enough to the device that it should be able to acquire, and verify that there are no other sources of RF interference that may be preventing acquisition.
112 +** Repeat for all wireless devices that need to be acquired to the gateway
113 +* Once all devices have been acquired, take the CEN-GWEXER out of acquire mode:
91 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
115 +** If using the Gateway Configuration tool, click the "STOP Acquire" button in the lower left
116 +* Address devices as indicated in the SHOWRUNNER™ takeoff by either:
117 +** Use Text Console to run the command: ##setrfidbytsid [CID] [TSID]##
118 +*** Replace "[CID]" with the connection ID as indicated in the takeoff
119 +*** Replace "[TSID]" with the 4-byte, hexadecimal TSID of the device to be addressed
120 +** Use Network Device Tree View to select each device and address them individually
121 +* Verify all devices have been acquired and addressed correctly using Network Device Tree View or with the Text Console command: ##reportnetdev##
96 96  
97 -~/~/1-2-3-hold on 4 until all lights blink, then release
98 -top light will blink slowly a few times and then hold solid or start blinking rapidly
99 -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
100 -
101 -~/~/"rep" to show acquired devices
102 -
103 103  = Moving/Removing Devices (Unacquiring Devices) =
104 104  
105 105  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.