Changes for page Pharos Configuration

Summary

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

Details

Page properties

Content

...	...	@@ -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
	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.
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:
	120	+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
	122	+* 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
	125	+* 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,10 @@
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.
	144	+ShowRunner™ is also capable of triggering Timelines in the Pharos project. This can be configured using the XPanel UI:
145	145
	146	+1. Navigate to Settings > Load Configura
146	146
	148	+
147	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.
148	148	)))