Changes for page ShowRunnerCLC™ BACnet
Last modified by Alexander Mott on 2024/06/14 18:19
From version 26.1
edited by Mark Kohlmann
on 2023/07/21 21:33
on 2023/07/21 21:33
Change comment:
There is no comment for this version
To version 30.1
edited by Alexander Mott
on 2024/06/14 18:06
on 2024/06/14 18:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. mark\.kohlmann@chiefintegrations\.com1 +XWiki.alexander\.mott@chiefintegrations\.com - Content
-
... ... @@ -1,5 +1,7 @@ 1 -ShowRunnerCLC™ uses Crestron's BACnet/IP stack and is bound by its licensing and limit s. ShowRunnerCLC™'s BACnet featureis licensed, a license from Chief Integrationsis required. Integrations of 50 points or less may use the free Crestron BACnet license.More than 50 points require the Crestron paid licenseand total points are limited by the platform(ZUM-HUB4 processors include a BACnet license, but require a separate license from Crestron to enable ShowRunnerCLC™ installation on the processor).processoritselfconsumesa point.BACnet points areassignedduringcommissioning.A .csvexportofthepoints maybedownloadedfromthe system.1 +ShowRunnerCLC™ uses Crestron's BACnet/IP stack and is bound by its licensing and limitations. Integrations of 50 points or less may use the free Crestron BACnet license, while integrations with more than 50 points require the Crestron paid license (ZUM-HUB4 processors include a BACnet license, but require a separate license from Crestron to enable ShowRunnerCLC™ installation on the processor). The maximum number of BACnet points available is limited per processor and detailed in the table below (note that the processor itself consumes a point). 2 2 3 +ShowRunnerCLC™'s BACnet feature is licensed, and an additional license from Chief Integrations is required. BACnet points are automatically created and assigned during commissioning, and a .csv export of the points may be downloaded from the system. It is recommended to wait until the end of the project to provide BACnet points to third parties as changes to the ShowRunnerCLC™ program during commissioning may affect the names and IDs for automatically generated BACnet points. ShowRunnerCLC™ version 3.050 and newer includes support for fully custom BACnet points, but it is recommended that custom BACnet points only be used where required by existing jobsite conditions (i.e. when ShowRunnerCLC™ is being used to upgrade an older system with existing BACnet integrations) due to the labor involved with manually creating BACnet points. Automatic point generation is recommended for all ShowRunnerCLC™ deployments on new construction. 4 + 3 3 BACnet Stack Features: 4 4 5 5 * BACnet/IP ... ... @@ -6,6 +6,7 @@ 6 6 * Configurable BACnet UDP port (options may be limited by processor firmware) 7 7 * BBMD w/ Foreign Device Registration (Enabled if necessary) 8 8 * Points can be discovered using traditional BACnet discovery tools 11 +* ShowRunner version 3.050 and later support custom BACnet points. Please discuss with Chief Integrations. 9 9 10 10 === Crestron BACnet Stack Details === 11 11 ... ... @@ -39,7 +39,7 @@ 39 39 )))|2000 40 40 |((( 41 41 * ZUM-HUB4 42 -)))| 10,00045 +)))|9,000 43 43 44 44 [[Crestron PICS Statement>>attach:Crestron_PICS.PDF]] 45 45 ... ... @@ -53,11 +53,11 @@ 53 53 AreaBaseID = BACnetIndex * Offset}}} 54 54 55 55 |=Feature|=Description|=Type|=Point|=Label|=R/W|=Units 56 -|Area Scene|Current Scene Active on the Area|MV|AreaBaseID|{AreaId}:{AreaName} Scene|RW|Scene 57 -|Occupancy Mode|Current Occupancy Mode for the Area|MV|AreaBaseID + 2|{AreaId}:{AreaName} Occupancy Mode|RW|Mode 59 +|Area Scene|Current Scene Active on the Area / Change Scene|MV|AreaBaseID|{AreaId}:{AreaName} Scene|RW|Scene 60 +|Occupancy Mode|Current Occupancy Mode for the Area / Change Occupancy Mode|MV|AreaBaseID + 2|{AreaId}:{AreaName} Occupancy Mode|RW|Mode 58 58 |Occupancy Status|Current Occupancy Status for the Area|BI|AreaBaseID + 1|{AreaId}:{AreaName} Occupied|R|Boolean 59 59 |Area Intensity|Current Area Average Intensity/Load Level (v3.010 or later)|AV|AreaBaseID + 3|{AreaId}:{AreaName} Intensity|RW|Percentage 60 -|Area Power|Current Area Power Consumption in Watts (Requires EM License & v3.010 or later)|AI|AreaBaseID + 4|{AreaId}:{AreaName} Power|R|Watts 63 +|Area Power|Current Area Power Consumption in Watts (Requires SR EM License & v3.010 or later)|AI|AreaBaseID + 4|{AreaId}:{AreaName} Power|R|Watts 61 61 |Loads|Individual Load intensities for each Load in the Area|AV|AreaBaseID + (V2: 100, V1: 1000) + LoadIndex|{AreaId}:{AreaName} Load{LoadId}:{LoadName}|RW|Percentage 62 62 |Photocell Level|Photocell sensor reading for each Photocell in the Area|AI|AreaBaseID + (V2: 50, V1: 100) + PhotocellIndex|{AreaId}:{AreaName} Photocell{PhotocellId}:{PhotocellName}|R|Percentage 63 63