Skip to Content
Last modified by Scott Kohlmann on 2023/04/20 22:34
From version 4.2
edited by Mark Kohlmann
on 2021/12/08 00:15
Change comment: Update document after refactoring.
To version 6.1
edited by Mark Kohlmann
on 2022/10/14 15:44
Change comment: There is no comment for this version

Summary

Details

Page properties
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  
... ... @@ -32,3 +32,9 @@
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 +===== =====
37 +
38 +===== Option 3: Virtual Fixtures =====
39 +
40 +In this scenario SR tracks "virtual fixtures" created in the WTEC system and maps them to SR loads.  Delay is minimal in this scenario, a fraction of a second.