Skip to Content

Changes for page Pharos Configuration

Last modified by Alexander Mott on 2024/02/26 15:10
From version 5.1
edited by Alexander Mott
on 2023/05/09 21:21
Change comment: There is no comment for this version
To version 4.1
edited by Alexander Mott
on 2023/05/05 21:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,8 +8,6 @@
8 8  
9 9  = Pharos Project =
10 10  
11 -== Creating a New Pharos Project for ShowRunner™ ==
12 -
13 13  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.
14 14  
15 15  When creating a Pharos project for a ShowRunner™ installation, there are several things to consider:
... ... @@ -68,21 +68,6 @@
68 68  1*. Fixtures can be unpatched by right clicking them in the universe
69 69  1. If desired, navigate to the "Timeline" page and create timelines
70 70  
71 -== Editing an Existing Pharos Project ==
72 -
73 -If modifications need to be made to a Pharos Project that is already working with ShowRunner™, there are some things that should be taken into consideration in order to avoid breaking the existing programming:
74 -
75 -* ShowRunner™ does not pay attention to how Pharos DMX fixtures are addressed, only how they are grouped
76 -** ShowRunner™ provides direct control of Pharos fixture groups by their group ID. Avoid changing Pharos fixture groups or group numbers unless you are aware of how they are mapped in ShowRunner™
77 -** Adding newly patched/addressed fixtures to existing groups that are mapped in ShowRunner™ will allow those fixtures to be controlled without adding them to the ShowRunner™ configuration
78 -** Removing fixtures from existing groups that are mapped in ShowRunner™ will prevent those fixtures from being controlled unless they are also in another group that is mapped to a ShowRunner™ load
79 -** Renumbering a group that is mapped to a load in ShowRunner™ will prevent ShowRunner™ from controlling that group, unless the new number is also mapped in ShowRunner™
80 -** If a new group is created that has the same group ID as a group that is already mapped in ShowRunner™, then ShowRunner™ will control that new group using the old load unless the ShowRunner™ configuration is updated
81 -* ShowRunner™ maps Scenes to Pharos Timelines by their timeline ID
82 -** Avoid changing Pharos timeline IDs unless you are aware of how they are mapped in ShowRunner™
83 -** If a new Timeline is added that replaces the ID of an old Timeline, then the scene mapping in ShowRunner™ needs to be updated to prevent the old ShowRunner™ Scene from triggering the new Timeline
84 -** If an existing Timeline is deleted, it should be unmapped in ShowRunner™ to prevent errors when the mapped ShowRunner™ Scene is recalled
85 -
86 86  = Device Configuration =
87 87  
88 88  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: