Wiki source code of Pharos Configuration
Version 1.21 by Alexander Mott on 2023/05/05 19:24
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
1.1 | 1 | {{box cssClass="floatinginfobox" title="**CONTENTS**"}} |
2 | {{toc/}} | ||
3 | {{/box}} | ||
4 | |||
5 | (% class="row" %) | ||
6 | ((( | ||
7 | 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. | ||
8 | |||
9 | = Pharos Project = | ||
10 | |||
![]() |
1.2 | 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. |
![]() |
1.1 | 12 | |
![]() |
1.13 | 13 | When creating a Pharos project for a ShowRunner™ installation, there are several things to consider: |
14 | |||
![]() |
1.17 | 15 | * Individual loads defined in ShowRunner™ send commands to individual Fixture Groups in Pharos |
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 | ((( | ||
![]() |
1.16 | 19 | (% class="col-xs-8" %) |
20 | ((( | ||
![]() |
1.15 | 21 | (% class="table-condensed" %) |
![]() |
1.17 | 22 | |(% style="width:244px" %)**ShowRunner™ Load Type**|(% style="width:244px" %)**Pharos API Command** |
![]() |
1.15 | 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 | ))) | ||
![]() |
1.16 | 27 | ))) |
![]() |
1.15 | 28 | * The Pharos controller does any necessary processing to adapt these commands for the fixtures |
![]() |
1.17 | 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 |
![]() |
1.18 | 30 | ** Certain manufacturer-specific fixture Profiles exist in order to help the Pharos controller achieve a consistent output across multiple different fixture types |
![]() |
1.19 | 31 | * If it is desired to control the white channel separately from the RGB channels of an RGBW fixture, then it must be defined in the Pharos project as two separate RGB and W fixtures that are in different groups |
32 | * Individual Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types of command (e.g. RGB vs CCT) to the same fixture | ||
![]() |
1.13 | 33 | ** Useful for certain situations, such as HSIC fixtures that need to be controlled as color-changing (RGB) in some situations but dynamic white (intensity/CCT) in others |
![]() |
1.19 | 34 | ** In this scenario, one group would be defined in ShowRunner™ as an RGB load and one group would be defined as a Dynamic White load |
![]() |
1.13 | 35 | |
![]() |
1.19 | 36 | The basic steps for creating a Pharos Project for use with ShowRunner™ are as follows: |
![]() |
1.1 | 37 | |
![]() |
1.2 | 38 | 1. Open the Pharos Designer 2 software |
39 | 1. In the top-right, click "New Project" and select the type of Pharos controller that will be the primary controller | ||
40 | 1*. Crestron SKUs DIN-DMX-1UNIVERSE and DIN-DMX-2UNIVERSE both correspond to "LPC" in Pharos | ||
![]() |
1.4 | 41 | 1. Navigate to the "Project" page by clicking the Pharos logo on the left |
![]() |
1.3 | 42 | 1. Under the "Controller API" heading, verify that API Version 5.0 is selected |
![]() |
1.12 | 43 | 1. Navigate to the "Network" page by clicking the network icon on the left |
![]() |
1.13 | 44 | 1. Select "Controller 1" and verify that the number of universes in the "Properties" menu matches the controller that was ordered for the job |
45 | 1. If required, click the "New Controller..." button to add additional Pharos controllers | ||
![]() |
1.4 | 46 | 1. Navigate to the "Layout" page by clicking the pencil and ruler icon on the left |
![]() |
1.5 | 47 | 1. At the top left, click "Manage..." to edit the layout name and dimensions, modify grid settings, and upload a background image if desired |
![]() |
1.8 | 48 | 1. Locate the desired fixture in the Fixture Profile List on the right side of the Layout page |
49 | 1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles | ||
![]() |
1.4 | 50 | 1*. Additional generic and manufacturer-specific profiles can be downloaded by clicking the cloud icon on the right, above the fixture profile list |
![]() |
1.7 | 51 | 1. Add fixtures to the layout by dragging them from the fixture profile list |
52 | 1*. Every fixture that is added to the layout represents a unique set of DMX addresses | ||
![]() |
1.12 | 53 | 1*. The fixture number is different than the fixture address, and is automatically incremented by Pharos Designer 2 |
![]() |
1.19 | 54 | 1*. Fixture properties such as name, shape, and size can be edited using the menu on the right |
![]() |
1.12 | 55 | 1*. Right-clicking a fixture on the layout will allow you to either "Duplicate" or create a "New Instance" of a fixture |
56 | 1**. Duplicating a fixture creates a new fixture with the same profile and properties but that will occupy different DMX addresses | ||
![]() |
1.8 | 57 | 1**. Creating a New Instance will create a new representation of the fixture without actually creating a new fixture; this allows you to have multiple fixtures represented on the layout that share the same DMX address |
![]() |
1.21 | 58 | 1. Create a Fixture Group by right clicking an empty area in the fixture list and selecting the "New Group" option, or by |
![]() |
1.20 | 59 | 1. Select the fixtures you would like to be grouped together |
60 | 1*. Click a fixture on the layout or in the list of fixtures to select it | ||
![]() |
1.21 | 61 | 1*. Use ctrl+click to add or remove a fixture from the selection |
62 | 1*. Use ctrl+drag on the layout to add multiple fixtures to the selection | ||
63 | 1*. Use shift+drag on the layout to drop the current selection and select just the newly highlighted fixtures | ||
64 | 1. Creating a new group will au | ||
![]() |
1.1 | 65 | |
![]() |
1.6 | 66 | Note: Due to limitations with the API, only single channel, RGB, or Intensity/CCT load types can be defined in ShowRunner™. Other fixture types are controllable, but the types of command that ShowRunner™ |
![]() |
1.1 | 67 | |
68 | = Device Configuration = | ||
69 | |||
70 | = ShowRunner™ Configuration = | ||
71 | |||
![]() |
1.19 | 72 | no feedback from dmx |
![]() |
1.1 | 73 | |
74 | |||
75 | ))) |