Changes for page Crestron RF Gateway Setup
Last modified by Alexander Mott on 2025/03/12 17:16
From version 12.1
edited by Alexander Mott
on 2024/02/09 00:39
on 2024/02/09 00:39
Change comment:
There is no comment for this version
To version 5.1
edited by Alexander Mott
on 2023/12/04 17:41
on 2023/12/04 17:41
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
-
... ... @@ -8,117 +8,40 @@ 8 8 9 9 = IP Configuration = 10 10 11 - Typically, each CEN-GWEXER will need tobe initially configured via USB (micro USB) 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 +Lorem 12 12 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 - 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 - 31 -If there is no permanent DHCP server on the lighting network, then CEN-GWEXERs should be configured with static IP addresses. If a temporary DHCP server is connected to the lighting network and the CEN-GWEXER MAC addresses are known, then the devices can be set up via Ethernet from one location, otherwise they will need to be set up via USB. Whether connected to the CEN-GWEXER via USB or Ethernet, the process to configure the static IP addresses is the same: 32 - 33 -* Open Text Console in Toolbox and connect to the CEN-GWEXER 34 -** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect 35 -* 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**(%%)) 36 -** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)## 37 -** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)## 38 -** Set default gateway: ##defr 0 **10.0.0.1**## 39 -** Disable DHCP: ##dhcp off## 40 -** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)## 41 -** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)## 42 -** 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]] 44 -* Repeat for all CEN-GWEXERs on the job 45 - 46 46 = SSL Setup = 47 47 48 - 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.15 +Lorem 49 49 50 -Configure the Connects user on the processor: 17 +~/~/https:~/~/wiki.chiefintegrations.com/SHOWRUNNER%E2%84%A2%20User%20Guide%20%26%20Wiki/SHOWRUNNER%E2%84%A2%20Appendix/SSL%20User%20Configuration/ 18 +SSL setup on proc 19 +SSL setup on devices 51 51 52 -* 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"]] 53 -** Verify the processor has authentication enabled by running the command: ##auth## without any parameters 54 -* Create a user by running the following commands, replacing the "username" and "password" with your desired credentials 55 -** ##adduser -N:username -P:password## 56 -** ##addusertogroup -N:username -G:Connects## 57 -* Verify that the user has been created by running the command: ##listusers## 58 -* This process only needs to be performed once per processor on the jobsite 21 +~/~/Need to manually set SSL/TSL method for connecting to gwexer with auth enabled 22 +- also need to update address book if gwexer are added to address book (defaults to ctp) 59 59 60 - ConfiguretheCS authenticationontheCEN-GWEXER:24 += RF Channel = 61 61 62 -* Run the following command, replacing the "username" and "password" with the credentials of the Connects user from the previous step 63 -** ##setcsauth -N:username -P:password## 64 -* Repeat this process for every CEN-GWEXER on the jobsite 26 +Lorem 65 65 66 - =RF=28 +~/~/"RFCHAnnel [#]" set rf channel for gwexer 67 67 68 - Crestronwireless 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 devicesthat are attempting to communicate with different CEN-GWEXERs.30 += Acquiring Devices = 69 69 70 -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. 32 +~/~/1-2-3-hold on 4 until all lights blink, then release 33 +top light will blink slowly a few times and then hold solid or start blinking rapidly 34 +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 71 71 72 -* If using Text Console, run the command: ##rfchannel [#]## 73 -** Replace "[#]" with the desired RF channel 74 -* If using the Gateway Configuration tool: 75 -** Connect to the CEN-GWEXER in another tool such as Text Console 76 -** Navigate to Functions > Gateway Configuration... to open the tool 77 -** At the top left, under "RF Channel", ensure "Fixed" is selected and then choose a channel 78 -** The Gateway Configuration window will become nonresponsive while the RF channel is being applied to the gateway 79 -** Close the tool once the change has been applied 80 -* Once the RF channel has been updated, verify it by running the command: ##rfchannel## without any parameters 36 +== Text Console == 81 81 82 - = AcquiringandAddressingDevices=38 +~/~/"acquire start" and "acquire stop" 83 83 84 -(% class="box warningmessage" %) 85 -((( 86 -**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.** 87 -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. 88 -Attempting to acquire devices while multiple gateways are actively in acquire mode may result in wireless hardware being acquired to the incorrect gateway. 89 -))) 40 +~/~/"rep" to show acquired devices 90 90 91 - Unlikewired Cresnet devices such as DIN-CENCN-2s or processors which can poll the connected Cresnet and report all devices that are currently connected, CEN-GWEXERsand otherwireless gatewaysmust first acquire the wirelessCrestrondevices. Acquiringwireless Crestron devices involves putting the gateway into acquire modeandthen performing a physical buttonpress sequenceon eachof the wirelessdevices to be acquired. This process is described in detail below:42 +== Gateway Configuration Tool == 92 92 93 -* Put the CEN-GWEXER into acquire mode using one of the methods below: 94 -** If using Text Console, run the command: ##acquire start## 95 -*** Devices will indicate their TSID in the Text Console window as they are acquired 96 -** If using the Gateway Configuration tool: 97 -*** Connect to the CEN-GWEXER in another tool such as Text Console 98 -*** Navigate to Functions > Gateway Configuration... to open the tool 99 -*** At the bottom left, click "Start Acquire" 100 -*** [[image:1701720163760-996.png||height="271" width="316"]] 101 -*** Wait for the confirmation dialog and click "OK" to close the confirmation dialog 102 -*** Previously acquired devices will be displayed with black text, while newly acquired devices will populate with blue text 103 -*** 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 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: 114 -** If using Text Console, run the command: ##acquire stop## 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## 44 +~/~/Connect > functions > gateway configuration for better acquiring tool 122 122 123 123 = Moving/Removing Devices (Unacquiring Devices) = 124 124
- 1701720163760-996.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.alexander\.mott@chiefintegrations\.com - Size
-
... ... @@ -1,1 +1,0 @@ 1 -12.1 KB - Content