Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10

From version 1.41
edited by Alexander Mott
on 2023/05/05 21:10
Change comment: (Autosaved)
To version 1.43
edited by Alexander Mott
on 2023/05/05 21:20
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -28,7 +28,11 @@
28 28  * The Pharos controller does any necessary processing to adapt these commands for the fixtures
29 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 30  ** Certain manufacturer-specific fixture Profiles exist in order to help the Pharos controller achieve a consistent output across multiple different fixture types
31 -* If it is desired to control the white channel separately from the RGB channels of an RGBW fixture, then it must be defined in the Pharos project as two separate RGB and W fixtures that are in different groups
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 +** Add both a generic RGB fixture and a generic White fixture to the layout
33 +** Assign each fixture to a different group
34 +** Patch the RGB fixture
35 +** Patch the White fixture immediately following the RGB fixture (e.g., if the RGB is at address 1, patch the White fixture to address 4)
32 32  * Individual Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types of command (e.g. RGB vs CCT) to the same fixture 
33 33  ** Useful for certain situations, such as HSIC fixtures that need to be controlled as color-changing (RGB) in some situations but dynamic white (intensity/CCT) in others
34 34  ** In this scenario, one group would be defined in ShowRunner™ as an RGB load and one group would be defined as a Dynamic White load
... ... @@ -115,6 +115,7 @@
115 115  
116 116  * All currently defined loads are shown on the left
117 117  ** The "Group: #" of the load must match the group number as defined in the Pharos project
122 +** It is not possible to change the group of an existing load from the XPanel UI. Instead, either pull the config and edit the "LoadBaseIndex" property of the load
118 118  * To add a new load to the controller, press "Add New Load" below the list of loads
119 119  ** The "Load Index/Channel" must match the group number as defined in the Pharos project
120 120  *** 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
... ... @@ -131,7 +131,8 @@
131 131  *** "RGB" loads are interpreted by the Pharos as an intensity + specific red, green, and blue values
132 132  **** Fixture profiles with a dedicated channel for intensity (IRGB, HSI, HSIC, etc.) will use the load level sent by ShowRunner™ for intensity and then mix the other channels to match the RGB values
133 133  **** Fixture profiles without a dedicated intensity channel (RGB, RGBW, etc.) will mix the intensities for each color to attempt to match the color and overall intensity sent by ShowRunner™
134 -** To control the white channel of RGBW fixtures separately from the RGB channels, the white
139 +** 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
140 +** The Area Assignment dictates what area the load will be associated with
135 135  
136 136  
137 137  note no feeback