LogoLogo
Hub HomeDownloadsDocumentationReleases
  • Welcome
  • Introduction to HOLOPLOT
    • HOLOPLOT unique capabilities
    • HOLOPLOT technology
    • HOLOPLOT OS
      • Audio signal flow
    • Product family
  • user guides
    • HOLOPLOT system design
      • System design best practices
        • Introduction to sound system design
        • Which HOLOPLOT product is best suited to the application?
        • How do I decide on the position of my arrays?
        • What should be the size and aspect ratio of my arrays?
      • Beam design best practices
        • What are the fundamental principles of designing with beams?
        • How do I set up my coverage zones and what impact does that have on my design?
        • What are the different beam parameters and how do I apply them in my design?
        • How do I apply those beams in real world applications?
    • HOLOPLOT system deployment
      • Integration overview
      • Unboxing
      • Networking overview
      • AES67 Quick start guide
      • Advanced Network Configuration Tips
      • Power
      • Rigging
        • X1 Rigging Components
        • X1 standard rigging side plate attachment guide
        • X1 Standard rigging lifting procedures
        • X1 custom rigging
      • Venue validation
      • System operation & monitoring
      • Pairing the arrays & routing audio
      • Align and tune beams
      • Measurement and system optimization
    • Troubleshooting
  • HOLOPLOT Plan
    • Getting started
      • Recommended specifications
      • Installing HOLOPLOT Plan
      • Additional 3rd party tools
      • Navigating the interface
    • Onboarding videos
    • Importing 3D assets from SketchUp
      • Setting up the SketchUp toolkit
      • Installing the Khronos glTF Exporter for SketchUp
      • Defining zone types in SketchUp
      • Importing assets from SketchUp
    • Working with Matrix Arrays
      • Creating arrays
      • Moving arrays
    • Working with zones
      • Defining zone types
      • Drawing zones
      • Moving zones
    • Working with presets
      • Creating a preset
      • Working with preset layers
      • Working with environmental conditions
    • Working with beams
      • Creating a Parametric Beam
        • Adjusting Parametric Beam parameters
      • Creating a Virtual Source
        • Adjusting Virtual Source parameters
      • Creating a Coverage Beam
        • Assigning zones to a Coverage Beam
        • Adjusting Coverage Beam parameters
        • Optimizing a Coverage Beam
        • Working with beam variants (advanced)
      • Creating an LF Coverage Beam
        • Creating crossovers
      • Routing Beams
    • Simulation
      • Simulation controls
      • Tuning
      • Probe Mode
      • Simulating with S21 arrays
    • Saving & exporting
      • Exporting to AFMG EASE
  • HOLOPLOT Control
    • Getting started
      • Accessing HOLOPLOT Control
      • Navigating the interface
    • Configuring the system
      • Setting up system essentials
      • Managing a project
      • Pairing Modules
      • Network Settings - RAVENNA only
      • Stream Management - RAVENNA only
      • Setting up Analog mode on X2 Modules
    • Operating the system
      • Getting an overview of the active project
      • Routing streams to audio inputs
      • Switching presets and environmental conditions
      • Applying actions to the system
      • Tuning beams
      • Monitoring level meters
    • Maintaining the system
      • Monitoring device health
      • Module driver test
      • Module and Controller events
      • Module and Controllers Issues List
  • HOLOPLOT API
    • Getting started
    • Documentation
      • Arrays and modules
      • Beams and presets
      • Device health
      • Controllers
      • System operation
      • Spaces
    • Examples
      • Changing a preset
      • Adjusting the system's gain
Powered by GitBook
LogoLogo

HOLOPLOT

  • HOLOPLOT Website
  • Contact
  • Imprint
  • Privacy Policy

© 2024 HOLOPLOT GmbH. All rights reserved.

On this page
  • Status breakdown
  • Module's Health
  • Status calculation thresholds
  • Controller's Health
  • Status calculation thresholds
  • CONTROL Status
  • Filtering and finding issues
  • Filter
  • Issue Tracker

Was this helpful?

Export as PDF
  1. HOLOPLOT Control
  2. Maintaining the system

Monitoring device health

PreviousMaintaining the systemNextModule driver test

Last updated 1 month ago

Was this helpful?

This page provides insights into monitoring network and hardware-related statuses in the Device List section. Discover how to utilize these statuses for system configuration and maintenance purposes.

The Device List section allows you to monitor system statuses in real-time at various detail levels—system level, array level, or controller/module-specific.

Status breakdown

For all statuses, HOLOPLOT Control represents the severity level in 4 statuses. Here is their meaning:

Status
Arrays / Modules
Controllers

🟢 OK

Everything is functioning correctly. Sound can be played without issues.

Everything is functioning correctly. Operation is normal.

