Skip to Content

Wiki source code of CEN-GWEXER Setup

Version 6.3 by Alexander Mott on 2023/12/04 19:26
Show last authors
1 {{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 {{toc/}}
3 {{/box}}
4
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.
6
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.
8
9 = IP Configuration =
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 (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
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
15 Whether connected to the CEN-GWEXER via USB or Ethernet, the process to configure the static IP addresses is the same:
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 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
33 Configure the Connects user on the processor:
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
42
43 Configure the CS authentication on the CEN-GWEXER:
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 Lorem
52
53 ~/~/"RFCHAnnel [#]" set rf channel for gwexer
54
55 = Acquiring Devices =
56
57 ~/~/1-2-3-hold on 4 until all lights blink, then release
58 top light will blink slowly a few times and then hold solid or start blinking rapidly
59 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
60
61 == Text Console ==
62
63 ~/~/"acquire start" and "acquire stop"
64
65 ~/~/"rep" to show acquired devices
66
67 == Gateway Configuration Tool ==
68
69 ~/~/Connect > functions > gateway configuration for better acquiring tool
70
71 = Moving/Removing Devices (Unacquiring Devices) =
72
73 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.
74
75 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:
76
77 * ##unacquirebytsid [TSID] 0##
78 * ##unacquirebytsid [TSID] 1##
79
80 Once all of the necessary TSIDs have been unacquired, use the ##reboot## command to reboot the gateway and complete the unacquire process.