Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.30
edited by Alexander Mott
on 2023/05/05 20:09
Change comment: (Autosaved)
To version 1.40
edited by Alexander Mott
on 2023/05/05 21:05
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -93,13 +93,45 @@
93 93  1. Navigate to the "Network" page in Pharos Designer 2
94 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 95  1*. Online controllers are displayed below the list of controllers that are defined in the project
96 -1. Select the controller 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
97 97  
98 -If connecting to a Pharos controller located on the Control Subnet of a Crestron processor from the LAN side of the processor, then it is necessary to configure port forwarding on the processor before the project
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.
99 99  
100 100  = ShowRunner™ Configuration =
101 101  
102 -no feedback from dmx
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.
103 103  
104 -
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 ShowRunner™, 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 +** 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
122 +*** "Single Channel" loads are interpreted by the Pharos as intensity only 
123 +**** 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
124 +**** Fixture profiles without a dedicated intensity channel (RGB, RGBA, RGBW, etc.) will set all channels to the same intensity value sent by ShowRunner™
125 +*** "Dynamic White" loads are interpreted by the Pharos as an intensity and a color temperature
126 +**** Fixture profiles with dedicated intensity and color temperature (HSIC, ICHS, I/CCT, etc.) will use the values sent by ShowRunner™
127 +**** 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™
128 +*** "RGB" loads are interpreted by the Pharos as an intensity + specific red, green, and blue values
129 +**** 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
130 +**** 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™
131 +* 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
132 +** To have a single load in ShowRunner™ control multiple Pharos groups, it is necessary to create a group in the Pharos project that contains the other groups and then associate the ShowRunner™ load with the super-group
133 +** To have
134 +
135 +
136 +note no feeback
105 105  )))