Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 22.1
edited by Alexander Mott
on 2023/05/16 18:12
Change comment: There is no comment for this version
To version 14.2
edited by Alexander Mott
on 2023/05/16 17:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,8 +4,6 @@
4 4  
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]].
8 -
9 9  = Pharos Projects =
10 10  
11 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.
... ... @@ -69,11 +69,8 @@
69 69  1*. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
70 70  1*. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
71 71  1*. Fixtures can be unpatched by right clicking them in the universe
72 -1*. Patching and re-patching is covered in further detail in the [[Fixture Addressing and Identification section>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Pharos Configuration.WebHome||anchor="HFixtureAddressing"]] below.
73 73  1. If desired, navigate to the "Timeline" page and create timelines
74 74  
75 -Discovering Pharos LPC controllers and uploading a project are covered in detail in the [[Pharos Configuration section>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Pharos Configuration.WebHome||anchor="HPharosConfiguration"]] below.
76 -
77 77  == Editing an Existing Pharos Project ==
78 78  
79 79  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:
... ... @@ -101,7 +101,7 @@
101 101  1. Select the Pharos controller from the list
102 102  1*. If a Pharos project is open, controllers defined in the project will be displayed above the list of online controllers
103 103  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
104 -1*. [[image:network-project-usb_text_crop.png]]
99 +1*. [[image:network-project-usb_text_crop.png||height="474" width="1300"]]
105 105  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]]
106 106  1. Press the "Configure" button to open the network configuration menu
107 107  1. Set DHCP mode to Static and configure the IP address, IP mask, default gateway, and DNS servers as required for your network
... ... @@ -118,11 +118,10 @@
118 118  1*. If you do not see the controller online, but you are connecting to it over a routed network, proceed to the next step
119 119  1. Select a controller that is defined in the project
120 120  1. In the Properties menu on the right, click the Serial Number dropdown menu and select the SN corresponding to the controller
121 -1*. [[image:network-project-assign_text_crop.png]]
116 +1*. [[image:network-project-assign_text_crop.png||height="463" width="1300"]]
122 122  1*. If you do not see the corresponding serial number, click the "Find..." button to open the search menu
123 -1**. [[image:network-project-find_text_crop.png]]
118 +1**.
124 124  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
125 -1**. [[image:network-project-found_text_crop.png]]
126 126  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
127 127  1. If there are multiple controllers in the project, repeat step 6 for all controllers
128 128  1. Once all controllers defined in the project have been assigned a serial number, press the "Upload" button
... ... @@ -183,28 +183,8 @@
183 183  ** 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
184 184  * 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
185 185  
186 -= Fixture Addressing and Identification =
180 += Fixture Addressing =
187 187  
188 188  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.
189 189  
190 -In order to re-patch fixtures:
191 -
192 -1. Open the project in Designer 2 and navigate to the "Patch" page
193 -1. On this page, all fixtures and fixture groups in the project will appear in a hierarchical tree view on the left
194 -1*. All fixtures are present, regardless of grouping or which layout they appear on
195 -1*. Fixtures will appear multiple times: once in the "All Fixtures" section, and again in any
196 -1*. f there are multiple controllers on the job, make sure that the correct controller is selected
197 -1*. For controllers with multiple universes, ensure that the fixtures are patched to the correct universe
198 -1*. Fixtures can be patched to multiple addresses, but it is not possible to patch multiple fixtures to the same address
199 -1*. Fixtures can be unpatched by right clicking them in the universe
200 -1. Current patching is viewed on the screen to the right
201 -1. Re-upload the project to all controllers if patching has been modified for an existing project
202 -
203 -In order to perform RDM addressing:
204 -
205 -* Ensure that the controller in the project you wish to address fixtures for has been assigned a live (currently online) controller and that the project has been uploaded to the live controller
206 -* Open the project in Designer 2 and navigate to the "Patch" page
207 -
208 -In order to verify addressing:
209 -
210 -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 fixtures.
184 +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.
network-project-assign_text_crop.png
Size
... ... @@ -1,1 +1,1 @@
1 -76.1 KB
1 +82.6 KB
Content
network-project-find_text_crop.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -28.6 KB
Content
network-project-found_text_crop.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.alexander\.mott@chiefintegrations\.com
Size
... ... @@ -1,1 +1,0 @@
1 -97.6 KB
Content
network-project-usb_text_crop.png
Size
... ... @@ -1,1 +1,1 @@
1 -47.5 KB
1 +83.9 KB
Content