Skip to Content

Changes for page Crestron RF Gateway Setup

Last modified by Alexander Mott on 2025/03/12 17:16
From version 25.1
edited by Alexander Mott
on 2024/12/02 18:53
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
Title
... ... @@ -1,1 +1,1 @@
1 -Crestron RF Gateway Setup
1 +CEN-GWEXER Setup
Hidden
... ... @@ -1,1 +1,1 @@
1 -false
1 +true
Content
... ... @@ -1,27 +5,35 @@
1 -{{warning}}
2 -All RF Gateways require authentication to be configured to connect to the device as well as credentials to be configured for SSL connection with the processor: **the Crestron Agent or Field Tech are responsible for recording these credentials. Chief Integrations provide assistance if the admin credentials are not known. The only way to connect to a device for which the credentials have been lost is to factory reset the device. (% style="color:red" %)All previously acquired devices will need to be re-acquired if the gateway is factory reset.(%%)**​​​​
3 -{{/warning}}
4 -
5 5  {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
6 6  {{toc/}}
7 7  {{/box}}
8 8  
9 -Crestron RF Gateways are a two-way radiofrequency (RF) transceivers that allow Crestron Zūm Wireless (ZUMMESH), infinetEX, or 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 +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.
10 10  
11 -Installations using infinetEX or Extended Range devices require the CEN-GWEXER gateway, while Zūm Wireless installations require the ZUMNET-GATEWAY. Throughout this article, "CEN-GWEXER" and "infinetEX" will be used to refer to the gateway and the wireless devices respectively.
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.
12 12  
13 -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. CEN-GWEXERs will typically have IP-IDs in the "##Cx##" range.
14 -
15 15  = IP Configuration =
16 16  
17 -Typically, each CEN-GWEXER will need to be initially configured via USB (microUSB) unless their MAC addresses are already known and the lighting network has a DHCP server. If the DHCP server on the network is temporary (e.g. DHCP server software running on your computer or a processor utilizing the [[ShowRunner™ DHCP Server>>doc:SHOWRUNNER™ Setup Guide.Troubleshooting Guide.Advanced Tools.DHCP Server.WebHome]]), then static IP addresses must be configured. If the DHCP server is permanent (such as a CP4N or ZUM-HUB4 Control Subnet), then only the IP table needs to be configured for the devices.
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]]).
18 18  
19 -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.
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.
20 20  
21 -== SSL Setup ==
15 +Whether connected to the CEN-GWEXER via USB or Ethernet, the process to configure the static IP addresses is the same:
22 22  
23 -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. The device connecting to the processor must be configured to use these credentials before the processor is added to the IP table, otherwise the device's IP address will be blocked by the processor (see [[our FAQ on how to resolve this>>attach:https://wiki.chiefintegrations.com/FAQ/I%20can%27t%20connect%20to%20my%20processor%20via%20Ethernet]]). **The Crestron Agent or Field Tech are responsible for recording these credentials. **If these Credentials are lost but the admin credentials to the device are known, then new SSL credentials can be set up. **the Crestron Agent or Field Tech are responsible for recording these credentials. Chief Integrations provide assistance if the credentials are not known. The only way to connect to a device for which the credentials have been lost is to factory reset the device, which may require redoing the start-up from scratch. **
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 +** 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 +** 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
24 24  
29 += SSL Setup =
30 +
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.
32 +
25 25  Configure the Connects user on the processor:
26 26  
27 27  * 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"]]
... ... @@ -38,50 +38,6 @@
38 38  ** ##setcsauth -N:username -P:password##
39 39  * Repeat this process for every CEN-GWEXER on the jobsite
40 40  
41 -== DHCP Configuration ==
42 -
43 -(% class="box warningmessage" %)
44 -(((
45 -Be sure to complete the above SSL Setup prior to setting the IP table
46 -)))
47 -
48 -If the lighting network has a permanent DHCP server, then CEN-GWEXERs only require their IP table to be configured, though it is good practice to also record or update their hostname. If the MAC addresses for the CEN-GWEXERs are not known, then the best way to update their configuration is via USB (microUSB). If you are able to identify the CEN-GWEXERs by MAC address, then it is possible to configure these settings via Ethernet using Text Console. Whether connected to the CEN-GWEXER via USB or Ethernet, the process to configure the IP table and hostname is the same:
49 -
50 -* Open Text Console in Toolbox and connect to the CEN-GWEXER
51 -** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect
52 -* Run the following commands to configure the CEN-GWEXER's IP table and hostname (example is for an IP-ID of (% style="color:olive" %)**C1**(%%), and a target processor IP address of (% style="color:orange" %)**172.22.0.1**(%%), and a device hostname of (% style="color:purple" %)**GWEXER-L1**(%%))
53 -** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**172.22.0.1**(%%)##
54 -** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)##
55 -** Reboot the CEN-GWEXER: ##reboot##
56 -* 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]]
57 -* Repeat for all CEN-GWEXERs on the job
58 -
59 -If setup has been done correctly and the ShowRunnerCLC™ program and configuration have already been loaded to the processor, then you should see the CEN-GWEXER's IP-ID reporting online when you run the ##ipt## command on both the CEN-IO and the processor.
60 -
61 -== Static Configuration ==
62 -
63 -(% class="box warningmessage" %)
64 -(((
65 -Be sure to complete the above SSL Setup prior to setting the IP table
66 -)))
67 -
68 -If there is no permanent DHCP server on the lighting network, then CEN-GWEXERs should be configured with static IP addresses via USB (micro USB). If a temporary DHCP server is connected to the lighting network and you are able to identify CEN-GWEXERs by MAC address, then it is possible to configure these settings via Ethernet using Text Console. Whether connected via USB or Ethernet, the process to configure the static IP addresses is the same:
69 -
70 -* Open Text Console in Toolbox and connect to the CEN-GWEXER
71 -** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect
72 -* 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**(%%))
73 -** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)##
74 -** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)##
75 -** Set default gateway: ##defr 0 **10.0.0.1**##
76 -** Disable DHCP: ##dhcp off##
77 -** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
78 -** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)##
79 -** Reboot the CEN-GWEXER: ##reboot##
80 -* 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]]
81 -* Repeat for all CEN-GWEXERs on the job
82 -
83 -If setup has been done correctly and the ShowRunnerCLC™ program and configuration have already been loaded to the processor, then you should see the CEN-GWEXER's IP-ID reporting online when you run the ##ipt## command on both the CEN-IO and the processor.
84 -
85 85  = RF Channel =
86 86  
87 87  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.
... ... @@ -98,7 +98,7 @@
98 98  ** Close the tool once the change has been applied
99 99  * Once the RF channel has been updated, verify it by running the command: ##rfchannel## without any parameters
100 100  
101 -= Acquiring and Addressing Devices =
65 += Acquiring Devices =
102 102  
103 103  (% class="box warningmessage" %)
104 104  (((
... ... @@ -120,25 +120,22 @@
120 120  *** Wait for the confirmation dialog and click "OK" to close the confirmation dialog
121 121  *** Previously acquired devices will be displayed with black text, while newly acquired devices will populate with blue text
122 122  *** 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
123 -* The process for acquiring a wireless device to a gateway varies for each model, but generally the procedure is as follows:
124 -** Press the "setup" button (top button for keypads) in the sequence press-press-press-hold
125 -** Do not release the button until the setup LED (top feedback LED for keypads) begins blinking slowly
126 -*** If the setup LED turns steady, then the device was acquired successfully
127 -*** If the setup LED begins to rapidly blink, then the acquire failed
128 -**** Press the "setup" button again to cancel acquire
129 -**** Attempt to acquire the device again
130 -**** 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.
131 -** Repeat for all wireless devices that need to be acquired to the gateway
132 -* Once all devices have been acquired, take the CEN-GWEXER out of acquire mode:
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
133 133  ** If using Text Console, run the command: ##acquire stop##
134 -** If using the Gateway Configuration tool, click the "STOP Acquire" button in the lower left
135 -* Address devices as indicated in the SHOWRUNNER™ takeoff by either:
136 -** Use Text Console to run the command: ##setrfidbytsid [CID] [TSID]##
137 -*** Replace "[CID]" with the connection ID as indicated in the takeoff
138 -*** Replace "[TSID]" with the 4-byte, hexadecimal TSID of the device to be addressed
139 -** Use Network Device Tree View to select each device and address them individually
140 -* Verify all devices have been acquired and addressed correctly using Network Device Tree View or with the Text Console command: ##reportnetdev##
92 +** If
93 +*
94 +*
95 +* Once devices have been acquired, use the text console command: reportnetdev to view the network ID
141 141  
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 +
142 142  = Moving/Removing Devices (Unacquiring Devices) =
143 143  
144 144  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.