Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.12
edited by Alexander Mott
on 2023/05/05 18:39
Change comment: (Autosaved)
To version 1.15
edited by Alexander Mott
on 2023/05/05 18:54
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -10,6 +10,29 @@
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 in ShowRunner™ send group-level commands to Fixture Groups in Pharos
16 +* Scene recalls in ShowRunner™ can be made to trigger Timelines in Pharos
17 +* The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT
18 +** (((
19 +(% class="table-condensed" %)
20 +|(% style="width:244px" %)ShowRunner™ Load Type|(% style="width:244px" %)Pharos API Command
21 +|(% style="width:244px" %)Single-Channel|(% style="width:244px" %)Intensity
22 +|(% style="width:244px" %)RGB|(% style="width:244px" %)Intensity/RGB
23 +|(% style="width:244px" %)Dynamic White|(% style="width:244px" %)Intensity/CCT
24 +)))
25 +* The Pharos controller does any necessary processing to adapt these commands for the fixtures
26 +** For example,
27 +
28 +*
29 +
30 +* ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
31 +* Fixture Groups defined as single-channel loads in ShowRunner™
32 +* 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
33 +* Fixtures can belong to multiple Fixture Groups, allowing ShowRunner™ to send different types (e.g. RGB vs CCT) of command to the same fixture 
34 +** 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
35 +
13 13  The basic steps for creating a Pharos Project for use with ShowRunner™ are:
14 14  
15 15  1. Open the Pharos Designer 2 software
... ... @@ -18,7 +18,8 @@
18 18  1. Navigate to the "Project" page by clicking the Pharos logo on the left
19 19  1. Under the "Controller API" heading, verify that API Version 5.0 is selected
20 20  1. Navigate to the "Network" page by clicking the network icon on the left
21 -1. Select "Controller 1" and verify t
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
22 22  1. Navigate to the "Layout" page by clicking the pencil and ruler icon on the left
23 23  1. At the top left, click "Manage..." to edit the layout name and dimensions, modify grid settings, and upload a background image if desired
24 24  1. Locate the desired fixture in the Fixture Profile List on the right side of the Layout page
... ... @@ -25,13 +25,6 @@
25 25  1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles
26 26  1*. Pharos also has a large selection of manufacturer-specific profiles which can be used instead of the generics
27 27  1*. Additional generic and manufacturer-specific profiles can be downloaded by clicking the cloud icon on the right, above the fixture profile list
28 -1. Prior to adding fixtures to the layout, consider the following:
29 -1*. ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
30 -1*. The Pharos API limits commands to single-channel (intensity), RGB, or Intensity/CCT
31 -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
32 -1*. Fixtures can belong to multiple Fixture Groups
33 -1**. This allows ShowRunner™ to send different types of commands to the same fixtures
34 -1**. 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
35 35  1. Add fixtures to the layout by dragging them from the fixture profile list
36 36  1*. Every fixture that is added to the layout represents a unique set of DMX addresses
37 37  1*. The fixture number is different than the fixture address, and is automatically incremented by Pharos Designer 2
... ... @@ -42,7 +42,6 @@
42 42  1.
43 43  1. adsf
44 44  
45 -
46 46  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™
47 47  
48 48  = Device Configuration =