Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.17
edited by Alexander Mott
on 2023/05/05 19:04
Change comment: (Autosaved)
To version 1.10
edited by Alexander Mott
on 2023/05/05 18:29
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -10,28 +10,6 @@
10 10  
11 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.
12 12  
13 -When creating a Pharos project for a ShowRunner™ installation, there are several things to consider:
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 -* Fixture Groups defined as single-channel loads in ShowRunner™
31 -* 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
32 -* 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 -** 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 -
35 35  The basic steps for creating a Pharos Project for use with ShowRunner™ are:
36 36  
37 37  1. Open the Pharos Designer 2 software
... ... @@ -39,9 +39,6 @@
39 39  1*. Crestron SKUs DIN-DMX-1UNIVERSE and DIN-DMX-2UNIVERSE both correspond to "LPC" in Pharos
40 40  1. Navigate to the "Project" page by clicking the Pharos logo on the left
41 41  1. Under the "Controller API" heading, verify that API Version 5.0 is selected
42 -1. Navigate to the "Network" page by clicking the network icon on the left
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 -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 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,16 +48,26 @@
48 48  1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles
49 49  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
26 +1. Prior to adding fixtures to the layout, consider the following:
27 +1*. ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
28 +1*. The Pharos API limits commands to single-channel (intensity), RGB, or Intensity/CCT
29 +1*. 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
30 +1*. Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types of commands to the same fixtures
31 +1**. For example,
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 -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
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
34 +1*. Note that the fixture number is different than the fixture address, and is automatically incremented by Pharos Designer 2
35 +1*. Right-clicking a fixture on the layout will allow you to "Duplicate" or create a "New Instance" of a fixture
36 +1**. Duplicating a fixture creates a new fixture with the same profile and properties
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 58  1.
39 +1. When adding fixtures to the layout, keep in mind ShowRunner™ uses group-level controls
40 +1*. ShowRunner™ is only able to send RGB, single-channel, and intensity/CCT commands
41 +1*. Other fixture types (such as HSI, warm/cool, ICHS, etc.) still work correctly, but only RGB, single-channel, and intensity/CCT commands can be sent ot them
42 +1*. RGBW fixtures should be defined as separate RGB and W fixtures so that ShowRunner™ can control the white channel separately from the RGB channels
59 59  1. adsf
60 60  
45 +
61 61  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™
62 62  
63 63  = Device Configuration =