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 14.1
edited by Alexander Mott
on 2022/09/19 16:09
Change comment: There is no comment for this version

Summary

Details

Page properties
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.