Changes for page Pharos Configuration

Summary

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

Details

Page properties

Content

...	...	@@ -8,16 +8,44 @@
8	8
9	9	= Pharos Project =
10	10
11		-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. ShowRunner™ sends group-level commands over the Pharos Controller API, so each Fixture Group in Pharos will correspond to
	11	+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.
12	12
13		-1. Download the Pharos Designer 2 software from Ph
	13	+The basic steps for creating a Pharos Project for use with ShowRunner™ are:
14	14
	15	+1. Open the Pharos Designer 2 software
	16	+1. In the top-right, click "New Project" and select the type of Pharos controller that will be the primary controller
	17	+1*. Crestron SKUs DIN-DMX-1UNIVERSE and DIN-DMX-2UNIVERSE both correspond to "LPC" in Pharos
	18	+1. Navigate to the "Project" page by clicking the Pharos logo on the left
	19	+1. Under the "Controller API" heading, verify that API Version 5.0 is selected
	20	+1. Navigate to the "Layout" page by clicking the pencil and ruler icon on the left
	21	+1. At the top left, click "Manage..." to edit the layout name and dimensions, modify grid settings, and upload a background image if desired
	22	+1. Locate the desired fixture in the Fixture Profile List on the right side of the Layout page
	23	+1*. Most fixtures can be controlled correctly using the generic single-channel, RGB, warm/cool, intensity/CCT, HSIC, etc. profiles
	24	+1*. Pharos also has a large selection of manufacturer-specific profiles which can be used instead of the generics
	25	+1*. Additional generic and manufacturer-specific profiles can be downloaded by clicking the cloud icon on the right, above the fixture profile list
	26	+1. Prior to adding fixtures to the layout, consider the following:
	27	+1*. ShowRunner™ uses group-level commands, so each individual load in ShowRunner™ must have a corresponding Fixture Group in Pharos
	28	+1*. The Pharos API limits commands to single-channel (intensity), RGB, or Intensity/CCT
	29	+1*. 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
	30	+1*. Fixtures can belong to multiple Fixture Groups
	31	+1**. This allows ShowRunner™ to send different types of commands to the same fixtures
	32	+1**. 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
	33	+1. Add fixtures to the layout by dragging them from the fixture profile list
	34	+1*. Every fixture that is added to the layout represents a unique set of DMX addresses
	35	+1*. Note that the fixture number is different than the fixture address, and is automatically incremented by Pharos Designer 2
	36	+1*. Right-clicking a fixture on the layout will allow you to "Duplicate" or create a "New Instance" of a fixture
	37	+1**. Duplicating a fixture creates a new fixture with the same profile and properties
	38	+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
	39	+1.
	40	+1. When adding fixtures to the layout, keep in mind ShowRunner™ uses group-level controls
	41	+1*. ShowRunner™ is only able to send RGB, single-channel, and intensity/CCT commands
	42	+1*. Other fixture types (such as HSI, warm/cool, ICHS, etc.) still work correctly, but only RGB, single-channel, and intensity/CCT commands can be sent ot them
	43	+1*. RGBW fixtures should be defined as separate RGB and W fixtures so that ShowRunner™ can control the white channel separately from the RGB channels
	44	+1. adsf
15	15
16		-The Pharos project layout can be as simple or as complicated as desired as long as the fixtures are grouped in a way that is compatible with ShowRunner™
17	17
	47	+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™
18	18
19		-Due to limitations with the Pharos API, only single channel, RGB, or Intensity/CCT load types can be defined in ShowRunner™.
20		-
21	21	= Device Configuration =
22	22
23	23	= ShowRunner™ Configuration =