Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.44
edited by Alexander Mott
on 2023/05/05 21:25
Change comment: (Autosaved)
To version 3.1
edited by Alexander Mott
on 2023/05/05 21:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,20 +14,10 @@
14 14  
15 15  * Individual loads defined in ShowRunner™ send commands to individual Fixture Groups in Pharos
16 16  * Scenes in ShowRunner™ can be mapped in order to trigger Timelines in Pharos
17 -* The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT(% class="row" %)
18 -(((
19 -(% class="col-xs-8" %)
20 -(((
21 -(% class="table-condensed" %)
22 -|(% style="width:244px" %)**ShowRunner™ Load Type**|(% style="width:244px" %)**Pharos API Command**
23 -|(% style="width:244px" %)Single-Channel|(% style="width:244px" %)Intensity
24 -|(% style="width:244px" %)RGB|(% style="width:244px" %)Intensity/RGB
25 -|(% style="width:244px" %)Dynamic White|(% style="width:244px" %)Intensity/CCT
26 -)))
27 -)))
28 -* The Pharos controller does any necessary processing to adapt these commands for the fixtures
29 -** For example, if Pharos receives an RGB command for a group containing RGB, HSI, and HSIC fixtures, it will do its best to make sure that the output color is consistent across all the different fixture types
30 -** Certain manufacturer-specific fixture Profiles exist in order to help the Pharos controller achieve a consistent output across multiple different fixture types
17 +* The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT
18 +** Other fixture profiles are still supported: the Pharos controller will do any necessary processing to adapt the commands to the fixtures
19 +*** For example, if Pharos receives an RGB command for a group containing RGB, HSI, and HSIC fixtures, it will mix the DMX channels to achieve a consistent color output across all the different fixture types
20 +*** Certain manufacturer-specific fixture Profiles exist in order to help the Pharos controller achieve a consistent output across multiple different fixture types
31 31  * To control the RGB and white channels of an RGBW fixture separately in ShowRunner™, it is necessary to define separate RGB and White fixtures in the Pharos project 
32 32  ** Add both a generic RGB fixture and a generic White fixture to the layout
33 33  ** Assign each fixture to a different group
... ... @@ -113,16 +113,16 @@
113 113  
114 114  = ShowRunner™ Configuration =
115 115  
116 -ShowRunner™ is able to control fixtures in Pharos by sending group-level commands directly to Fixture Groups that are defined in the Pharos project, triggering Timelines that are defined in the Pharos project, or both. Note that since fixt
106 +ShowRunner™ is able to control fixtures in Pharos by sending group-level commands directly to Fixture Groups that are defined in the Pharos project, triggering Timelines that are defined in the Pharos project, or both. Note that ShowRunner™ does not receive feedback from the Pharos controller, so fixture feedback as shown in the ShowRunner™ UI is only accurate if ShowRunner™ sent group-level commands. Changes to fixture levels caused by a Timeline are not reflected in the ShowRunner™ UI.
117 117  
118 118  In order to control DMX fixtures on a Pharos controller with ShowRunner™, it is necessary to make sure that the ShowRunner™ configuration has the correct settings for the Pharos controller. Under the "LightingControllers" section of the ShowRunner™ configuration, locate the entry for the Pharos controller. Under the "Properties" section, verify that the "IpAddressOrHostname" matches the IP address or hostname of the Pharos controller. The "ApiPort" only needs to be changed if the HTTP port for the Pharos controller's web server has been changed from the default 80. Once the Properties for all Pharos controllers have been updated, load the configuration to the processor.
119 119  
120 -To add Pharos loads to ShowRunner™, launch the XPanel and navigate to the Settings > Load Configuration page and then select the Pharos controller from the list of controllers on the left. Once the controller is selected, press the "Configure Loads" button:
110 +Control Pharos groups with ShowRunner™, it is necessary to define them as loads in the ShowRunner™ configuration. To do this using the XPanel UI, navigate to the Settings > Load Configuration page and then select the Pharos controller from the list of controllers on the left. Once the controller is selected, press the "Configure Loads" button:
121 121  
122 -* All currently defined loads are shown on the left
112 +* Currently defined loads are shown in the list on the left
123 123  ** The "Group: #" of the load must match the group number as defined in the Pharos project
124 124  ** It is not possible to change the group of an existing load from the XPanel UI. Instead, either save the config and edit the "LoadBaseIndex" property of the load, or delete the load and create a new load at the correct group
125 -* To add a new load to the controller, press "Add New Load" below the list of loads
115 +* Press "Add New Load" below the list of loads to create a new load
126 126  ** The "Load Index/Channel" must match the group number as defined in the Pharos project
127 127  *** Since ShowRunner™ uses group-level commands and fixtures in a group aren't necessarily on the same DMX universe, the "Universe ID" is grayed out and cannot be modified
128 128  *** It is not possible to assign multiple Pharos groups to the same load, and it is not possible to assign multiple loads to the same group
... ... @@ -141,8 +141,26 @@
141 141  ** If controlling the RGB and White channels of an RGBW fixture separately, then you must define an RGB type load associated with the RGB fixture group in Pharos and then a Single Channel type load associated with the White fixture group in Pharos
142 142  ** The Area Assignment dictates what area the load will be associated with
143 143  
144 -ShowRunner™ is also capable of triggering Timelines in the Pharos project.
134 +ShowRunner™ is also capable of triggering Timelines in the Pharos project. This can be configured using the XPanel UI:
145 145  
136 +1. Navigate to Settings > Load Hardware
137 +1. Select the Pharos controller from the list of load controllers on the left
138 +1. Press "Configure Scene Tracking"
139 +1. Tick the "Enable Scene Tracking" box to enable scene tracking
140 +1. Select an area whose scenes you want to trigger Timelines from the "Area to Track" list
141 +1*. Note that the area selected does not actually need any loads assigned to it
142 +1*. Pharos fixture groups do not need to be defined as loads in ShowRunner™ at all if scene tracking is being used to control fixtures
143 +1. With the area selected, press "Add New Map"
144 +1. Select the scene you want to trigger the Timeline from the list of scenes
145 +1. Enter the number of the Timeline as defined in the Pharos project in the "Timeline ID" field
146 +1. Press "Add" to add the scene map
147 +1. Press "Add New Map" to add more Timelines, or select another area to trigger Timelines with scene recalls on other areas
146 146  
147 -Once scene tracking has been configured for an area, Pharos Timelines will be triggered regardless of whether the individual loads are actually defined in ShowRunner™ or not.
149 +Some things to consider if you are triggering Pharos Timelines with ShowRunner™:
150 +
151 +* If Scene Tracking is configured for a ShowRunner™ Area, the Pharos Timeline will be triggered regardless of whether any loads are assigned to the Area
152 +* Scene recalls are still executed even if Scene Tracking is enabled
153 +** Non-DMX loads in an area with Scene Tracking will still go to their predefined scene levels unless they are excluded from the scene
154 +** Pharos DMX loads will go to their predefined scene levels unless they are excluded from the scene, even if they are included in the Pharos Timeline being triggered
155 +* If Timelines are being used to control DMX fixtures, then the Fixture Groups do not actually need to be defined in ShowRunner™ unless direct control of the Fixture Groups is desired
148 148  )))