Skip to Content
Last modified by Alexander Mott on 2024/12/02 19:02
From version 1.2
edited by Alexander Mott
on 2024/10/24 17:30
Change comment: (Autosaved)
To version 1.1
edited by Alexander Mott
on 2024/10/24 17:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,19 +30,19 @@
30 30  
31 31  (% class="box warningmessage" %)
32 32  (((
33 -Be sure to complete the above SSL Setup prior to setting the IP table
33 +
34 34  )))
35 35  
36 -If the lighting network has a permanent DHCP server, then CEN-IOs 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-IOs are not known, then the best way to update their configuration is via USB (microUSB). If you are able to identify the CEN-IOs by MAC address, then it is possible to configure these settings via Ethernet using Text Console. Whether connected to the CEN-IO via USB or Ethernet, the process to configure the IP table and hostname is the same:
36 +If the lighting network has a permanent DHCP server, then CEN-IO-COMs 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-IO-COMs are not known, then the best way to update their configuration is via USB (microUSB). If you are able to identify the CEN-IO-COMs by MAC address, then it is possible to configure these settings via Ethernet using Text Console. Whether connected to the CEN-IO-COM via USB or Ethernet, the process to configure the IP table and hostname is the same:
37 37  
38 -* Open Text Console in Toolbox and connect to the CEN-IO
38 +* Open Text Console in Toolbox and connect to the CEN-IO-COM
39 39  ** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect
40 -* Run the following commands to configure the CEN-IO's IP table and hostname (example is for an IP-ID of (% style="color:olive" %)**21**(%%), and a target processor IP address of (% style="color:orange" %)**172.22.0.1**(%%), and a device hostname of (% style="color:purple" %)**IO-COM-L1**(%%))
41 -** Update IP table: ##addm (% style="color:olive" %)**21**(%%) (% style="color:orange" %)**172.22.0.1**(%%)##
42 -** Set hostname: ##host (% style="color:purple" %)**IO-COM-L1**(%%)##
43 -** Reboot the CEN-IO: ##reboot##
40 +* Run the following commands to configure the CEN-IO-COM'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**(%%))
41 +** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**172.22.0.1**(%%)##
42 +** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)##
43 +** Reboot the CEN-IO-COM: ##reboot##
44 44  * 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]]
45 -* Repeat for all CEN-IOs on the job
45 +* Repeat for all CEN-IO-COMs on the job
46 46  
47 47  == Static Configuration ==
48 48  
... ... @@ -51,17 +51,82 @@
51 51  Be sure to complete the above SSL Setup prior to setting the IP table
52 52  )))
53 53  
54 -If there is no permanent DHCP server on the lighting network, then CEN-IOs 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-IOs 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:
54 +If there is no permanent DHCP server on the lighting network, then CEN-IO-COMs 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-IO-COMs 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:
55 55  
56 -* Open Text Console in Toolbox and connect to the CEN-IO
56 +* Open Text Console in Toolbox and connect to the CEN-IO-COM
57 57  ** Note that you may need to manually select "SSL" connection type, as "Auto" might not always redirect
58 -* Run the following commands to configure the CEN-IO'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" %)**21**(%%), and a target processor IP address of (% style="color:orange" %)**10.0.0.10**(%%), and a device hostname of (% style="color:purple" %)**COM-IO-L1**(%%))
58 +* Run the following commands to configure the CEN-IO-COM'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**(%%))
59 59  ** Set IP address: ##ipa 0 (% style="color:blue" %)**10.0.0.12**(%%)##
60 60  ** Set IP subnet mask: ##ipm 0 (% style="color:darkgoldenrod" %)**255.255.255.0**(%%)##
61 61  ** Set default gateway: ##defr 0 **10.0.0.1**##
62 62  ** Disable DHCP: ##dhcp off##
63 -** Update IP table: ##addm (% style="color:olive" %)**21**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
64 -** Set hostname: ##host (% style="color:purple" %)**COM-IO-L1**(%%)##
65 -** Reboot the CEN-IO: ##reboot##
63 +** Update IP table: ##addm (% style="color:olive" %)**C1**(%%) (% style="color:orange" %)**10.0.0.10**(%%)##
64 +** Set hostname: ##host (% style="color:purple" %)**GWEXER-L1**(%%)##
65 +** Reboot the CEN-IO-COM: ##reboot##
66 66  * 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]]
67 -* Repeat for all CEN-IOs on the job
67 +* Repeat for all CEN-IO-COMs on the job
68 +
69 += RF Channel =
70 +
71 +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-IO-COMs.
72 +By default, all CEN-IO-COMs 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-IO-COMs. When selecting which RF channel to use for each CEN-IO-COM, it is best to avoid using the same RF channel for any CEN-IO-COMs 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.
73 +
74 +* If using Text Console, run the command: ##rfchannel [#]##
75 +** Replace "[#]" with the desired RF channel
76 +* If using the Gateway Configuration tool:
77 +** Connect to the CEN-IO-COM in another tool such as Text Console
78 +** Navigate to Functions > Gateway Configuration... to open the tool
79 +** At the top left, under "RF Channel", ensure "Fixed" is selected and then choose a channel
80 +** The Gateway Configuration window will become nonresponsive while the RF channel is being applied to the gateway
81 +** Close the tool once the change has been applied
82 +* Once the RF channel has been updated, verify it by running the command: ##rfchannel## without any parameters
83 +
84 += Acquiring and Addressing Devices =
85 +
86 +(% class="box warningmessage" %)
87 +(((
88 +**When acquiring wireless hardware on jobs with multiple CEN-IO-COMs, it is very important that only one gateway is in acquire mode at a time.**
89 +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.
90 +Attempting to acquire devices while multiple gateways are actively in acquire mode may result in wireless hardware being acquired to the incorrect gateway.
91 +)))
92 +
93 +Unlike wired Cresnet devices such as DIN-CENCN-2s or processors which can poll the connected Cresnet and report all devices that are currently connected, CEN-IO-COMs and other wireless gateways must first acquire the wireless Crestron devices. Acquiring wireless Crestron devices involves putting the gateway into acquire mode and then performing a physical button press sequence on each of the wireless devices to be acquired. This process is described in detail below:
94 +
95 +* Put the CEN-IO-COM into acquire mode using one of the methods below:
96 +** If using Text Console, run the command: ##acquire start##
97 +*** Devices will indicate their TSID in the Text Console window as they are acquired
98 +** If using the Gateway Configuration tool:
99 +*** Connect to the CEN-IO-COM in another tool such as Text Console
100 +*** Navigate to Functions > Gateway Configuration... to open the tool
101 +*** At the bottom left, click "Start Acquire"
102 +*** [[image:1701720163760-996.png||height="271" width="316"]]
103 +*** Wait for the confirmation dialog and click "OK" to close the confirmation dialog
104 +*** Previously acquired devices will be displayed with black text, while newly acquired devices will populate with blue text
105 +*** 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
106 +* The process for acquiring a wireless device to a gateway varies for each model, but generally the procedure is as follows:
107 +** Press the "setup" button (top button for keypads) in the sequence press-press-press-hold
108 +** Do not release the button until the setup LED (top feedback LED for keypads) begins blinking slowly
109 +*** If the setup LED turns steady, then the device was acquired successfully
110 +*** If the setup LED begins to rapidly blink, then the acquire failed
111 +**** Press the "setup" button again to cancel acquire
112 +**** Attempt to acquire the device again
113 +**** 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.
114 +** Repeat for all wireless devices that need to be acquired to the gateway
115 +* Once all devices have been acquired, take the CEN-IO-COM out of acquire mode:
116 +** If using Text Console, run the command: ##acquire stop##
117 +** If using the Gateway Configuration tool, click the "STOP Acquire" button in the lower left
118 +* Address devices as indicated in the SHOWRUNNER™ takeoff by either:
119 +** Use Text Console to run the command: ##setrfidbytsid [CID] [TSID]##
120 +*** Replace "[CID]" with the connection ID as indicated in the takeoff
121 +*** Replace "[TSID]" with the 4-byte, hexadecimal TSID of the device to be addressed
122 +** Use Network Device Tree View to select each device and address them individually
123 +* Verify all devices have been acquired and addressed correctly using Network Device Tree View or with the Text Console command: ##reportnetdev##
124 +
125 += Moving/Removing Devices (Unacquiring Devices) =
126 +
127 +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.
128 +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:
129 +
130 +* ##unacquirebytsid [TSID] 0##
131 +* ##unacquirebytsid [TSID] 1##
132 +Once all of the necessary TSIDs have been unacquired, use the ##reboot## command to reboot the gateway and complete the unacquire process.