Read planning errors and warnings

When you wire a system in the Plan3D editor, validation runs as you work, so issues surface inline in the overlays the moment they occur, not only when you simulate. This guide covers the recurring warnings, the one caveat that trips people up (current-exceeded vs orientation), and the read-only state a signature puts the variant into.

Before you start

• Have your system wired: modules placed, strings created, and strings assigned to inverter MPP trackers.
• Know your inverter's maximum current per MPP tracker — most of the warnings here compare your string's current against that limit. Inverter specs come from the components catalog.
• Understand that warnings are advisory. You can save a variant that still has open warnings. The point of resolving them is a system that actually performs as planned.

Where errors and warnings show up

• Inverter overlay, Current section. Open an inverter in Strings mode. The Current section shows a per-MPP-tracker comparison of summed string current against the inverter's maximum current. When a tracker is over the limit, an inline error tag appears.
• Inverter overlay, orientation. The same overlay surfaces a separate orientation-mismatch warning when a string mixes module orientations.
• As you work. Validation updates as you edit, so a warned variant still saves and the warning stays visible until you resolve it.

The inverter overlay is your first stop for wiring problems. Both the current and orientation checks live there as inline tags, not as a titled page banner.

MPP Tracker current exceeded

What it means

A string carries more current than the inverter's MPP tracker can handle. In the inverter overlay, the Current section compares the summed string current against the inverter's maximum current per MPP tracker. When one or more trackers are over the limit, an inline error tag reads MPP Tracker current exceeded: (in German, MPP Tracker Stromstärke überschritten: — the editor shows this text in whichever language you use) followed by the affected tracker numbers (#1, #2, …). It's an inline value in the overlay, not a titled "maximum current exceeded" page banner.

When you'll see it

• Too many modules wired in parallel onto one MPP tracker push the summed current over the inverter's rating.
• An auto-routed system distributed strings in a way that loaded one tracker more than expected, or a manual edit afterwards pushed a tracker over.
• You over-provisioned module wattage relative to the inverter and the per-tracker current crept above the limit.

How to fix it

You have three paths:

1. Split the string into two shorter strings, paralleled on the same MPP tracker or moved onto different MPP trackers.
2. Pick a different inverter with a higher per-MPP current rating from the components catalog.
3. Remove modules from the string to drop the total current.

The warning is advisory, so you can still save the variant. Resolve it before you send the offer to the customer: if the inverter clips current at runtime, the installed system under-performs.

Current vs orientation: reading the right warning

The single most confusing thing in the validation surface: the inverter overlay carries two separate checks that are easy to mistake for one another.

• Current-exceeded (MPP Tracker current exceeded:) comes from the per-tracker current comparison in the Current section.
• Orientation-mismatch (Modules have different orientation / DE: Module haben unterschiedliche Ausrichtung) shows when a string mixes module tilts or orientations.

Note: These are distinct checks. If you see an orientation-style message on a string whose orientation looks consistent, confirm both conditions yourself: - Open the string and check the per-module orientation to confirm whether the orientation is actually mismatched. - Read the Current section to confirm whether the summed string current is over the inverter's maximum current per MPP tracker.

Treat the two as separate issues and resolve whichever one actually holds.

Mixed orientation matters because modules on the same MPP tracker pull down to the lowest-producing module's output, so a mixed-orientation string under-produces. Power optimizers let each optimized panel operate as its own MPP, which is the usual fix when you genuinely need mixed orientations on one string.

Signed variants are read-only

What it means

Once a variant is signed, the entire Plan3D editor and the variant's components become read-only. The scene still renders for review and the cameras still navigate, but every editing tool is greyed out: string editing, inverter editing, module placement, all of it. Existing warnings remain visible, but you no longer act on them in place. The signed scope is contractual, and historic offers stay reproducible for reference.

When you'll see it

• The customer signed, and only afterwards did you or a reviewer spot a wiring issue, such as a string over its tracker's current limit, a mixed-orientation string, or a module placed wrong.
• You open the signed variant's Plan3D editor to fix it and find every tool disabled.

How to fix it

1. On the same offer, duplicate the signed variant. The duplicate action copies its Plan3D state into a fresh, editable variant. (Creating a brand-new variant from scratch gives you a blank plan, not a copy — so duplicate, don't create-new.)
2. Make your fix in the duplicated variant: re-wire the string, pick a different inverter, or correct the orientation.
3. Re-run the simulation and take the duplicated variant through to signature as the corrected scope.

The original signed variant stays unchanged. Duplicating the variant is the supported path for any late change.

When something is genuinely broken

If the planner won't open at all, your saved variant disappears, components vanish after save, or the simulation returns clearly-wrong numbers (negative production, a 10x payback), those are separate from validation warnings. Contact Reonic support with:

• Your workspace name and your user email.
• The offer and variant you were working in (copy the page URL from your browser).
• A screenshot of the editor state.
• What you expected versus what you see.
• Browser console errors (open your browser's developer tools, then the Console tab) if you have them.

Things to know

• Validation updates as you work. Warnings surface in the inverter overlay the moment a string crosses a limit — you don't have to simulate to see them.
• Warnings are advisory. The current-exceeded and orientation-mismatch warnings still let you save. Resolving them is about a system that performs as planned.
• Current and orientation are separate checks. If a message seems to describe the wrong issue, verify the underlying condition manually: check per-module orientation for orientation warnings, and the Current section for current warnings.
• Mixed orientation under-produces. Modules on one MPP tracker pull down to the weakest module; optimizers (one MPP per optimized panel) are the fix when a mixed-orientation string is unavoidable.
• Warnings are on-screen in the editor. For grid-operator submissions, screenshot the editor and the variant overview.
• Signed variants lock the validation surface. Once a variant is signed, the 3D editor and variant components become read-only — warnings stay visible but can't be fixed. Duplicate the variant instead.
• The signed scope is contractual. Duplicating the signed variant is the supported path for late changes.

Need help?

• Step-by-step questions about a specific warning → contact your Reonic account manager.
• Bug reports → include the offer and variant page URL, a screenshot, browser console output, and your account email.
• Feature requests → mention them to your Reonic account manager.

Last updated on August 4, 2026