Skip to Content
Last modified by Scott Kohlmann on 2023/04/20 22:34
From version 3.1
edited by Mark Kohlmann
on 2021/06/11 19:51
Change comment: There is no comment for this version
To version 5.1
edited by Mark Kohlmann
on 2022/10/14 15:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -SHOWRUNNER™ User Guide & Wiki.Design Guide.Hardware Design Guide.WebHome
1 +Design Guide.Hardware Design Guide.WebHome
Content
... ... @@ -7,12 +7,12 @@
7 7  * WTEC occupancy actions apply load levels globally by location and do not provide granular settings.
8 8  * WTEC plug loads can only be controlled as part of a location.
9 9  * Fixtures may be controlled directly but each fixture must be commanded individually which will result in a delay between each fixtures receipt of a commanded load level.
10 -* Feedback from the WTEC system is delayed ~~1 second.  Real-world experience seems to be 1/2 to 2 seconds.
10 +* Feedback from the WTEC system is delayed ~~1 second.  Real-world experience seems to be 1/2 to 2 seconds.  This is addressed with option 3.
11 11  * SR cannot modify WTEC scene settings
12 12  * Location intensity overrides fixture intensity
13 13  * Due to heavy data transfer via HTTP a 4-series or better is required for this integration.
14 14  
15 -There are two main approaches to take when integrating with a WTEC SmartDirector or SmartEngine.
15 +There are three main approaches to take when integrating with a WTEC SmartDirector or SmartEngine.
16 16  
17 17  ===== Option 1: Locations/Fixtures are treated as SHOWRUNNER™ loads =====
18 18  
... ... @@ -27,8 +27,15 @@
27 27  
28 28  ===== Option 2: Locations are treated as SHOWRUNNER™ Areas and Individual Fixture Control (Optional) =====
29 29  
30 -In this scenario we treat Locations on the WTEC system as an SR Area.  This approach is best when an SR touchscreen, keypad, schedule, or occupancy sensor needs to recall scenes defined on the WTEC system.  SR scenes are mapped to WTEC Location scenes by querying the WTEC system for the scene names assigned to a Location.  The last scene listed is mapped to SR's off scene, the first through 2nd to last are mapped in order from scene 1 (on) to scene N.  Master raise/lower will be sent to the WTEC system to control the master intensity.  Fixtures may be controlled individually in this application if there are no scene settings on the WTEC system because an active WTEC scene will lock out fixture control.  Settings this up is best done by importing a csv file into SR from the command line.
30 +In this scenario we treat Locations on the WTEC system as an SR Area.  This approach is best when an SR touchscreen, keypad, schedule, or occupancy sensor needs to recall scenes defined on the WTEC system.  SR scenes are mapped to WTEC Location scenes by querying the WTEC system for the scene names assigned to a Location.  The last scene listed is mapped to SR's off scene, the first through 2nd to last are mapped in order from scene 1/On to scene N.  Master raise/lower will be sent to the WTEC system to control the master intensity.  Fixtures may be controlled individually in this application if there are no scene settings on the WTEC system because an active WTEC scene will lock out fixture control.  Settings this up is best done by importing a csv file into SR from the command line.
31 31  
32 32  ===== Notes: =====
33 33  
34 34  * SR loads can track the status of WTEC Location or Fixtures by associating an SR load with the WTEC load using TrackLoadGlobalId property on the SR load.  This is helpful if Crestron hardware is controlling EM loads in locales that do not permit POE lighting for EM purposes.  The SR/Crestron load will follow the state of the WTEC Location or Fixture.
35 +
36 +(% class="wikigeneratedid" %)
37 +===== =====
38 +
39 +===== Option 3: Virtual Fixtures =====
40 +
41 +In this scenario SR tracks "virtual fixtures" created in the WTEC system and maps them to SR loads.