Wiki source code of Pharos Configuration
Version 1.9 by Alexander Mott on 2023/05/05 18:24
Hide last authors
author | version | line-number | content |
---|---|---|---|
![]() |
1.1 | 1 | {{box cssClass="floatinginfobox" title="**CONTENTS**"}} |
2 | {{toc/}} | ||
3 | {{/box}} | ||
4 | |||
5 | (% class="row" %) | ||
6 | ((( | ||
7 | 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. | ||
8 | |||
9 | = Pharos Project = | ||
10 | |||
![]() |
1.2 | 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. |
![]() |
1.1 | 12 | |
![]() |
1.2 | 13 | The basic steps for creating a Pharos Project for use with ShowRunner™ are: |
![]() |
1.1 | 14 | |
![]() |
1.2 | 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 | ||
![]() |
1.4 | 18 | 1. Navigate to the "Project" page by clicking the Pharos logo on the left |
![]() |
1.3 | 19 | 1. Under the "Controller API" heading, verify that API Version 5.0 is selected |
![]() |
1.4 | 20 | 1. Navigate to the "Layout" page by clicking the pencil and ruler icon on the left |
![]() |
1.5 | 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 |
![]() |
1.8 | 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 | ||
![]() |
1.5 | 24 | 1*. Pharos also has a large selection of manufacturer-specific profiles which can be used instead of the generics |
![]() |
1.4 | 25 | 1*. Additional generic and manufacturer-specific profiles can be downloaded by clicking the cloud icon on the right, above the fixture profile list |
![]() |
1.7 | 26 | 1. Add fixtures to the layout by dragging them from the fixture profile list |
27 | 1*. Every fixture that is added to the layout represents a unique set of DMX addresses | ||
28 | 1*. Note that the fixture number is different than the fixture address, and is automatically incremented by Pharos Designer 2 | ||
29 | 1*. Right-clicking a fixture on the layout will allow you to "Duplicate" or create a "New Instance" of a fixture | ||
30 | 1**. Duplicating a fixture creates a new fixture with the same profile and properties | ||
![]() |
1.8 | 31 | 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 |
![]() |
1.9 | 32 | 1. When adding fixtures to the layout, keep in mind ShowRunner™ uses group-level controls and that the Pharos API has certain limitations on the types of commands that can be sent |
33 | 1*. ShowRunner™ is only able to send RGB, single-channel, and intensity/CCT commands | ||
34 | 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 | ||
![]() |
1.8 | 35 | 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 |
36 | 1. adsf | ||
![]() |
1.1 | 37 | |
![]() |
1.2 | 38 | |
![]() |
1.6 | 39 | 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™ |
![]() |
1.1 | 40 | |
41 | = Device Configuration = | ||
42 | |||
43 | = ShowRunner™ Configuration = | ||
44 | |||
45 | |||
46 | |||
47 | ))) |