Changes for page Pharos Configuration

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -14,21 +14,15 @@
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
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
	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
	21	+* 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
	22	+** Add both a generic RGB fixture and a generic White fixture to the layout
	23	+** Assign each fixture to a different group
	24	+** Patch the RGB fixture
	25	+** 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
...	...	@@ -103,10 +103,60 @@
103	103	1*. If you are connecting to a controller on a Control Subnet from the LAN side of the processor, put the processor's LAN IP address followed by a colon and the external port number that corresponds to internal port 38008 of the controller. See our [[FAQ>>https://wiki.chiefintegrations.com/FAQ/I%20can%27t%20connect%20to%20my%20Pharos%20LPC%20on%20the%20Control%20Subnet]] for information
104	104	1. If there are multiple controllers in the project, repeat step 6 for all controllers
105	105	1. Once all controllers defined in the project have been assigned a serial number, press the "Upload" button
	100	+1. Upload the project to individual controllers, or press the "Upload All" button to upload the project to all online controllers
106	106
	102	+Pharos projects can also be loaded to controllers using the web interface, but in these cases it is still necessary to assign the Serial Number of the controller to the controller that is defined in the Pharos project. Additionally, the Pharos project must be exported for upload. See our [[FAQ>>https://wiki.chiefintegrations.com/FAQ/I%20can%27t%20load%20my%20Pharos%20project%20using%20the%20Pharos%20web%20interface]] for details.
	103	+
107	107	= ShowRunner™ Configuration =
108	108
109		-no feedback from dmx
	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.
110	110
111		-
	108	+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.
	109	+
	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:
	111	+
	112	+* Currently defined loads are shown in the list on the left
	113	+** The "Group: #" of the load must match the group number as defined in the Pharos project
	114	+** 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
	115	+* Press "Add New Load" below the list of loads to create a new load
	116	+** The "Load Index/Channel" must match the group number as defined in the Pharos project
	117	+*** 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
	118	+*** 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
	119	+**** To have a single load in ShowRunner™ control multiple Pharos groups, create a new group in the Pharos project that contains the other groups and then associate the ShowRunner™ load with the super-group
	120	+**** To have multiple ShowRunner™ loads control the same set of fixtures, create multiple groups in the Pharos project and assign the same fixtures to all groups (this is useful e.g. to allow ShowRunner™ to control an HSIC fixture using either RGB or dynamic white without needing to change the Load Type)
	121	+** The "Load Type" does not need to strictly match the fixture type as defined in the Pharos project, as the Pharos controller will do its own processing to mix the DMX output to achieve the desired color
	122	+*** "Single Channel" loads are interpreted by the Pharos as intensity only
	123	+**** Fixture profiles with a dedicated channel for intensity (IRGB, HSI, HSIC, ICHS, etc.) will only adjust the intensity channel, leaving the color and color temperature unchanged
	124	+**** Fixture profiles without a dedicated intensity channel (RGB, RGBA, RGBW, etc.) will set all channels to the same intensity value sent by ShowRunner™
	125	+*** "Dynamic White" loads are interpreted by the Pharos as an intensity and a color temperature
	126	+**** Fixture profiles with dedicated intensity and color temperature (HSIC, ICHS, I/CCT, etc.) will use the values sent by ShowRunner™
	127	+**** Pharos will attempt to mix the DMX output for fixture profiles without dedicated intensity and color temperature channels (warm/cool, RGBW, etc.) in order to match the values sent by ShowRunner™
	128	+*** "RGB" loads are interpreted by the Pharos as an intensity + specific red, green, and blue values
	129	+**** 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
	130	+**** 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™
	131	+** 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
	132	+** The Area Assignment dictates what area the load will be associated with
	133	+
	134	+ShowRunner™ is also capable of triggering Timelines in the Pharos project. This can be configured using the XPanel UI:
	135	+
	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
	148	+
	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
112	112	)))