Changes for page Pharos Configuration

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (2 modified, 4 added, 0 removed)
  • network-project-assign_text_crop.png
  • network-project-usb_text_crop.png
  • lyout-2_text.png
  • network-project-find_text_crop.png
  • network-project-found_text_crop.png
  • patch-2_text.png

Details

Page properties

Content

...	...	@@ -4,6 +4,8 @@
4	4
5	5	ShowRunner™ can control DMX fixtures through several different methods, including Pharos DMX controllers. The most common Pharos controllers sold through Crestron are the Pharos LPC-1 (DIN-DMX-1UNIVERSE) and the Pharos LPC-2 (DIN-DMX-2UNIVERSE). These LPC controllers appear physically identical, but the LPC-1 shares a single universe across both DMX outputs while the LPC-2 has a separate universe for each output. ShowRunner™ uses the Pharos Controller API to send commands over Ethernet to the Pharos Controller, which then sends DMX commands to the fixtures.
6	6
	7	+This article covers the basics of Pharos Designer 2 for the purposes of integrating with ShowRunnerCLC™ installations. Further information can be found from the official[[ Pharos Designer 2 documentation>>https://dl.pharoscontrols.com/software_help/designer2/Default.htm]].
	8	+
7	7	= Pharos Projects =
8	8
9	9	ShowRunner™ integrates with Pharos LPC DMX controllers using the Pharos API. The ShowRunner™ configuration and the Pharos project loaded to the Pharos LPC need to be in coordination with each other in order for ShowRunner™ to control the DMX loads as expected. It is therefore sometimes necessary to either create or edit a Pharos project in order to determine how the DMX loads need to be defined in the ShowRunner™ configuration.
...	...	@@ -41,6 +41,8 @@
41	41	1. Select "Controller 1" and verify that the number of universes in the "Properties" menu matches the controller that was ordered for the job
42	42	1. If required, click the "New Controller..." button to add additional Pharos controllers
43	43	1. Navigate to the "Layout" page by clicking the pencil and ruler icon on the left
	46	+1*. Overview of completed layout:
	47	+1*. [[image:lyout-2_text.png]]
44	44	1. At the top left, click "Manage..." to edit the layout name and dimensions, modify grid settings, and upload a background image if desired
45	45	1. Locate the desired fixture in the Fixture Profile List on the right side of the Layout page
46	46	1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles
...	...	@@ -61,14 +61,29 @@
61	61	1**. Shift-dragging on the layout will select just the highlighted fixtures
62	62	1*. Fixtures can be removed from a group by right clicking them under the group in the Fixture List
63	63	1*. Fixtures can be added to an existing group by selecting and then dragging them to a group in the Fixture List
	68	+1*. **Note:** dragging a fixture from one group into another will not remove it from the first group, only add it to the second group. Be careful not to accidentally assign fixtures to more groups than intended.
64	64	1. Once all fixtures have been laid out and grouped, navigate to the "Patch" page
	70	+1*. Overview of a completed patch:
	71	+1*. [[image:patch-2_text.png]]
	72	+1. All fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
	73	+1*. All fixtures are present, regardless of grouping or which layout they appear on
	74	+1**. Fixtures will appear multiple times: once in the "All Fixtures" section, and then again in any groups that they are assigned to
	75	+1**. Patched fixtures have blue text, even if they are not patched to the currently visible universe
	76	+1**. Unpatched fixtures have black text
	77	+1**. The currently selected fixture has red text regardless of whether it is patched or not
	78	+1*. Current patching is viewed on the screen to the right
	79	+1**. By default, all universes on all controllers are shown
	80	+1**. Displayed universes can be narrowed down by selecting controllers and outputs from the list of controllers
	81	+1**. The currently selected fixture is highlighted in red in the fixture list and in blue if it is patched to the currently visible universe
65	65	1. Patch fixtures by dragging them from the fixture list onto the DMX universe
66		-1*. If there are multiple controllers on the job, make sure that the correct controller is selected
	83	+1*. If there are multiple controllers on the job, make sure that the correct controller and universe is selected and displayed on the right
67	67	1*. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
68	68	1*. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
69	69	1*. Fixtures can be unpatched by right clicking them in the universe
70	70	1. If desired, navigate to the "Timeline" page and create timelines
71	71
	89	+Discovering Pharos LPC controllers and uploading a project are covered in detail in the [[Pharos Configuration section>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Pharos Configuration.WebHome||anchor="HPharosConfiguration"]] below.
	90	+
72	72	== Editing an Existing Pharos Project ==
73	73
74	74	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:
...	...	@@ -75,7 +75,7 @@
75	75
76	76	* The version of Pharos Designer 2 is tied to the version of the Pharos controller firmware. Editing an existing project with a newer version of Designer 2 than the project was last saved in may result in the newly edited project no longer being able to be loaded to the controller without updating the controller firmware.
77	77	** To maintain full backwards compatibility with an existing installation, verify the controller's current firmware version and then download the corresponding version of Designer 2 from [[Pharos Controls' website>>https://www.pharoscontrols.com/support/designer/software-downloads/#software-archive]]
78		-* ShowRunner™ does not pay attention to how Pharos DMX fixtures are addressed, only how they are grouped
	97	+* ShowRunner™ does not pay attention to how Pharos DMX fixtures are addressed, only how they are grouped. Re-patching fixtures (changing their address) is covered in the [[Fixture Addressing and Identification section>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Pharos Configuration.WebHome||anchor="HFixtureAddressingandIdentification"]] below.
79	79	** 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™
80	80	** 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
81	81	** 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
...	...	@@ -114,8 +114,10 @@
114	114	1. Select a controller that is defined in the project
115	115	1. In the Properties menu on the right, click the Serial Number dropdown menu and select the SN corresponding to the controller
116	116	1*. [[image:network-project-assign_text_crop.png]]
117		-1*. If you do not see the corresponding serial number, click the "Find..." button
118		-1*. If you are connecting to the controller over a routed network, put the controller's IP address into this field
	136	+1*. If you do not see the corresponding serial number, click the "Find..." button to open the search menu
	137	+1**. [[image:network-project-find_text_crop.png]]
	138	+1*. If you are connecting to the controller over a routed network, put the controller's IP address into this field and press the "Add" button
	139	+1**. [[image:network-project-found_text_crop.png]]
119	119	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
120	120	1. If there are multiple controllers in the project, repeat step 6 for all controllers
121	121	1. Once all controllers defined in the project have been assigned a serial number, press the "Upload" button
...	...	@@ -129,6 +129,8 @@
129	129
130	130	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.
131	131
	153	+== Define Pharos Loads in ShowRunner™ ==
	154	+
132	132	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:
133	133
134	134	* Currently defined loads are shown in the list on the left
...	...	@@ -153,8 +153,10 @@
153	153	** 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
154	154	** The Area Assignment dictates what area the load will be associated with
155	155
156		-ShowRunner™ is also capable of triggering Timelines in the Pharos project. This can be configured using the XPanel UI:
	179	+== Scene Mapping ==
157	157
	181	+ShowRunner™ is also capable of triggering Timelines in the Pharos project by mapping Pharos Timelines to ShowRunner™ Scenes. This can be configured using the XPanel UI:
	182	+
158	158	1. Navigate to Settings > Load Hardware
159	159	1. Select the Pharos controller from the list of load controllers on the left
160	160	1. Press "Configure Scene Tracking"
...	...	@@ -170,14 +170,107 @@
170	170
171	171	Some things to consider if you are triggering Pharos Timelines with ShowRunner™:
172	172
	198	+* Since Scene Mapping will directly trigger Pharos Timelines, any Pharos fixture that is part of the Timeline will be affected
	199	+** Pharos Groups that are mapped to ShowRunner™ loads in other areas or Pharos Groups that are not defined in ShowRunner™ at all will still be affected if they are part of the Timeline
173	173	* 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
	201	+* If Scene Tracking is configured for a ShowRunner™ Area, then recalling //any// Scene on the Area will release (stop) //all// Timelines that are associated with the Area before triggering any new Timelines associated with the Scene
	202	+** If the Scene being recalled does not have any Timeline  associated with it, any Timelines associated with the area are still released
174	174	* Scene recalls are still executed even if Scene Tracking is enabled
175	175	** Non-DMX loads in an area with Scene Tracking will still go to their predefined scene levels unless they are excluded from the scene
176	176	** 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
177	177	* 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
178	178
179		-= Fixture Addressing =
	208	+= Fixture Addressing and Identification =
180	180
181		-Pharos Designer 2 has several features that make it relatively straightforward to address DMX fixtures, or to change how fixtures need to be addressed in order for the lighting controls to work correctly. Since ShowRunner™ uses fixture groups to send commands to DMX fixtures on the Pharos LPC, the specific fixture addresses do not matter as long as they are addressed according to the Pharos project. This means that if fixtures are re-patched to different addresses in the Pharos project but kept in the same fixture groups, then no changes to the ShowRunner™ configuration are necessary.
	210	+Pharos Designer 2 has several features that make it relatively straightforward to address DMX fixtures, or to change how fixtures need to be addressed in order for the lighting controls to work correctly.
182	182
183		-In addition to allowing the re-patching of fixtures, Pharos LPC have Remote Device Management (RDM) capabilities that allow for remotely addressing DMX fixtures provided the fixtures are RDM capable. See our [[DMX Fixture Addressing page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.DMX Fixture Addressing.WebHome]] for more general information regarding DMX networks and fixture addressing for non-RDM capable fixtues.
	212	+== Re-Patching Fixtures ==
	213	+
	214	+Since ShowRunner™ uses fixture groups to send commands to DMX fixtures on the Pharos LPC, the specific fixture universe and address does not matter as long as fixtures have been addressed according to the Pharos project. This means that if fixtures were installed and connected to a different universe than originally anticipated, it is relatively straightforward to re-patch fixtures to different addresses on different universes while maintaining their groups in the Pharos project without requiring changes to the ShowRunner™ configuration.
	215	+
	216	+In order to re-patch fixtures in the Pharos project:
	217	+
	218	+1. Open the project in Designer 2 and navigate to the "Patch" page
	219	+1*. All fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
	220	+1**. All fixtures are present, regardless of grouping or which layout they appear on
	221	+1**. Fixtures will appear multiple times: once in the "All Fixtures" section, and then again in any groups that they are assigned to
	222	+1**. Patched fixtures have blue text, even if they are not patched to the currently visible universe
	223	+1**. Unpatched fixtures have black text
	224	+1**. The currently selected fixture has red text regardless of whether it is patched or not
	225	+1*. Current patching is viewed on the screen to the right
	226	+1**. By default, all universes on all controllers are shown
	227	+1**. Displayed universes can be narrowed down by selecting controllers and outputs from the list of controllers
	228	+1**. The currently selected fixture is highlighted in red in the fixture list and in blue if it is patched to the currently visible universe
	229	+1. There are two options to patch or re-patch fixtures
	230	+1*. Drag the fixture from the list of fixtures on the left and onto the universe on the right
	231	+1*. Select a previously patched fixture from the universe on the right and move it to a new address, or right-click to un-patch entirely
	232	+1. When patching or re-patching fixtures, keep the following in mind:
	233	+1*. If there are controllers with multiple universes, or multiple controllers defined in the project, ensure that the fixtures are patched to the correct controller and universe
	234	+1*. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
	235	+1*. Fixtures can be unpatched by right clicking them in the universe
	236	+1*. Be wary of accidentally assigning fixtures to multiple groups when dragging them onto the universe to be patched
	237	+1. Be sure to re-upload the project to all controllers if patching has been modified for an existing project
	238	+
	239	+== Remote Device Management ==
	240	+
	241	+In addition to allowing the re-patching of fixtures, Pharos LPC have Remote Device Management (RDM) capabilities that allow for remotely addressing DMX fixtures provided the fixtures are RDM capable. More general information regarding DMX networks and methods for addressing non-RDM capable fixtures is available on our [[DMX Fixture Addressing page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.DMX Fixture Addressing.WebHome]].
	242	+
	243	+In order to perform RDM addressing in Pharos Designer 2:
	244	+
	245	+1. Ensure that the controller in the project you wish to address fixtures for has been assigned a live (currently online) controller and that the project has been uploaded to the live controller
	246	+1. Open the project in Designer 2 and navigate to the "Patch" page
	247	+1. Select the controller that you wish to address devices for
	248	+1. Press the "Discover" button that corresponds to the output that you want to address devices for
	249	+1*. Single-universe LPCs have separate "Discover" buttons corresponding to each of the two DMX outputs
	250	+1*. Multi-universe LPCs and EDNs typically have a single "Discover" button for each universe, as there is a 1-to-1 relationship between the output and the universe
	251	+1. A window will appear and list all discovered devices, along with a unique device ID, manufacturer/model information, personality (control mode), footprint (number of required addresses), and their current start address
	252	+1*. Due to manufacturer compatibility issues, some RDM-capable devices may not appear online, and available information (such as personality) may be incomplete for those devices that are online
	253	+1*. Non-driver devices (such as splitters) will appear in the list, but it will not be possible to change their start address
	254	+1*. In cases where RDM capable devices do not appear online, they must be addressed manually as described on our [[DMX Fixture Addressing page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.DMX Fixture Addressing.WebHome||anchor="HAddressingDrivers"]]
	255	+1. Click the "Identify" button and then select the device from the list of available devices in order to identify a specific RDM device
	256	+1*. The device should identify itself by flashing any attached loads (if a driver), or by flashing indicator LEDs (if it is another type of device, such as a splitter)
	257	+1. To change a device's start address, double-click its start address and type the new start address
	258	+1. Once all devices have been identified and re-addressed, click the "Discover" button to refresh the list and verify that no new devices appear online
	259	+1. Repeat steps 3 through 8 for all controllers
	260	+1. If discovering on all outputs of all controllers does not reveal all the expected drivers, then it may be necessary to manually address drivers as described on our [[DMX Fixture Addressing page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.DMX Fixture Addressing.WebHome||anchor="HAddressingDrivers"]] and move on to troubleshooting the DMX installation
	261	+
	262	+== Address Verification ==
	263	+
	264	+Once fixtures have been addressed, they can be verified using the ordinary ShowRunner™ load verification processes and tools. If fixtures are not behaving as expected, then it may be necessary to dig deeper and determine where the issue lies. To rule out or identify load configuration issues in ShowRunner™, first verify that fixtures are patched and grouped correctly in the Pharos project, and that the loads in ShowRunner™ are mapped to the correct groups in Pharos.
	265	+
	266	+If the Pharos project and ShowRunner™ configuration are determined to be in sync, then the next step is to verify that fixtures have been addressed correctly:
	267	+
	268	+1. Ensure that the controller in the project you wish to address fixtures for has been assigned a live (currently online) controller and that the project has been uploaded to the live controller
	269	+1. Open the project in Designer 2 and navigate to the "Layout" or "Patch" page
	270	+1*. (Layout page shown, but both pages have this capability)
	271	+1. Click the lightbulb icon on the top of the page
	272	+1. Select a fixture to begin flashing fixtures in the field
	273	+1*. Fixtures or entire fixture groups can be selected from the fixture hierarchy on the left
	274	+1*. On the Layout page, fixtures can also be selected from the layout
	275	+1*. On the Patch page, fixtures can be selected
	276	+1. If the wrong fixtures flash when the fixture or fixture group is identified in Pharos, then there is an issue with how the fixtures are addressed or patched
	277	+1. If the expected fixtures (and only the expected fixtures) flash when identified in Pharos, then fixtures have been addressed correctly
	278	+1. To stop identifying selected fixtures, click the lightbulb icon again
	279	+
	280	+The Pharos web UI can also be used as an alternative to Designer 2 in order to verify fixture addressing by parking and unparking individual channels from the "Output" tab. This method also enables you to verify that the correct fixture profiles have been assigned in the Pharos project by comparing the fixture behavior when individual channels are parked to the expected behavior based on the assigned fixture profile:
	281	+
	282	+1. Ensure that a project is loaded to the controller and then connect to it by entering the IP address into a web browser
	283	+1*. If you are connecting to a controller on a Control Subnet from the LAN side of the processor, input the processor's IP address along with the appropriate port. See our [[FAQ>>https://wiki.chiefintegrations.com/FAQ/I%20can%27t%20connect%20to%20my%20Pharos%20LPC%20on%20the%20Control%20Subnet]] for information
	284	+1. Navigate to the "Output" tab to see live outputs
	285	+1. At the top of the page, select the appropriate universe for controllers with multiple universes
	286	+1. All 512 channels in the selected universe
	287	+1*. Channels with fixtures patched to them appear in white, along with current output level
	288	+1*. Channels with no fixtures patched to them appear in gray
	289	+1*. Channels that are currently parked (overridden) appear in red
	290	+1*. Channels that are currently being used in a timeline or Pharos scene appear in yellow
	291	+1. In the "Park" section at the bottom, use the "Channels" and "Level" fields to override specific channels to a specific level
	292	+1*. Use commas and hyphens to select multiple or ranges of addresses
	293	+1*. Leaving the "Level" section blank will park the channels at 0
	294	+1*. Use tab, shift-tab, and enter to quickly navigate between and confirm fields in the "Park" and "Unpark" sections
	295	+1. In the "Unpark" section at the bottom, use the "Channel" field to release currently parked channels
	296	+1*. Use commas and hyphens to select multiple or ranges of addresses to unpark
	297	+1*. Use tab, shift-tab, and enter to quickly navigate between and confirm fields in the "Park" and "Unpark" sections
	298	+1. Parking channels is useful to verify fixtures have been addressed correctly
	299	+1*. Parking all channels at 0 and then parking individual channels or ranges of channels at 255 helps to verify that fixtures are addressed correctly and that there are not multiple fixtures that have been accidentally addressed alike
	300	+1*. Parking all of a fixture's channels at 0 and then individually parking individual channels at 255 helps to verify that the start address is correct and that the fixture type assigned in the project (RGBW, HSIC, IRGB, etc.) matches the actual behavior of the fixture
	301	+1. Always un-park all channels before disconnecting, as parked channels will not be affected by Pharos timelines and will not be controllable from ShowRunner™

network-project-assign_text_crop.png

Size

...	...	@@ -1,1 +1,1 @@
1		-82.6 KB
	1	+76.1 KB

Content

network-project-usb_text_crop.png

Size

...	...	@@ -1,1 +1,1 @@
1		-83.9 KB
	1	+47.5 KB

Content

lyout-2_text.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.alexander\.mott@chiefintegrations\.com

Size

...	...	@@ -1,0 +1,1 @@
	1	+177.3 KB

Content

network-project-find_text_crop.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.alexander\.mott@chiefintegrations\.com

Size

...	...	@@ -1,0 +1,1 @@
	1	+28.6 KB

Content

network-project-found_text_crop.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.alexander\.mott@chiefintegrations\.com

Size

...	...	@@ -1,0 +1,1 @@
	1	+97.6 KB

Content

patch-2_text.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.alexander\.mott@chiefintegrations\.com

Size

...	...	@@ -1,0 +1,1 @@
	1	+185.8 KB

Content