Wiki source code of CEN-GWEXER Setup
Version 3.1 by Alexander Mott on 2023/12/04 16:57
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 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 | Lorem | ||
| 12 | |||
| 13 | = SSL Setup = | ||
| 14 | |||
| 15 | Lorem | ||
| 16 | |||
| 17 | = RF Channel = | ||
| 18 | |||
| 19 | Lorem | ||
| 20 | |||
| 21 | = Useful Commands and Other Notes = | ||
| 22 | |||
| 23 | Lorem | ||
| 24 | |||
| 25 | == Acquiring Devices == | ||
| 26 | |||
| 27 | Lorem | ||
| 28 | |||
| 29 | == Moving/Removing Devices (Unacquiring Devices) == | ||
| 30 | |||
| 31 | 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. | ||
| 32 | |||
| 33 | 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: | ||
| 34 | |||
| 35 | * ##unacquirebytsid [TSID] 0## | ||
| 36 | * ##unacquirebytsid [TSID] 1## | ||
| 37 | |||
| 38 | Once all of the necessary TSIDs have been unacquired, use the ##reboot## command to reboot the gateway and complete the unacquire process. |