Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 1.31
edited by Alexander Mott
on 2023/05/05 20:14
Change comment: (Autosaved)
To version 1.38
edited by Alexander Mott
on 2023/05/05 20:54
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -97,14 +97,35 @@
97 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 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 99  1. Select a controller that is defined in the project
100 -1. In the Properties menu on the right, assign the Serial Number to the controller
101 -1*. If
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
102 102  
103 -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.
104 104  
105 105  = ShowRunner™ Configuration =
106 106  
107 -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.
108 108  
109 -
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 +** 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
119 +*** "Single Channel" loads are interpreted by the Pharos as intensity only 
120 +**** Fixture profiles with a dedicated channel for intensity (IRGB, HSI, HSIC, ICHS, etc.) will only adjust the intensity, leaving the color and color temperature unchanged
121 +**** Fixture profiles without a dedicated intensity channel (RGB, RGBA, RGBW, etc.) will set all channels to the same intensity
122 +*** "Dynamic White" loads are interpreted by the Pharos as an intensity and a color temperature
123 +****
124 +*** "RGB" loads are interpreted by the Pharos as a specific color value
125 +* 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
126 +** 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
127 +** To have
128 +
129 +
130 +note no feeback
110 110  )))