Real-Time Monitoring

Mirox actively retrieves data from your plants instead of waiting for them to report in, so you always have near-real-time visibility into every installation — and you notice a silent logger the moment it stops responding, not hours later.

Active Data Collection

Real-time monitoring is built on an active collection model. A dedicated edge agent (the Data Scraper) runs on or near each plant and continuously reaches out to the local devices to pull their latest readings.

• Active Retrieval: Mirox connects to your loggers, inverters, meters and storage systems and reads them on a schedule — it never depends on the device choosing to push data
• Continuous Operation: Collection runs around the clock to keep your dashboards close to live
• Failure Visibility: Because Mirox initiates every read, a device that goes quiet is detected immediately and surfaces as a data-collection issue

This approach gives you current information even from equipment that has no ability to report on its own.

How Mirox Connects to Your Devices

Plants in the field run a wide mix of hardware, so Mirox connects to each device family through a purpose-built adapter rather than a single generic protocol. Each adapter understands one vendor's specific interface — its login flow, its data format and its quirks — and translates the readings into the common Mirox metric vocabulary.

Adapters already exist for many common device families, including:

• Data loggers such as Bluelog, Huawei SmartLogger and Sungrow loggers
• Inverter controllers such as SMA Sunny Central and SMA Power Manager
• Power-quality meters such as Janitza
• Controllers and PLCs such as Phoenix Contact and Dexcon
• Battery storage systems such as FREQCON BESS
• On-site historians and monitoring servers, including SQL Server based historians and PRTG
• File and object stores holding exported readings (S3-compatible storage and local files)
• Weather and irradiance sources that supplement on-site measurements

What Mirox Measures

Mirox normalizes everything it reads into one consistent metric catalog covering generation, storage, environment and infrastructure — currently well over 370 distinct measurements spanning grid and AC output, inverter and combiner-box (GAK) values, string-level readings, battery box/module/cell values, weather inputs and agent health. Component-level labels (per inverter, per string, per battery module) let you drill from a whole-plant figure down to an individual device.

Components are auto-discovered: as readings arrive, Mirox infers the plant's inverters, combiner boxes, strings and battery hierarchy from the data stream and builds the component tree for you, without manual entry.

Data Processing Pipeline

Once a reading is collected, it passes through a consistent set of steps before it reaches your dashboards:

1. Validation: Readings are range-checked, energy counters are confirmed to only ever increase, and frozen or stuck values are flagged
2. Normalization: Values are converted to standard units (for example kW to W) and a common format
3. Enrichment: Mirox derives values that are not read directly — such as energy integrated from power, combiner-box aggregates and clear-sky baselines
4. Storage: The result is recorded in the time-series database for analysis and visualization

This pipeline means data from a Sungrow logger and data from an SQL historian end up indistinguishable to you — same units, same names, same quality checks.

Real-Time Advantages

The active collection model delivers several concrete benefits:

• Reduced Latency: You see system changes and events almost as they happen
• Higher Reliability: Monitoring does not depend on device-initiated reports that may silently fail
• Comprehensive Coverage: Mirox can read devices that have no ability to push data at all
• Proactive Monitoring: A communication or device failure is detected the moment a scheduled read does not return the expected data

Connection Status and Topology

Because Mirox initiates every connection, it can show you the full path from the cloud all the way down to each logger. You can see whether the cloud is reaching the on-site agent, whether the agent can reach your network infrastructure and devices, and whether each individual logger is responding — so when something breaks, you know exactly where in the chain to look. The on-site network discovery and device health checks are covered in the Local Network Inspector.

Security Considerations

Active collection is designed to strengthen, not weaken, your plant's security posture:

• Read-Only Operation: Collection reads device values and does not write to or control your equipment
• Encrypted Connections: Data retrieval uses encrypted transport wherever the device supports it
• Access Control: All collection activity is authenticated and authorized
• Network Isolation: The on-site agent operates within secure network boundaries and reaches the cloud over controlled, monitored channels

Related Features

• Data Scraper — the edge agent and the full list of supported device adapters
• Digital Twin — physics-based modeling built on the collected data
• KPI Dashboard — the headline metrics derived from real-time monitoring
• Local Network Inspector — on-site discovery and connection health for your plant network
• Events — automatic detection of issues from the live data feed
• Forecasts — weather-based production outlook on top of historical readings