Changes for page Pharos Configuration
Last modified by Alexander Mott on 2024/02/26 15:10
From version 23.1
edited by Alexander Mott
on 2023/05/16 18:14
on 2023/05/16 18:14
Change comment:
There is no comment for this version
To version 24.1
edited by Alexander Mott
on 2023/05/16 18:15
on 2023/05/16 18:15
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -80,7 +80,7 @@ 80 80 81 81 * The version of Pharos Designer 2 is tied to the version of the Pharos controller firmware. Editing an existing project with a newer version of Designer 2 than the project was last saved in may result in the newly edited project no longer being able to be loaded to the controller without updating the controller firmware. 82 82 ** To maintain full backwards compatibility with an existing installation, verify the controller's current firmware version and then download the corresponding version of Designer 2 from [[Pharos Controls' website>>https://www.pharoscontrols.com/support/designer/software-downloads/#software-archive]] 83 -* ShowRunner™ does not pay attention to how Pharos DMX fixtures are addressed, only how they are grouped 83 +* ShowRunner™ does not pay attention to how Pharos DMX fixtures are addressed, only how they are grouped. Re-patching fixtures (changing their address) is covered in the [[Fixture Addressing and Identification section>>doc:SHOWRUNNER™ Setup Guide.SHOWRUNNER™ Installation Guide.Program Configuration.Pharos Configuration.WebHome||anchor="HFixtureAddressingandIdentification"]] below. 84 84 ** 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™ 85 85 ** 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 86 86 ** 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