Skip to Content
Last modified by Scott Kohlmann on 2023/04/20 22:34
From version 11.1
edited by Mark Kohlmann
on 2023/02/12 05:05
Change comment: There is no comment for this version
To version 12.1
edited by Scott Kohlmann
on 2023/04/20 22:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.mark\.kohlmann@chiefintegrations\.com
1 +XWiki.scott\.kohlmann@chiefintegrations\.com
Content
... ... @@ -1,4 +1,4 @@
1 -SHOWRUNNER™ (SR) can control locations and fixtures attached to a WTEC SmartDirector or SmartEngine.  Connectivity is via an HTTPS connection to either the SmartDirector or SmartEngine.  SmartDirector is the preferred end point.
1 +ShowRunnerCLC™ (SR) can control locations and fixtures attached to a WTEC SmartDirector or SmartEngine.  Connectivity is via an HTTPS connection to either the SmartDirector or SmartEngine.  SmartDirector is the preferred end point.
2 2  
3 3  ===== Caveats: =====
4 4  
... ... @@ -14,7 +14,7 @@
14 14  
15 15  There are three main approaches to take when integrating with a WTEC SmartDirector or SmartEngine.
16 16  
17 -===== Option 1: Locations/Fixtures are treated as SHOWRUNNER™ loads =====
17 +===== Option 1: Locations/Fixtures are treated as ShowRunnerCLC™ loads =====
18 18  
19 19  In this scenario SR treats Locations on the WTEC system effectively as load groups.  This approach is best when SR is the master lighting system for a project.  Locations are added to SR as loads.  Any commands to a load are sent to the WTEC system for execution.  Changes in the WTEC system will be sent back to SR and the load's status will be updated on SR side.  If a scene is activated on the WTEC side then SR can still command the master intensity for the location.  SR load profiles and settings are applied before a command is sent to the WTEC location.  Initial setup for this can be done from a csv file via the command line.
20 20  
... ... @@ -25,7 +25,7 @@
25 25  * Enter "0" for the Load Index
26 26  * Name and assign the newly created load to the appropriate area
27 27  
28 -===== Option 2: Locations are treated as SHOWRUNNER™ Areas and Individual Fixture Control (Optional) =====
28 +===== Option 2: Locations are treated as ShowRunnerCLC™ Areas and Individual Fixture Control (Optional) =====
29 29  
30 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  
... ... @@ -53,6 +53,6 @@
53 53  
54 54  ===== Partition Sensors =====
55 55  
56 -showrunner can report partition sensor status to WTEC.
56 +ShowRunnerCLC™ can report partition sensor status to WTEC.
57 57  
58 58  [[Config Example>>WTEC Partition Configuration Sample]]