Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.41
edited by Alexander Mott
on 2023/05/05 21:10
Change comment: (Autosaved)
To version 1.16
edited by Alexander Mott
on 2023/05/05 18:59
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -12,28 +12,37 @@
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 -(((
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 +* (((
18 +The Pharos API limits group-level commands to intensity, intensity/RGB, and intensity/CCT* (((
19 19  (% class="col-xs-8" %)
20 20  (((
21 21  (% class="table-condensed" %)
22 -|(% style="width:244px" %)**ShowRunner™ Load Type**|(% style="width:244px" %)**Pharos API Command**
22 +|(% style="width:244px" %)ShowRunner™ Load Type|(% style="width:244px" %)Pharos API Command
23 23  |(% style="width:244px" %)Single-Channel|(% style="width:244px" %)Intensity
24 24  |(% style="width:244px" %)RGB|(% style="width:244px" %)Intensity/RGB
25 25  |(% style="width:244px" %)Dynamic White|(% style="width:244px" %)Intensity/CCT
26 26  )))
27 +
28 +(% class="row" %)
29 +(((
30 +
27 27  )))
32 +)))
33 +)))
28 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 
35 +** For example,
36 +
37 +*
38 +
39 +* ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
40 +* Fixture Groups defined as single-channel loads in ShowRunner™
41 +* 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
42 +* 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:
45 +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,92 +47,24 @@
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
59 +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 -1. Add fixtures to the layout by dragging them from the Fixture Profile List
61 +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
64 +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. Create Fixture Groups by clicking the folder icon above the Fixture List on the left or by right clicking an empty area in the Fixture List
59 -1*. Fixture Groups will correspond to individual loads in ShowRunner™
60 -1*. When a new Fixture Group is created, all currently selected fixtures are automatically added to the group
61 -1**. Clicking a fixture on the layout or in the fixture list will select just that fixture
62 -1**. Ctrl-clicking a fixture will add or remove it from the current selection
63 -1**. Ctrl-dragging on the layout will add multiple fixtures to the current selection
64 -1**. Shift-dragging on the layout will select just the highlighted fixtures
65 -1*. Fixtures can be removed from a group by right clicking them under the group in the Fixture List
66 -1*. Fixtures can be added to an existing group by selecting and then dragging them to a group in the Fixture List
67 -1. Once all fixtures have been laid out and grouped, navigate to the "Patch" page
68 -1. Patch fixtures by dragging them from the fixture list onto the DMX universe
69 -1*. If there are multiple controllers on the job, make sure that the correct controller is selected
70 -1*. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
71 -1*. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
72 -1*. Fixtures can be unpatched by right clicking them in the universe
73 -1. If desired, navigate to the "Timeline" page and create timelines
68 +1.
69 +1. adsf
74 74  
71 +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™
72 +
75 75  = Device Configuration =
76 76  
77 -ShowRunner™ must be able to communicate with the Pharos controller via Ethernet in order for control to work. Pharos controllers ship in DHCP mode by default, but they will sometimes fail to get an address if the controller is powered up before the DHCP server is running. If this happens, or if there is no DHCP server on the network, then it is necessary to configure the controller via USB:
78 -
79 -1. Open Pharos Designer 2 or an existing Pharos project
80 -1. Connect to the Pharos controller using the USB-B port on the front of the controller
81 -1. Navigate to the "Network" page
82 -1. Select the Pharos controller from the list
83 -1*. If a Pharos project is open, controllers defined in the project will be displayed above the list of online controllers
84 -1*. If there are multiple online controllers, use the "Beacon" function to flash all the LEDs on the front of the controller and verify the correct one is selected
85 -1. If the Pharos Designer 2 version is different than the firmware on the Pharos controller, then it is necessary to either update the controller by pressing the "Reload Firmware" button, or downgrade Pharos Designer 2 by downloading the appropriate version from Pharos Controls' website
86 -1. Press the "Configure" button to open the network configuration menu
87 -1. Set DHCP mode to Static and configure the IP address, IP mask, default gateway, and DNS servers as required for your network
88 -
89 -Once the Pharos controller is online, it is necessary to load the Pharos project to the controller:
90 -
91 -1. Open the Pharos project in Pharos Designer 2
92 -1. Connect to the network that the Pharos controller is on, or connect to the controller directly via USB
93 -1. Navigate to the "Network" page in Pharos Designer 2
94 -1. Verify that all online controllers have firmware that matches the version of Pharos Designer 2 you are running, and update them if necessary
95 -1*. Online controllers are displayed below the list of controllers that are defined in the project
96 -1*. If you do not see the controller online and you are hard-wired to the same network as the controller, verify that the controller has the correct IP settings
97 -1*. If the controller is on a Control Subnet and you are connecting via the LAN, [[verify that port forwarding has been configured>>https://wiki.chiefintegrations.com/FAQ/I%20can%27t%20connect%20to%20my%20Pharos%20LPC%20on%20the%20Control%20Subnet]] and proceed to the next step
98 -1*. If you do not see the controller online, but you are connecting to it over a routed network, proceed to the next step
99 -1. Select a controller that is defined in the project
100 -1. In the Properties menu on the right, click the Serial Number dropdown menu and select the SN corresponding to the controller
101 -1*. If you do not see the corresponding serial number, click the "Find..." button
102 -1*. If you are connecting to the controller over a routed network, put the controller's IP address into this field
103 -1*. If you are connecting to a controller on a Control Subnet from the LAN side of the processor, put the processor's LAN IP address followed by a colon and the external port number that corresponds to internal port 38008 of the controller. See our [[FAQ>>https://wiki.chiefintegrations.com/FAQ/I%20can%27t%20connect%20to%20my%20Pharos%20LPC%20on%20the%20Control%20Subnet]] for information
104 -1. If there are multiple controllers in the project, repeat step 6 for all controllers
105 -1. Once all controllers defined in the project have been assigned a serial number, press the "Upload" button
106 -1. Upload the project to individual controllers, or press the "Upload All" button to upload the project to all online controllers
107 -
108 -Pharos projects can also be loaded to controllers using the web interface, but in these cases it is still necessary to assign the Serial Number of the controller to the controller that is defined in the Pharos project. Additionally, the Pharos project must be exported for upload. See our [[FAQ>>https://wiki.chiefintegrations.com/FAQ/I%20can%27t%20load%20my%20Pharos%20project%20using%20the%20Pharos%20web%20interface]] for details.
109 -
110 110  = ShowRunner™ Configuration =
111 111  
112 -In order to control DMX fixtures on a Pharos controller with ShowRunner™, it is necessary to make sure that the ShowRunner™ configuration has the correct settings for the Pharos controller. Under the "LightingControllers" section of the ShowRunner™ configuration, locate the entry for the Pharos controller. Under the "Properties" section, verify that the "IpAddressOrHostname" matches the IP address or hostname of the Pharos controller. The "ApiPort" only needs to be changed if the HTTP port for the Pharos controller's web server has been changed from the default 80. Once the Properties for all Pharos controllers have been updated, load the configuration to the processor.
113 113  
114 -To add Pharos loads to ShowRunner™, launch the XPanel and navigate to the Settings > Load Configuration page and then select the Pharos controller from the list of controllers on the left. Once the controller is selected, press the "Configure Loads" button:
115 -
116 -* All currently defined loads are shown on the left
117 -** The "Group: #" of the load must match the group number as defined in the Pharos project
118 -* To add a new load to the controller, press "Add New Load" below the list of loads
119 -** The "Load Index/Channel" must match the group number as defined in the Pharos project
120 -*** Since ShowRunner™ uses group-level commands and fixtures in a group aren't necessarily on the same DMX universe, the "Universe ID" is grayed out and cannot be modified
121 -*** It is not possible to assign multiple Pharos groups to the same load, and it is not possible to assign multiple loads to the same group
122 -**** To have a single load in ShowRunner™ control multiple Pharos groups, create a new group in the Pharos project that contains the other groups and then associate the ShowRunner™ load with the super-group
123 -**** To have multiple ShowRunner™ loads control the same set of fixtures, create multiple groups in the Pharos project and assign the same fixtures to all groups (this is useful e.g. to allow ShowRunner™ to control an HSIC fixture using either RGB or dynamic white without needing to change the Load Type)
124 -** The "Load Type" does not need to strictly match the fixture type as defined in the Pharos project, as the Pharos controller will do its own processing to mix the DMX output to achieve the desired color
125 -*** "Single Channel" loads are interpreted by the Pharos as intensity only 
126 -**** Fixture profiles with a dedicated channel for intensity (IRGB, HSI, HSIC, ICHS, etc.) will only adjust the intensity channel, leaving the color and color temperature unchanged
127 -**** Fixture profiles without a dedicated intensity channel (RGB, RGBA, RGBW, etc.) will set all channels to the same intensity value sent by ShowRunner™
128 -*** "Dynamic White" loads are interpreted by the Pharos as an intensity and a color temperature
129 -**** Fixture profiles with dedicated intensity and color temperature (HSIC, ICHS, I/CCT, etc.) will use the values sent by ShowRunner™
130 -**** Pharos will attempt to mix the DMX output for fixture profiles without dedicated intensity and color temperature channels (warm/cool, RGBW, etc.) in order to match the values sent by ShowRunner™
131 -*** "RGB" loads are interpreted by the Pharos as an intensity + specific red, green, and blue values
132 -**** Fixture profiles with a dedicated channel for intensity (IRGB, HSI, HSIC, etc.) will use the load level sent by ShowRunner™ for intensity and then mix the other channels to match the RGB values
133 -**** Fixture profiles without a dedicated intensity channel (RGB, RGBW, etc.) will mix the intensities for each color to attempt to match the color and overall intensity sent by ShowRunner™
134 -** To control the white channel of RGBW fixtures separately from the RGB channels, the white
135 -
136 -
137 -note no feeback
78 +
138 138  )))