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 19.1
edited by Alexander Mott
on 2024/02/16 20:14
on 2024/02/16 20:14
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Hidden
-
... ... @@ -1,1 +1,1 @@ 1 - true1 +false - Content
-
... ... @@ -8,26 +8,12 @@ 8 8 9 9 = IP Configuration = 10 10 11 -Typically, each CEN-GWEXER will need to be initially configured via USB (micro ,unless their MAC addresses are already known and the lighting network has a DHCP server(eitherbyrunningDHCP server software on your computer,oriftheprocessorhas a control subnetoris running11 +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. 12 12 13 -CEN-GWEXER sfor 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 - Whether connectedto the CEN-GWEXER via USBor Ethernet, theprocessto configure the static IP addresses is the same:15 +== SSL Setup == 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 28 - 29 -= SSL Setup = 30 - 31 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 32 33 33 Configure the Connects user on the processor: ... ... @@ -46,6 +46,36 @@ 46 46 ** ##setcsauth -N:username -P:password## 47 47 * Repeat this process for every CEN-GWEXER on the jobsite 48 48 35 +== DHCP Configuration == 36 + 37 +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: 38 + 39 +* Open Text Console in Toolbox and connect to the CEN-GWEXER 40 +** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect 41 +* 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**(%%)) 42 +** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**172.22.0.1**(%%)## 43 +** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)## 44 +** Reboot the CEN-GWEXER: ##reboot## 45 +* 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]] 46 +* Repeat for all CEN-GWEXERs on the job 47 + 48 +== Static Configuration == 49 + 50 +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: 51 + 52 +* Open Text Console in Toolbox and connect to the CEN-GWEXER 53 +** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect 54 +* 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**(%%)) 55 +** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)## 56 +** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)## 57 +** Set default gateway: ##defr 0 **10.0.0.1**## 58 +** Disable DHCP: ##dhcp off## 59 +** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)## 60 +** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)## 61 +** Reboot the CEN-GWEXER: ##reboot## 62 +* 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]] 63 +* Repeat for all CEN-GWEXERs on the job 64 + 49 49 = RF Channel = 50 50 51 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. ... ... @@ -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 = 81 += 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 103 +* The process for acquiring a wireless device to a gateway varies for each model, but generally the procedure is as follows: 104 +** Press the "setup" button (top button for keypads) in the sequence press-press-press-hold 105 +** Do not release the button until the setup LED (top feedback LED for keypads) begins blinking slowly 106 +*** If the setup LED turns steady, then the device was acquired successfully 107 +*** If the setup LED begins to rapidly blink, then the acquire failed 108 +**** Press the "setup" button again to cancel acquire 109 +**** Attempt to acquire the device again 110 +**** 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. 111 +** Repeat for all wireless devices that need to be acquired to the gateway 112 +* 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 114 +** If using the Gateway Configuration tool, click the "STOP Acquire" button in the lower left 115 +* Address devices as indicated in the SHOWRUNNER™ takeoff by either: 116 +** Use Text Console to run the command: ##setrfidbytsid [CID] [TSID]## 117 +*** Replace "[CID]" with the connection ID as indicated in the takeoff 118 +*** Replace "[TSID]" with the 4-byte, hexadecimal TSID of the device to be addressed 119 +** Use Network Device Tree View to select each device and address them individually 120 +* 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.