Changes for page Pharos Configuration

Summary

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

Details

Page properties

Content

...	...	@@ -8,6 +8,8 @@
8	8
9	9	= Pharos Project =
10	10
	11	+== Creating a New Pharos Project for ShowRunner™ ==
	12	+
11	11	Pharos projects are created using the free Pharos Designer 2 software from Pharos Controls. When creating a project for use with ShowRunner™, ensure that API version 5.0 is selected for the project. Individual loads control from ShowRunner™ is achieved with group-level commands using the Pharos Controller API, so each Fixture Group defined in the Pharos Project should correspond to a single load in ShowRunner™. In addition to group-level commands, ShowRunner™ also supports mapping ShowRunner™ Scenes to Pharos Timelines.
12	12
13	13	When creating a Pharos project for a ShowRunner™ installation, there are several things to consider:
...	...	@@ -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
	19	+* The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT
	20	+** Other fixture profiles are still supported: the Pharos controller will do any necessary processing to adapt the commands to the fixtures
	21	+*** 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
	22	+*** 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
...	...	@@ -76,8 +76,23 @@
76	76	1*. Fixtures can be unpatched by right clicking them in the universe
77	77	1. If desired, navigate to the "Timeline" page and create timelines
78	78
79		-= Device Configuration =
	71	+== Editing an Existing Pharos Project ==
80	80
	73	+If modifications need to be made to a Pharos Project that is already working with ShowRunner™, there are some things that should be taken into consideration in order to avoid breaking the existing programming:
	74	+
	75	+* ShowRunner™ does not pay attention to how Pharos DMX fixtures are addressed, only how they are grouped
	76	+** ShowRunner™ provides direct control of Pharos fixture groups by their group ID. Avoid changing Pharos fixture groups or group numbers unless you are aware of how they are mapped in ShowRunner™
	77	+** Adding newly patched/addressed fixtures to existing groups that are mapped in ShowRunner™ will allow those fixtures to be controlled without adding them to the ShowRunner™ configuration
	78	+** Removing fixtures from existing groups that are mapped in ShowRunner™ will prevent those fixtures from being controlled unless they are also in another group that is mapped to a ShowRunner™ load
	79	+** Renumbering a group that is mapped to a load in ShowRunner™ will prevent ShowRunner™ from controlling that group, unless the new number is also mapped in ShowRunner™
	80	+** If a new group is created that has the same group ID as a group that is already mapped in ShowRunner™, then ShowRunner™ will control that new group using the old load unless the ShowRunner™ configuration is updated
	81	+* ShowRunner™ maps Scenes to Pharos Timelines by their timeline ID
	82	+** Avoid changing Pharos timeline IDs unless you are aware of how they are mapped in ShowRunner™
	83	+** If a new Timeline is added that replaces the ID of an old Timeline, then the scene mapping in ShowRunner™ needs to be updated to prevent the old ShowRunner™ Scene from triggering the new Timeline
	84	+** If an existing Timeline is deleted, it should be unmapped in ShowRunner™ to prevent errors when the mapped ShowRunner™ Scene is recalled
	85	+
	86	+= Pharos Configuration =
	87	+
81	81	ShowRunner™ must be able to communicate with the Pharos controller via Ethernet in order for control to work. Pharos controllers ship in DHCP mode by default, but they will sometimes fail to get an address if the controller is powered up before the DHCP server is running. If this happens, or if there is no DHCP server on the network, then it is necessary to configure the controller via USB:
82	82
83	83	1. Open Pharos Designer 2 or an existing Pharos project
...	...	@@ -113,7 +113,7 @@
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 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.
	123	+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. A video tutorial of setting up Pharos loads and configuring Scene Tracking is [[available on our YouTube channel>>https://www.youtube.com/watch?v=Y63C_vnATec&list=PLhxgcngAeiD_pCRxFDwX5eg0O56OjNdHf]].
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
...	...	@@ -158,7 +158,9 @@
158	158
159	159	Some things to consider if you are triggering Pharos Timelines with ShowRunner™:
160	160
161		-* Pharos Fixture Groups do not need to be defined in ShowRunner™ if Timelines are the only intended means of controlling the DMX fixtures
162		-* ShowRunner™ will still execute a scene recall even if the scene is mapped to a Pharos Timeline
163		-** Non-DMX loads in an area with Scene tracking configured will still go to their scene levels
	168	+* 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
	169	+* Scene recalls are still executed even if Scene Tracking is enabled
	170	+** Non-DMX loads in an area with Scene Tracking will still go to their predefined scene levels unless they are excluded from the scene
	171	+** 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
	172	+* 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
164	164	)))