Configuring Components
The Components page is where you describe the physical make-up of a plant — its inverters, combiner boxes, strings, irradiation sensors, and feed-in meters — so the platform knows what it is monitoring. Getting this configuration right is what turns raw measurements into a clear-sky simulation, a performance ratio, loss detection, and string-level analysis. This guide walks you through each task and explains what your edits actually drive.
Where it lives
Open your plant's Components section in Mirox (in the app: open a plant from your plants, then its Components section). The tabs across the top — Stromzähler (feed-in meter), Irradiation, Inverter, Combiner Box, and Strings — group every component type.
Why Configuration Matters
The Components page is not just an inventory. The numbers you enter here become the reference the Digital Twin compares live telemetry against:
- Clear-sky simulation uses each string's panel datasheet, azimuth, tilt, and panel count to model the energy a string should produce under clear skies.
- Performance ratio and degradation are measured against the configured peak power, so an under- or over-stated peak power skews every efficiency figure.
- Loss detection attributes shortfalls to specific components — it can only do that if the component tree is complete and correctly mapped.
- String analysis and the component states (producing normal, degraded, inferred, and so on) depend on the same configuration.
Keep configured power and string power in agreement
A power mismatch — where the plant's configured peak power does not equal the sum of its strings — degrades digital-twin accuracy. The Review Status card flags it, and you should resolve it before relying on the analysis (see Check the Review Status).
Read the Status Cards
Above the tabs, three cards summarize the plant's configuration health:
- Peak Power — the configured peak production of the plant.
- System Metrics — current system-level figures, including the logger count.
- Review Status — how complete and consistent the configuration is (covered below).
Configure Inverters
Open the Inverter tab. Each row is an inverter the platform has discovered or that you added. Click a row to open its detail drawer, where you can:
- Assign a datasheet. Pick the inverter model from the Datasheet dropdown. The datasheet supplies the manufacturer, model, rated peak performance, and efficiency figures shown below the selector.
- Add notes. Use the Information field for any free-text context (service history, location, quirks).
- Mark as hidden. Toggle Mark as Hidden to remove a decommissioned or duplicate inverter from the main view. Use the Show Hidden switch on the tab to bring hidden items back temporarily.
- Click Save.
The drawer also shows read-only state — connected strings, combiner boxes, panel count, connected peak power, status, last-seen time, and discovery source. Use the Connected Components cards to jump straight to that inverter's combiner boxes or strings.
Auto-detection fills the name
An inverter with no name shows a "Waiting for Auto-Detection" placeholder and is named automatically once data arrives. Clearing a name with the eraser hands it back to auto-detection.
Add Combiner Boxes
If a plant routes its strings through combiner boxes (Generatoranschlusskästen), add them so the string tree matches reality. The Combiner Box tab only appears once a plant has at least one.
- On the Inverter, Combiner Box, or Strings tab, click Add Combiner Box.
- Select the parent Inverter.
- Enter the Number of Combiner Boxes to create (1–50) and, optionally, a Name Prefix (for example
GAK-). - Click Save.
Add and Configure Strings
Strings carry the panel configuration that drives the clear-sky model, so this is the most impactful part of the page. Open the Strings tab (filter by inverter, and by combiner box where present, to narrow the list).
Add strings
- Click Add String.
- Choose the target — To Inverter or To Combiner Box — and select one or more targets.
- Fill in the string configuration:
- Number of Strings — how many identical strings to create per target.
- Panel Datasheet — the panel model; its rated power feeds the peak-power calculation.
- Azimuth — orientation in degrees (0–360, where 180 = South).
- Tilt — angle in degrees (0–90).
- Panels per Row and Parallel Rows — together these define how many panels each string carries.
- The dialog previews the estimated peak power you are about to add, computed from the panel rating and counts. Click Save.
Edit strings in bulk
- Select one or more strings in the table (or none, to apply to a wider scope).
- Click Edit.
- Adjust the panel datasheet, azimuth, tilt, or panels in series.
- Choose the scope under Apply changes to — Selected Strings, All Strings in Combiner Box, All Strings in Inverter, or All Strings in Park.
- Toggle Mark as Verified once a string's configuration is confirmed correct.
- Toggle Mark as reviewed to clear the review flag (needs attention) for the selection. This dismisses the flag, but it returns on the next analysis run if the underlying problem persists.
- Click Save.
Verify as you go
Marking strings verified is how you track which configuration you have reviewed. Verifying also copies any detected values into the manual fields you left empty, so the configuration you confirm matches what the analysis found, and it clears the review flag. Detection keeps running on verified strings as a cross-check — if a later run confidently contradicts a verified value, the string is flagged for attention while your manual value stays in effect. The Review Status card tracks your verification progress in its pie chart, independently of the warnings.
How values are prioritised
For every string property — azimuth, tilt, panels per row, parallel rows, panel count, peak power — the analysis uses a clear priority: manual before detected before default. Configure only what you are sure of; the analysis fills the gaps with the values it detects, and falls back to a default only when neither exists. A manual value is never overwritten by a detection. Instead, when a confident detection contradicts a manual value, the string is flagged for attention so you can decide — your value stays in effect until you change it.
Inspect a single string
Click a string row to open its detail drawer:
- Configuration shows each property as Configured vs Detected side by side, plus the effective totals (total panels, peak power) actually in use.
- Analysis Metrics compares Expected vs Measured: the expected degradation from the panel datasheet's aging at the string's installation age — with the corresponding power loss (W) and voltage loss (V) — next to what the analysis measured. Both columns are cumulative since installation, so they compare directly; a measured value below expected means the string ages better than its datasheet predicts. The performance ratio and the installation age complete the picture.
- The installation date defaults to the park's commissioning date; set the string's replacement date (pencil icon) to override it for repowered strings — degradation is computed against this date.
- Information holds free-text notes; the connected components cards jump to the parent inverter or combiner box.
Check the Review Status
The Review Status card tells you whether the configuration is complete and self-consistent:
- A verified percentage and pie chart show how many visible strings you have confirmed.
- A power comparison shows the configured Expected peak power against the Strings total, and the Offset between them. When they match, it reads Power Matching.
- A needs-attention counter reports how many strings are flagged for review — because a value (azimuth, tilt, panels per row, parallel rows) is unknown on both sides (neither configured nor detected), a string was detected as not connected, a measurement looks defective, or a confident detection conflicts with a configured value. Strings whose configuration is complete — from manual or detected values — are never counted here, even while still unverified.
- When strings are flagged, the card shows a Review button. Clicking it filters the table to exactly the strings the counter reports — the number on the card always equals the rows you see. Resolve them and mark them verified or reviewed. If the totals are correct but the expected peak power is wrong, adjust the expected peak power in the plant's core data settings instead.
Once the power matches and nothing is flagged, the card reads All Good and offers a Deep Analysis action that asks the agent to re-evaluate the plant with the corrected configuration. Verification progress is tracked separately by the pie — unverified strings with a complete configuration are fine and raise no warning.
While an analysis runs, you can open the live deep-analysis protocol to follow it in real time: the start and mode, the day-quality verdict (detected curtailment or cloudy periods and what was excluded), per-string progress, a degradation summary, "results saved", and the final peak-power comparison of detected vs configured vs nameplate. It is the quickest way to see what the analysis concluded and why.
In the strings table, problems are also shown inline so you can spot them without opening each drawer:
- Orange values mark a conflict directly in the affected cell — azimuth/cardinal direction, tilt, parallel-rows factor, panels per row, or panel total — each with a "Configured X / Detected Y" tooltip.
- Two shield icons appear in the verified column: a red shield signals a confident configuration conflict (its tooltip lists each conflicting field with both values), and an orange shield signals missing information (it names the missing fields). A verified string can carry a problem icon too — the green check is shown alongside it.
Other Component Types
- Irradiation — the irradiation sensors used as the production reference. Click a row to view sensor details.
- Stromzähler (Feed-in Meter) — the meters that measure energy fed to the grid. Click a row to view meter details.
Related Guides
- Setup — the short end-to-end workflow: configure what you know, let the analysis detect the rest, review and verify
- Component States — the operational states the Digital Twin assigns to the components you configure here
- Digital Twin — the engine that turns this configuration plus live telemetry into monitoring insight
- Loss Detection — how a complete, correct component tree lets shortfalls be attributed to a specific string or inverter
- Solar Plants — the supported solar configurations and the parameters Mirox monitors
- Configuring Data Loggers — map discovered devices so components start reporting data