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
on 2023/12/04 20:11
Change comment:
There is no comment for this version
To version 1.2
edited by Alexander Mott
on 2023/07/10 14:55
on 2023/07/10 14:55
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,111 +2,28 @@ 2 2 {{toc/}} 3 3 {{/box}} 4 4 5 - CEN-GWEXERs areatwo-way radiofrequency(RF)transceiversthatallowCrestroninfinetEXandExtendedRangewirelessdevicestocommunicatewiththe controlprocessoroverEthernet.TheyareforCrestronwirelesssystemswhat [[DIN-CENCN-2s>>doc:SHOWRUNNER™SetupGuide.SHOWRUNNER™InstallationGuide.SHOWRUNNER™InstallationandNetworkSetup.DIN-CENCN-2Setup.WebHome]]areforwiredCresnetsystems.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 - ForSHOWRUNNER™ installations, theIP address of the CEN-GWEXER doesnot matter as long asits in the same range as the processor and does not conflictwith any other devices on the network. Instead,CEN-GWEXERs are identified tothe processor via their IP-ID. Note that which infinetEX devices are landed atwhich CEN-GWEXER matters, and if devices are moved betweenCEN-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,eachCEN-GWEXER will need tobe initially configured viaUSB (micro USB), unlesstheir MAC addresses are already knownand 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/TLS". It is alsonecessary to manuallyedit 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 +Lorem 14 14 15 - Whether connectedto the CEN-GWEXER via USB or Ethernet, the process to configurethestatic IP addresses is the same:15 +== Sub 2 == 16 16 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 17 +Lorem 28 28 29 -= SSL Setup=19 += Other Notes = 30 30 31 - Crestron devices that support SSLrequire the useof a secureconnection between the processor and the device. In order to establish this secure connection, the processormust have authentication enabled and there must be a user on the processor with "Connects" group permissions.21 +Lorem 32 32 33 - ConfiguretheConnectsuser on the processor:23 +== RF Channel == 34 34 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 25 +Lorem 42 42 43 - Configurethe CSauthenticationon theCEN-GWEXER:27 +== Unacquiring Devices == 44 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 - 49 -= RF Channel = 50 - 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. 52 - 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. 54 - 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 - 65 -= Acquiring Devices = 66 - 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 - 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 -= Moving/Removing Devices (Unacquiring Devices) = 104 - 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. 106 - 107 -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: 108 - 109 -* ##unacquirebytsid [TSID] 0## 110 -* ##unacquirebytsid [TSID] 1## 111 - 112 -Once all of the necessary TSIDs have been unacquired, use the ##reboot## command to reboot the gateway and complete the unacquire process. 29 +Lorem
- 1701720163760-996.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.1 KB - Content