Changes for page Crestron RF Gateway Setup
Last modified by Alexander Mott on 2025/03/12 17:16
From version 13.1
edited by Alexander Mott
on 2024/02/09 00:48
on 2024/02/09 00:48
Change comment:
There is no comment for this version
To 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
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -8,30 +8,14 @@ 8 8 9 9 = IP Configuration = 10 10 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 . IftheDHCPserver onthenetworkis temporary (e.g.DHCP server softwarerunningon your computer oraprocessor utilizing, 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]]). 12 12 13 - When connecting to aCEN-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. 14 14 15 - ==DHCPConfiguration==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 -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 20 * Open Text Console in Toolbox and connect to the CEN-GWEXER 21 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 (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**(%%)) 23 -** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**172.22.0.1**(%%)## 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 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 36 ** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)## 37 37 ** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)## ... ... @@ -40,7 +40,6 @@ 40 40 ** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)## 41 41 ** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)## 42 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 44 * Repeat for all CEN-GWEXERs on the job 45 45 46 46 = SSL Setup = ... ... @@ -79,7 +79,7 @@ 79 79 ** Close the tool once the change has been applied 80 80 * Once the RF channel has been updated, verify it by running the command: ##rfchannel## without any parameters 81 81 82 -= Acquiring and AddressingDevices =65 += Acquiring Devices = 83 83 84 84 (% class="box warningmessage" %) 85 85 ((( ... ... @@ -101,25 +101,22 @@ 101 101 *** Wait for the confirmation dialog and click "OK" to close the confirmation dialog 102 102 *** Previously acquired devices will be displayed with black text, while newly acquired devices will populate with blue text 103 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: 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 114 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## 92 +** If 93 +* 94 +* 95 +* Once devices have been acquired, use the text console command: reportnetdev to view the network ID 122 122 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 + 123 123 = Moving/Removing Devices (Unacquiring Devices) = 124 124 125 125 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.