🟡 Warning

Sound can be played, there might be minor issues that compromise the system’s performance. Show can go on, but should be checked later on.

Controllers still function, but minor issues are observed. Show can go on, but should be checked later on.

🟠 Error

Modules can still make sound, but with severe degradation to system’s performance. Should be checked as soon as possible.

Controllers functionality is impacted, major issues are observed. Should be checked as soon as possible.

🔴 Critical

Modules are severely compromised and might not make sound.

Controllers cannot function properly.

⚪️ Unknown

Modules are not reporting any information, or we cannot accurately report its health.

Controllers are not reporting any information, or we cannot accurately report its health.

The Unknown status is an addition to the health statuses used when the system cannot infer the accurate status of modules, arrays, or controllers. An example of this is when a module or controller is offline.

Module's Health

Each module component group has its own logic and calculation approaches. Each outlined component state change generates an event for the respective device.

  • Power status—Power statuses have no effect on the module's health (e.g., a module can be sleeping and have a network error).

  • Network interfaces

    • NTP

    • Ravenna and PTP (If Dante is selected as the AoIP protocol, these statuses will not be considered in the health status calculation).

  • Hardware statuses

    • Amplifiers

    • PSUs

    • Drivers

Status calculation thresholds

The all-arrays/system, individual array, and module's health statuses are derived from the aggregation of the different network and hardware statuses using the thresholds below:

Status
% of devices ≥ 🔴
% of devices ≥ 🟠
% of devices ≥ 🟡
% of devices ≥ ⚪️

🟢

–

–

–

–

🟡

1%

5%

5%

1%

🟠

10%

30%

–

30%

🔴

30%

50%

–

50%

Module's health

The module's health is evaluated based on network and hardware statuses, which are derived from the aggregation of the aforementioned criteria. The highest severity level among these statuses determines the overall health of the module's network and hardware.

Single array's health

The single array health is an aggregation of the hardware and network statuses of the modules inside a specific array. The highest severity of its components defines the health status shown in HOLOPLOT Control.

Arrays' health or system health

The arrays' health is a single status derived from the health of all the system's arrays, using the thresholds mentioned above.

Controller's Health

Calculating the health of controllers follows a similar approach to modules and arrays, although with different components and thresholds.

Each controller component group has its own logic and calculation approaches. Each outlined component state change generates an event for the respective device.

  • Online status

  • Network status

    • Connectivity

      • HOLOPLOT Cloud

      • NTP

    • Network

      • Audio Module Control Network: It enables communication between the audio modules and the controllers for system management, operation, and configuration.

      • HOLOPLOT Control Network: It provides connectivity for HOLOPLOT Control and the Public System API, supporting user interaction and external system integration.

      • Audio Network: It supports Audio over IP monitoring services specifically for RAVENNA installations. It detects audio stream announcements and monitors audio streams to facilitate failover mechanisms.

      • Intercontroller Network: It facilitates the communication between HOLOPLOT controllers to synchronize their states and ensure redundancy in system operations.

  • Hardware status

    • Drives

    • Fans

    • PSUs

Status calculation thresholds

The controller health statuses are derived from the aggregation of the different network and hardware statuses using the thresholds below:

Each module component group has its own logic and calculation approaches. Each outlined component state change generates an event for the respective device.

Status
% of devices ≥ 🔴
% of devices ≥ 🟠
% of devices ≥ 🟡
% of devices ≥ ⚪️

🟢

–

–

–

–

🟡

1%

10%

10%

1%

🟠

10%

30%

–

30%

🔴

50%

80%

–

50%

Redundancy toggle An additional system setting informs whether modules and controllers are expected to have redundant network connections—Primary and secondary or just primary. This information affects how modules and controllers calculate their health.

To set up redundancy, go to Settings › System Settings and select your preferred setup.

CONTROL Status

This status refers to the web browser's connection to the system, which is visible only on the footer.


Filtering and finding issues

For a full list of possible issues, please refer to Module and Controllers Issues List

When navigating to the Device List, the right panel shows 2 collapsed cards: the filters and the issue tracker. They can be used together or independently.

Filter

The filter has two functions:

When collapsed, it allows for monitoring of the Network and Hardware statuses.

When expanded, it allows for filtering based on Power, Network, and Hardware statuses to quickly identify system failures during debugging.

Issue Tracker

Whenever there's an issue affecting the network or hardware status, the specific issue will be displayed on the Issue Tracker in the following format Type – Issue description.

Click the issue to filter the modules with that specific issue.

Device List
Module side panel
Module health
Single Array Health
System / Arrays' Health in the footer
Controllers' status
Controller side panel
Redundancy settings
CONTROL Status in the footer
Filters & Issue Tracker
Collapsed Filters
Expanded Filters