Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.20
edited by Alexander Mott
on 2023/05/05 19:19
Change comment: (Autosaved)
To version 1.13
edited by Alexander Mott
on 2023/05/05 18:44
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -12,28 +12,14 @@
12 12  
13 13  When creating a Pharos project for a ShowRunner™ installation, there are several things to consider:
14 14  
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 -(((
19 -(% class="col-xs-8" %)
20 -(((
21 -(% class="table-condensed" %)
22 -|(% style="width:244px" %)**ShowRunner™ Load Type**|(% style="width:244px" %)**Pharos API Command**
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 -)))
27 -)))
28 -* The Pharos controller does any necessary processing to adapt these commands for the fixtures
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
30 -** Certain manufacturer-specific fixture Profiles exist in order to help the Pharos controller achieve a consistent output across multiple different fixture types
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 
15 +* The Pharos API limits commands to single-channel (intensity), RGB, and intensity/CCT
16 +* ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
17 +* Fixture Groups defined as single-channel loads in ShowRunner™
18 +* For RGBW fixtures, it may be a good idea to define them as separate RGB and W fixtures so that ShowRunner™ is able to control the white channel separately from the RGB channels
19 +* Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types (e.g. RGB vs CCT) of command to the same fixture 
33 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
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
35 35  
36 -The basic steps for creating a Pharos Project for use with ShowRunner™ are as follows:
22 +The basic steps for creating a Pharos Project for use with ShowRunner™ are:
37 37  
38 38  1. Open the Pharos Designer 2 software
39 39  1. In the top-right, click "New Project" and select the type of Pharos controller that will be the primary controller
... ... @@ -47,22 +47,19 @@
47 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
48 48  1. Locate the desired fixture in the Fixture Profile List on the right side of the Layout page
49 49  1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles
36 +1*. Pharos also has a large selection of manufacturer-specific profiles which can be used instead of the generics
50 50  1*. Additional generic and manufacturer-specific profiles can be downloaded by clicking the cloud icon on the right, above the fixture profile list
51 51  1. Add fixtures to the layout by dragging them from the fixture profile list
52 52  1*. Every fixture that is added to the layout represents a unique set of DMX addresses
53 53  1*. The fixture number is different than the fixture address, and is automatically incremented by Pharos Designer 2
54 -1*. Fixture properties such as name, shape, and size can be edited using the menu on the right
41 +1*. Fixture properties such as name, shape, and size can be edited
55 55  1*. Right-clicking a fixture on the layout will allow you to either "Duplicate" or create a "New Instance" of a fixture
56 56  1**. Duplicating a fixture creates a new fixture with the same profile and properties but that will occupy different DMX addresses
57 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
58 -1. Select the fixtures you would like to be grouped together 
59 -1*. Click a fixture on the layout or in the list of fixtures to select it
60 -1*. Hold Ctrl while clicking on fixtures to add or remove them from the selection
61 -1*. Ctrl+click will add or remove a fixture from the selection
62 -1*. While holding the Ctrl key, click on fixtures in the list of fixtures on the left or on the layout to select them
63 -1*. Clicking fixtures w
45 +1.
64 64  1. adsf
65 65  
48 +
66 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™
67 67  
68 68  = Device Configuration =
... ... @@ -69,7 +69,6 @@
69 69  
70 70  = ShowRunner™ Configuration =
71 71  
72 -no feedback from dmx
73 73  
74 74  
75 75  )))