Changes for page Pharos Configuration

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -12,28 +12,19 @@
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		-(((
19		-(% class="col-xs-8" %)
20		-(((
21		-(% class="table-condensed" %)
22		-|(% style="width:244px" %)**ShowRunner™ Load Type**|(% style="width:244px" %)**Pharos API Command**
23		-|(% style="width:244px" %)Single-Channel|(% style="width:244px" %)Intensity
24		-|(% style="width:244px" %)RGB|(% style="width:244px" %)Intensity/RGB
25		-|(% style="width:244px" %)Dynamic White|(% style="width:244px" %)Intensity/CCT
26		-)))
27		-)))
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
	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	+* The Pharos API limits group-level commands to single-channel (intensity), RGB, and intensity/CCT
	18	+** The Pharos c
	19	+* The Pharos Controller does all the processing necessary to adapt an API command to the appropriate DMX outputs
	20	+** E.g., Pharos will
	21	+* ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
	22	+* Fixture Groups defined as single-channel loads in ShowRunner™
	23	+* 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
	24	+* 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:
	27	+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,59 +47,25 @@
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
	41	+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
	43	+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
	46	+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
	50	+1.
	51	+1. adsf
74	74
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:
	54	+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™
78	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
	56	+= Device Configuration =
88	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. Select the controller in the project
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
99		-
100	100	= ShowRunner™ Configuration =
101	101
102		-no feedback from dmx
103	103
104	104
105	105	)))