Skip to Content
Last modified by Alexander Mott on 2024/09/13 16:45
From version 13.1
edited by Alexander Mott
on 2022/09/17 00:37
Change comment: There is no comment for this version
To version 15.1
edited by Scott Kohlmann
on 2023/04/21 13:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
1 +XWiki.scott\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,11 +1,9 @@
1 -{{box title="**CONTENTS**"}}
1 +{{box cssClass="floatinginfobox" title="**CONTENTS**"}}
2 2  {{toc/}}
3 3  {{/box}}
4 4  
5 5  (% class="row" %)
6 6  (((
7 -= Overview =
8 -
9 9  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).
10 10  
11 11  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.
... ... @@ -12,15 +12,15 @@
12 12  
13 13  Serial numbers should be collected by the electrical contractor during installation and provided to the lighting controls technician prior to startup.
14 14  
15 -= Addressing Devices in SHOWRUNNER™ =
13 += Addressing Devices in ShowRunnerCLC™ =
16 16  
17 -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]].)
15 +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]].)
18 18  
19 -To address devices in the SHOWRUNNER™ UI:
17 +To address devices in the ShowRunnerCLC™ UI:
20 20  
21 21  * [[Configure the processor and load the configuration file>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.Processor Setup.WebHome]]
22 22  * If other network devices are present, [[they should also be configured>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.SHOWRUNNER™ Installation and Network Setup.WebHome]]
23 -* Launch the SHOWRUNNER™ XPanel UI and connect to the processor
21 +* Launch the ShowRunnerCLC™ XPanel UI and connect to the processor
24 24  * Navigate to Settings>Device Addressing
25 25  * This page lists all devices that are defined in the program, sorted by ID:
26 26  .[[image:1655828296124-885.png||height="372" width="638"]]