Changes for page Pharos Configuration

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

From 25.4 to 25.5

From version 25.5

edited by Alexander Mott
on 2023/05/16 19:11

Change comment: (Autosaved)

To version 37.1

edited by Alexander Mott
on 2024/02/26 15:10

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (1 modified, 1 added, 0 removed)
- patch-2_text.png
- lyout-2_text.png

Details

Page properties

Content

@@ -43,6 +43,8 @@
 . Select "Controller 1" and verify that the number of universes in the "Properties" menu matches the controller that was ordered for the job
 . If required, click the "New Controller..." button to add additional Pharos controllers
 . Navigate to the "Layout" page by clicking the pencil and ruler icon on the left
++1*. Overview of completed layout:
++1*. [[image:lyout-2_text.png]]
 . At the top left, click "Manage..." to edit the layout name and dimensions, modify grid settings, and upload a background image if desired
 . Locate the desired fixture in the Fixture Profile List on the right side of the Layout page
 *. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles
@@ -63,13 +63,25 @@
 **. Shift-dragging on the layout will select just the highlighted fixtures
 *. Fixtures can be removed from a group by right clicking them under the group in the Fixture List
 *. Fixtures can be added to an existing group by selecting and then dragging them to a group in the Fixture List
++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.
 . Once all fixtures have been laid out and grouped, navigate to the "Patch" page
++1*. Overview of a completed patch:
++1*. [[image:patch-2_text.png]]
++1. All fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
++1*. All fixtures are present, regardless of grouping or which layout they appear on
++1**. Fixtures will appear multiple times: once in the "All Fixtures" section, and then again in any groups that they are assigned to
++1**. Patched fixtures have blue text, even if they are not patched to the currently visible universe
++1**. Unpatched fixtures have black text
++1**. The currently selected fixture has red text regardless of whether it is patched or not
++1*. Current patching is viewed on the screen to the right
++1**. By default, all universes on all controllers are shown
++1**. Displayed universes can be narrowed down by selecting controllers and outputs from the list of controllers
++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
 . Patch fixtures by dragging them from the fixture list onto the DMX universe
--1*. If there are multiple controllers on the job, make sure that the correct controller is selected
++1*. If there are multiple controllers on the job, make sure that the correct controller and universe is selected and displayed on the right
 *. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
 *. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
 *. Fixtures can be unpatched by right clicking them in the universe
--1*. Patching and re-patching is covered in further detail in the [[Fixture Addressing and Identification section>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Pharos Configuration.WebHome||anchor="HFixtureAddressingandIdentification"]] below.
 . If desired, navigate to the "Timeline" page and create timelines
  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.
@@ -136,6 +136,8 @@
  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.
++== Define Pharos Loads in ShowRunner™ ==
++
  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:
  * Currently defined loads are shown in the list on the left
@@ -160,8 +160,10 @@
  ** 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
  ** The Area Assignment dictates what area the load will be associated with
--ShowRunner™ is also capable of triggering Timelines in the Pharos project. This can be configured using the XPanel UI:
++== Scene Mapping ==
++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:
++
 . Navigate to Settings > Load Hardware
 . Select the Pharos controller from the list of load controllers on the left
 . Press "Configure Scene Tracking"
@@ -177,7 +177,11 @@
  Some things to consider if you are triggering Pharos Timelines with ShowRunner™:
++* Since Scene Mapping will directly trigger Pharos Timelines, any Pharos fixture that is part of the Timeline will be affected
++** 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
  * 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
++* 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
++** If the Scene being recalled does not have any Timeline  associated with it, any Timelines associated with the area are still released
  * Scene recalls are still executed even if Scene Tracking is enabled
  ** Non-DMX loads in an area with Scene Tracking will still go to their predefined scene levels unless they are excluded from the scene
  ** 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
@@ -185,26 +185,95 @@
  = Fixture Addressing and Identification =
--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.
++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.
--In order to re-patch fixtures:
++== Re-Patching Fixtures ==
++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.
++
++In order to re-patch fixtures in the Pharos project:
++
 . Open the project in Designer 2 and navigate to the "Patch" page
