Features and enhancements introduced in the v2.9 release.
TPS 5 Support: The Pharos Designer TPS 5 (Touch Panel Station 5″) is a new, updated, elegant interface with a customisable, 5″ capacitive touch screen, compatible with any Pharos Designer Controller.
- Install is easy and convenient with just a single Power-over-Ethernet (PoE) network connection.
- Provides a user interface to any Pharos Designer control system.
The functionality is similar to the existing TPS, although with greater responsiveness, resolution and enhanced hardware.
More information can be found here
Authentication Update: 2.9 includes a major overhaul to the authentication system for Pharos Designer Mosaic Controllers.
The Controller login and the Web Interface user accounts have been unified, meaning user accounts can now be created on the controller, with the same user groups as the Web Interface user accounts, with the option to expand these in future.
More information can be found here
Key features include:
- The creation of an admin user account will be encouraged on first usage or after a factory reset
- Web Interface user accounts have been replaced by Controller user accounts
- .htaccess files have been replaced with .webconfig files (more information available in the Help or from the Authentication application note)
- A new API version, v6, that has improved and updated authentication functionality
- Include username in the Log when an action is fired from the Web Interface
- Print to the Log when a user is created or signs in
- Improved resilience against brute forcing the unit’s password
Cloud Connection Status Triggers: New functionality has been implemented to allow controllers to trigger off the Cloud Connection status.
These include:
- A condition to check if the controller has an active connection to a Cloud Site or not
- A trigger that fires on Cloud Site connection status change
- An http and lua API query for Cloud connection status
RDM Polling (Beta): A framework for RDM Polling has been included in this release, allowing the controller to scan for RDM fixtures and report information back through an IO Module or through a web server. This feature itself is currently still in beta, so please contact Support if you are interested in trying this functionality.
Please note: this feature is offered as a technical preview for experimentation only, and is therefore not actively recommended for live projects. Documentation and full support will become available at a later date.
Designer Enhancements: We continue to make improvements throughout the software, with some of the highlights in v2.9 including:
- Improved Direct Colour simulation
- Allow user to force running of dropped project after 5 failed loads
- Create common authentication endpoint for API v6.0
- Upgrade jQuery to resolve vulnerabilities
- Remove legacy (api == 0) user api support
- Log when users are created, logged in and logged out on the Web Interface
- Allow a discovered controller to be associated with a project controller as long as patch capacity is known
- Clearing a controller’s log from Designer should require entry of the admin password
- Log username of user who triggers action on the Web Interface
- Single Controller Project files shouldn’t send multicast trigger messages
- Rename .htaccess file
