Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 25.7
edited by Alexander Mott
on 2023/05/16 19:21
Change comment: (Autosaved)
To version 33.1
edited by Alexander Mott
on 2023/05/16 21:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -43,6 +43,8 @@
43 43  1. Select "Controller 1" and verify that the number of universes in the "Properties" menu matches the controller that was ordered for the job
44 44  1. If required, click the "New Controller..." button to add additional Pharos controllers
45 45  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]]
46 46  1. At the top left, click "Manage..." to edit the layout name and dimensions, modify grid settings, and upload a background image if desired
47 47  1. Locate the desired fixture in the Fixture Profile List on the right side of the Layout page
48 48  1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles
... ... @@ -63,13 +63,25 @@
63 63  1**. Shift-dragging on the layout will select just the highlighted fixtures
64 64  1*. Fixtures can be removed from a group by right clicking them under the group in the Fixture List
65 65  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.
66 66  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
67 67  1. Patch fixtures by dragging them from the fixture list onto the DMX universe
68 -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
69 69  1*. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
70 70  1*. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
71 71  1*. Fixtures can be unpatched by right clicking them in the universe
72 -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.
73 73  1. If desired, navigate to the "Timeline" page and create timelines
74 74  
75 75  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.
... ... @@ -185,26 +185,95 @@
185 185  
186 186  = Fixture Addressing and Identification =
187 187  
188 -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.
202 +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.
189 189  
190 -In order to re-patch fixtures:
204 +== Re-Patching Fixtures ==
191 191  
206 +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.
207 +
208 +In order to re-patch fixtures in the Pharos project:
209 +
192 192  1. Open the project in Designer 2 and navigate to the "Patch" page
193 -1. On this page, all fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
194 -1*. All fixtures are present, regardless of grouping or which layout they appear on
195 -1*. Fixtures will appear multiple times: once in the "All Fixtures" section, and again in any
196 -1*. If there are multiple controllers on the job, make sure that the correct controller is selected
197 -1*. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
211 +1*. All fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
212 +1**. All fixtures are present, regardless of grouping or which layout they appear on
213 +1**. Fixtures will appear multiple times: once in the "All Fixtures" section, and then again in any groups that they are assigned to
214 +1**. Patched fixtures have blue text, even if they are not patched to the currently visible universe
215 +1**. Unpatched fixtures have black text
216 +1**. The currently selected fixture has red text regardless of whether it is patched or not
217 +1*. Current patching is viewed on the screen to the right
218 +1**. By default, all universes on all controllers are shown
219 +1**. Displayed universes can be narrowed down by selecting controllers and outputs from the list of controllers
220 +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
221 +1. There are two options to patch or re-patch fixtures
222 +1*. Drag the fixture from the list of fixtures on the left and onto the universe on the right
223 +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
224 +1. When patching or re-patching fixtures, keep the following in mind:
225 +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
198 198  1*. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
199 199  1*. Fixtures can be unpatched by right clicking them in the universe
200 -1. Current patching is viewed on the screen to the right
201 -1. Re-upload the project to all controllers if patching has been modified for an existing project
228 +1*. Be wary of accidentally assigning fixtures to multiple groups when dragging them onto the universe to be patched
229 +1. Be sure to re-upload the project to all controllers if patching has been modified for an existing project
202 202  
203 -In order to perform RDM addressing:
231 +== Remote Device Management ==
204 204  
205 -* 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
206 -* Open the project in Designer 2 and navigate to the "Patch" page
233 +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]].
207 207  
208 -In order to verify addressing:
235 +In order to perform RDM addressing in Pharos Designer 2:
209 209  
210 -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.
237 +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
238 +1. Open the project in Designer 2 and navigate to the "Patch" page
239 +1. Select the controller that you wish to address devices for
240 +1. Press the "Discover" button that corresponds to the output that you want to address devices for
241 +1*. Single-universe LPCs have separate "Discover" buttons corresponding to each of the two DMX outputs
242 +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
243 +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
244 +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
245 +1*. Non-driver devices (such as splitters) will appear in the list, but it will not be possible to change their start address
246 +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"]]
247 +1. Click the "Identify" button and then select the device from the list of available devices in order to identify a specific RDM device
248 +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)
249 +1. To change a device's start address, double-click its start address and type the new start address
250 +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
251 +1. Repeat steps 3 through 8 for all controllers
252 +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
253 +
254 +== Address Verification ==
255 +
256 +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.
257 +
258 +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:
259 +
260 +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
261 +1. Open the project in Designer 2 and navigate to the "Layout" or "Patch" page
262 +1*. (Layout page shown, but both pages have this capability)
263 +1. Click the lightbulb icon on the top of the page
264 +1. Select a fixture to begin flashing fixtures in the field
265 +1*. Fixtures or entire fixture groups can be selected from the fixture hierarchy on the left
266 +1*. On the Layout page, fixtures can also be selected from the layout
267 +1*. On the Patch page, fixtures can be selected
268 +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
269 +1. If the expected fixtures (and only the expected fixtures) flash when identified in Pharos, then fixtures have been addressed correctly
270 +1. To stop identifying selected fixtures, click the lightbulb icon again
271 +
272 +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:
273 +
274 +1. Ensure that a project is loaded to the controller and then connect to it by entering the IP address into a web browser
275 +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
276 +1. Navigate to the "Output" tab to see live outputs
277 +1. At the top of the page, select the appropriate universe for controllers with multiple universes
278 +1. All 512 channels in the selected universe
279 +1*. Channels with fixtures patched to them appear in white, along with current output level
280 +1*. Channels with no fixtures patched to them appear in gray
281 +1*. Channels that are currently parked (overridden) appear in red
282 +1*. Channels that are currently being used in a timeline or Pharos scene appear in yellow
283 +1. In the "Park" section at the bottom, use the "Channels" and "Level" fields to override specific channels to a specific level
284 +1*. Use commas and hyphens to select multiple or ranges of addresses
285 +1*. Leaving the "Level" section blank will park the channels at 0
286 +1*. Use tab, shift-tab, and enter to quickly navigate between and confirm fields in the "Park" and "Unpark" sections
287 +1. In the "Unpark" section at the bottom, use the "Channel" field to release currently parked channels
288 +1*. Use commas and hyphens to select multiple or ranges of addresses to unpark
289 +1*. Use tab, shift-tab, and enter to quickly navigate between and confirm fields in the "Park" and "Unpark" sections
290 +1. Parking channels is useful to verify fixtures have been addressed correctly
291 +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
292 +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
293 +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 @@
1 -185.7 KB
1 +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