--1. On this page, all fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
--1*. All fixtures are present, regardless of grouping or which layout they appear on
--1*. Fixtures will appear multiple times: once in the "All Fixtures" section, and again in any
--1*. If there are multiple controllers on the job, make sure that the correct controller is selected
--1*. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
++1*. All fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
++1**. All fixtures are present, regardless of grouping or which layout they appear on
++1**. Fixtures will appear multiple times: once in the "All Fixtures" section, and then again in any groups that they are assigned to
++1**. Patched fixtures have blue text, even if they are not patched to the currently visible universe
++1**. Unpatched fixtures have black text
++1**. The currently selected fixture has red text regardless of whether it is patched or not
++1*. Current patching is viewed on the screen to the right
++1**. By default, all universes on all controllers are shown
++1**. Displayed universes can be narrowed down by selecting controllers and outputs from the list of controllers
++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
++1. There are two options to patch or re-patch fixtures
++1*. Drag the fixture from the list of fixtures on the left and onto the universe on the right
++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
++1. When patching or re-patching fixtures, keep the following in mind:
++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
 *. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
 *. Fixtures can be unpatched by right clicking them in the universe
--1. Current patching is viewed on the screen to the right
--1. Re-upload the project to all controllers if patching has been modified for an existing project
++1*. Be wary of accidentally assigning fixtures to multiple groups when dragging them onto the universe to be patched
++1. Be sure to re-upload the project to all controllers if patching has been modified for an existing project
--In order to perform RDM addressing:
++== Remote Device Management ==
--* 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
--* Open the project in Designer 2 and navigate to the "Patch" page
++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]].
--In order to verify addressing:
++In order to perform RDM addressing in Pharos Designer 2:
--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 fixtures.
++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
++1. Open the project in Designer 2 and navigate to the "Patch" page
++1. Select the controller that you wish to address devices for
++1. Press the "Discover" button that corresponds to the output that you want to address devices for
++1*. Single-universe LPCs have separate "Discover" buttons corresponding to each of the two DMX outputs
++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
++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
++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
++1*. Non-driver devices (such as splitters) will appear in the list, but it will not be possible to change their start address
++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"]]
++1. Click the "Identify" button and then select the device from the list of available devices in order to identify a specific RDM device
++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)
++1. To change a device's start address, double-click its start address and type the new start address
++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
++1. Repeat steps 3 through 8 for all controllers
++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
++
++== Address Verification ==
++
++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.
++
++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:
++
++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
++1. Open the project in Designer 2 and navigate to the "Layout" or "Patch" page
++1*. (Layout page shown, but both pages have this capability)
++1. Click the lightbulb icon on the top of the page
++1. Select a fixture to begin flashing fixtures in the field
++1*. Fixtures or entire fixture groups can be selected from the fixture hierarchy on the left
++1*. On the Layout page, fixtures can also be selected from the layout
++1*. On the Patch page, fixtures can be selected
++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
++1. If the expected fixtures (and only the expected fixtures) flash when identified in Pharos, then fixtures have been addressed correctly
++1. To stop identifying selected fixtures, click the lightbulb icon again
++
++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:
++
++1. Ensure that a project is loaded to the controller and then connect to it by entering the IP address into a web browser
++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
++1. Navigate to the "Output" tab to see live outputs
++1. At the top of the page, select the appropriate universe for controllers with multiple universes
++1. All 512 channels in the selected universe
++1*. Channels with fixtures patched to them appear in white, along with current output level
++1*. Channels with no fixtures patched to them appear in gray
++1*. Channels that are currently parked (overridden) appear in red
++1*. Channels that are currently being used in a timeline or Pharos scene appear in yellow
++1. In the "Park" section at the bottom, use the "Channels" and "Level" fields to override specific channels to a specific level
++1*. Use commas and hyphens to select multiple or ranges of addresses
++1*. Leaving the "Level" section blank will park the channels at 0
++1*. Use tab, shift-tab, and enter to quickly navigate between and confirm fields in the "Park" and "Unpark" sections
++1. In the "Unpark" section at the bottom, use the "Channel" field to release currently parked channels
++1*. Use commas and hyphens to select multiple or ranges of addresses to unpark
++1*. Use tab, shift-tab, and enter to quickly navigate between and confirm fields in the "Park" and "Unpark" sections
++1. Parking channels is useful to verify fixtures have been addressed correctly
++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
++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
++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™

patch-2_text.png

Size

@@ -1,1 +1,1 @@
--185.7 KB
++185.8 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