Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 17.2
edited by Alexander Mott
on 2023/05/16 17:34
Change comment: There is no comment for this version
To version 6.1
edited by Alexander Mott
on 2023/05/09 21:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -2,17 +2,15 @@
2 2  {{toc/}}
3 3  {{/box}}
4 4  
5 +(% class="row" %)
6 +(((
5 5  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.
6 6  
7 -This article covers the basics of Pharos Designer 2 for the purposes of integrating with ShowRunnerCLC™ installations. Further information can be found from the official[[ Pharos Designer 2 documentation>>https://dl.pharoscontrols.com/software_help/designer2/Default.htm]].
9 += Pharos Project =
8 8  
9 -= Pharos Projects =
10 -
11 -ShowRunner™ integrates with Pharos LPC DMX controllers using the Pharos API. The ShowRunner™ configuration and the Pharos project loaded to the Pharos LPC need to be in coordination with each other in order for ShowRunner™ to control the DMX loads as expected. It is therefore sometimes necessary to either create or edit a Pharos project in order to determine how the DMX loads need to be defined in the ShowRunner™ configuration.
12 -
13 13  == Creating a New Pharos Project for ShowRunner™ ==
14 14  
15 -Pharos projects are created using the free [[Pharos Designer 2 software>>https://www.pharoscontrols.com/support/designer/software-downloads/]] 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.
13 +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.
16 16  
17 17  When creating a Pharos project for a ShowRunner™ installation, there are several things to consider:
18 18  
... ... @@ -34,7 +34,6 @@
34 34  The basic steps for creating a Pharos Project for use with ShowRunner™ are as follows:
35 35  
36 36  1. Open the Pharos Designer 2 software
37 -1*. Note that the version of Designer 2 lines up with the version of the Pharos controller firmware, and that any project that is created or edited in one version of Designer 2 will not necessarily be able to be loaded to a controller that is running older firmware without first updating the firmware
38 38  1. In the top-right, click "New Project" and select the type of Pharos controller that will be the primary controller
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
... ... @@ -75,8 +75,6 @@
75 75  
76 76  If modifications need to be made to a Pharos Project that is already working with ShowRunner™, there are some things that should be taken into consideration in order to avoid breaking the existing programming:
77 77  
78 -* The version of Pharos Designer 2 is tied to the version of the Pharos controller firmware. Editing an existing project with a newer version of Designer 2 than the project was last saved in may result in the newly edited project no longer being able to be loaded to the controller without updating the controller firmware.
79 -** To maintain full backwards compatibility with an existing installation, verify the controller's current firmware version and then download the corresponding version of Designer 2 from [[Pharos Controls' website>>https://www.pharoscontrols.com/support/designer/software-downloads/#software-archive]]
80 80  * ShowRunner™ does not pay attention to how Pharos DMX fixtures are addressed, only how they are grouped
81 81  ** ShowRunner™ provides direct control of Pharos fixture groups by their group ID. Avoid changing Pharos fixture groups or group numbers unless you are aware of how they are mapped in ShowRunner™
82 82  ** Adding newly patched/addressed fixtures to existing groups that are mapped in ShowRunner™ will allow those fixtures to be controlled without adding them to the ShowRunner™ configuration
... ... @@ -98,8 +98,7 @@
98 98  1. Select the Pharos controller from the list
99 99  1*. If a Pharos project is open, controllers defined in the project will be displayed above the list of online controllers
100 100  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
101 -1*. [[image:network-project-usb_text_crop.png]]
102 -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>>https://www.pharoscontrols.com/support/designer/software-downloads/#software-archive]]
96 +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
103 103  1. Press the "Configure" button to open the network configuration menu
104 104  1. Set DHCP mode to Static and configure the IP address, IP mask, default gateway, and DNS servers as required for your network
105 105  
... ... @@ -115,10 +115,8 @@
115 115  1*. If you do not see the controller online, but you are connecting to it over a routed network, proceed to the next step
116 116  1. Select a controller that is defined in the project
117 117  1. In the Properties menu on the right, click the Serial Number dropdown menu and select the SN corresponding to the controller
118 -1*. [[image:network-project-assign_text_crop.png]]
119 -1*. If you do not see the corresponding serial number, click the "Find..." button to open the search menu
120 -1**.
121 -1*. If you are connecting to the controller over a routed network, put the controller's IP address into this field and press the "Add" button
112 +1*. If you do not see the corresponding serial number, click the "Find..." button
113 +1*. If you are connecting to the controller over a routed network, put the controller's IP address into this field
122 122  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
123 123  1. If there are multiple controllers in the project, repeat step 6 for all controllers
124 124  1. Once all controllers defined in the project have been assigned a serial number, press the "Upload" button
... ... @@ -178,9 +178,4 @@
178 178  ** Non-DMX loads in an area with Scene Tracking will still go to their predefined scene levels unless they are excluded from the scene
179 179  ** Pharos DMX loads will go to their predefined scene levels unless they are excluded from the scene, even if they are included in the Pharos Timeline being triggered
180 180  * If Timelines are being used to control DMX fixtures, then the Fixture Groups do not actually need to be defined in ShowRunner™ unless direct control of the Fixture Groups is desired
181 -
182 -= Fixture Addressing =
183 -
184 -Pharos Designer 2 has several features that make it relatively straightforward to address DMX fixtures, or to change how fixtures need to be addressed in order for the lighting controls to work correctly. Since ShowRunner™ uses fixture groups to send commands to DMX fixtures on the Pharos LPC, the specific fixture addresses do not matter as long as they are addressed according to the Pharos project. This means that if fixtures are re-patched to different addresses in the Pharos project but kept in the same fixture groups, then no changes to the ShowRunner™ configuration are necessary.
185 -
186 -In addition to allowing the re-patching of fixtures, Pharos LPC have Remote Device Management (RDM) capabilities that allow for remotely addressing DMX fixtures provided the fixtures are RDM capable. See our [[DMX Fixture Addressing page>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Device Addressing.DMX Fixture Addressing.WebHome]] for more general information regarding DMX networks and fixture addressing for non-RDM capable fixtues.
173 +)))
network-project-assign_text_crop.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -76.1 KB
Content
network-project-usb_text_crop.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -47.5 KB
Content