Skip to Content
Last modified by Alexander Mott on 2024/09/13 16:45
From version 18.1
edited by Alexander Mott
on 2024/09/13 16:45
Change comment: There is no comment for this version
To version 4.1
edited by Alexander Mott
on 2022/06/21 16:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Addressing Devices in the ShowRunnerCLC™ UI
1 +Addressing Devices from the UI
Content
... ... @@ -1,13 +1,5 @@
1 -(% class="box warningmessage" %)
2 -(((
3 -Device addressing using the method described below may be unreliable in newer builds of ShowRunnerCLC™ (v3.011+)
4 -The current recommendation for ShowRunnerCLC™ start-ups is to [[address devices through Toolbox>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Addressing Devices from Toolbox.WebHome]], using either the Network Device Tree View tool or text console commands
5 -)))
1 +=== Overview ===
6 6  
7 -{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
8 -{{toc/}}
9 -{{/box}}
10 -
11 11  All Crestron lighting control programs function on the same basic principles with regard to addressing devices. The lighting control program maintains an internal database of controlled hardware (i.e. load controllers, keypads, sensors, etc.) which are each given a unique //address//. These unique addresses, as defined in the program, include the //device connection ID// (a.k.a. Cresnet ID) of the controlled device, the //device host id// (i.e., the ID of the device where the Cresnet or Zūm Link cable is landed), and the //device host branch// (for cases where the host device has multiple Nets, such as the DIN-CENCN-2).
12 12  
13 13  In order for the lighting control program to function, all of the devices that it is meant to control must be addressed. Since there are often multiples of the same model device on a job, it is important to be able to distinguish between them (e.g. we need the keypad in the kitchen to control lights in the kitchen and not in the office). In order to uniquely identify each individual device, every device is given a globally unique serial number which is printed on the device at the factory. These serial numbers and the associated touch-settable ID (TSID) are reported to the processor when the device is connected. If the serial number for a given device is known, it can be used to assign that device the correct address for the program.
... ... @@ -14,18 +14,18 @@
14 14  
15 15  Serial numbers should be collected by the electrical contractor during installation and provided to the lighting controls technician prior to startup.
16 16  
17 -= Device Addressing in the XPanel UI =
9 +=== Addressing Devices in SHOWRUNNER™ ===
18 18  
19 -Cresnet devices can be addressed from the ShowRunnerCLC™ UI if their serial numbers are known. (Note that Zūm Wired devices cannot currently be addressed from the ShowRunnerCLC™ UI because their serial numbers cannot be directly translated into TSIDs. Instead, they must be [[addressed through Toolbox>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Addressing Devices from Toolbox.WebHome]].)
11 +Cresnet devices can be addressed from the SHOWRUNNER™ UI if their serial numbers are known. (Note that Zūm Wired devices cannot currently be addressed from the SHOWRUNNER™ UI because their serial numbers cannot be directly translated into TSIDs. Instead, they must be [[addressed through Toolbox>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.Addressing Devices from Toolbox.WebHome]].)
20 20  
21 -To address devices in the ShowRunnerCLC™ UI:
13 +To address devices in the SHOWRUNNER™ UI:
22 22  
23 23  * [[Configure the processor and load the configuration file>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome]]
24 24  * If other network devices are present, [[they should also be configured>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]]
25 -* Launch the ShowRunnerCLC™ XPanel UI and connect to the processor
17 +* Launch the SHOWRUNNER™ XPanel UI and connect to the processor
26 26  * Navigate to Settings>Device Addressing
27 27  * This page lists all devices that are defined in the program, sorted by ID:
28 -.[[image:1655828296124-885.png||height="372" width="638"]]
20 +[[image:1655828296124-885.png||height="372" width="638"]]
29 29  ** "Model" column indicates the expected device model (e.g. C2N-CBD-P, GLPP-DIMFLVCN-PM, GLPP-1DIMFLV2CN-PM, etc.)
30 30  ** "Description" gives the Global ID and label for any associated devices (including any non-system sensors)
31 31  ** "ID" lists the device address in the form: ##[HostDeviceID]**-**[HostBranch]**:**[ConnectionID]##
... ... @@ -48,7 +48,7 @@
48 48  * There should be check boxes next to "Models Match", "SN Match", and "Online". All three boxes must be checked for the "Verified" check mark to appear
49 49  ** If the "Models Match" check mark is missing, verify that the reported model matches the model in the configuration
50 50  ** If the "SN Match" check mark is missing, verify that you have the correct serial number entered
51 -*** If there is a "Capture Reported Serial Number" button next to the "Serial Number" field, it can be used to record the serial number of the device to see what the serial number is for the device currently at that address.
43 +*** If there is a "Capture Reported Serial Number" button next to the "Serial Number" field, it can be used to record the serial number of the device
52 52  ** If the "Online" check mark is missing, then there is no device reporting online at that Host Device/Branch and Connection ID
53 53  * As of June 2022, issues have been reported with Crestron's Device Database that results in processors being unable to properly query devices:
54 54  ** Run the command ##broadcast on## command in Text Console