Fixtures

Only where the portal has RDM.

Fixture status across a site

Open a site and select its Fixtures tab for an overview covering every controller in the site, with a summary per controller.

Users who have the correct permissions to see fixture information for any controller in the site will see those controllers in the summary. Refresh All starts a poll across all controllers the user can run polls from in the site, asking you to confirm first because a poll can momentarily disrupt lighting output. Selecting a controller takes you to its dedicated Fixtures tab where fixtures can be managed.

Under Site Fixtures Status the whole site is broken down by status, and under Devices the same breakdown is repeated per controller, each card sizing its bars against that controller's own total. Alongside the fixture statuses, a card counts Unassigned Devices — responders no fixture in the project claims — and No Data, the fixtures nothing has been reported for at all.

These cards use the dashboard's own wording. The device fixtures tab names two of the same statuses differently on the markers in its own table, and lists which word to expect where.

A message at the top of this tab records that, while fixture status monitoring is being introduced, it is included in your standard Cloud subscription, and that you will be told in advance if that is going to change. Dismissing it hides it for you on this site.

Prerequisites

The controller runs a recent enough version. Below the minimum the device's Fixtures tab is not shown at all rather than shown empty — so a missing tab is the thing to check first. On an LPC family controller the minimum is Pharos Designer 2.16.3. On an Express controller it is Pharos Express 2.1.2.

The controller is a model that supports RDM. The tab is offered per model, and some models, the VLC family among them, do not have it whatever their firmware.

Fixture status is turned on for your portal, and you may see it. It is a portal feature, so a portal without it has no fixtures tabs anywhere; and the tab is withheld from a user without permission to view fixtures on that device.

Your fixtures support RDM. Check the manufacturer's documentation. A fixture that doesn't support RDM can still exist in the project and will appear as a fixture in the Fixtures tab for controllers, but Cloud has no way to query it.

Your fixtures have RDM UIDs set in the project file. Fixtures added by RDM discovery get their UID automatically. Anything added by hand needs the UID entering in the fixture's properties. Without a UID, the device can't match a discovered responder to a fixture in your project. See the Pharos Designer or Pharos Express help for how to do this in your system.