Troubleshooting Guide

Solutions for common issues you may encounter while using Branch. Find your issue below or use Ctrl+F to search.

Need more help?

If your issue isn't covered here, run BUGREPORT to submit a detailed bug report, or contact support at contact@leafautomation.ai

Categories

Panel Detection & GroupsString SolvingData ExportHomeruns & InvertersData PersistenceAuthentication & APIAutoCAD IntegrationSolarEdge PDF Import

Panel Detection & Groups

Issues with PANELGROUPCREATE not detecting panels correctly

PANELGROUPCREATE misses some panels

Related: PANELGROUPCREATE

Possible Causes

  • Panels are slightly misaligned (not on a consistent grid)
  • Panel blocks have non-uniform scaling
  • Some panels are on locked or frozen layers
  • Panels are part of external references (XREFs)

Solutions

  • Ensure all panels are aligned to a consistent grid. Branch uses alignment tolerance—panels offset by more than a few inches may be treated as separate rows.
  • Use uniformly scaled blocks. If panels have different X/Y scale factors, they may not be recognized.
  • Unlock and thaw all panel layers before running PANELGROUPCREATE.
  • Bind or explode XREFs containing panels before detection.

Panels detected as multiple groups instead of one

Related: PANELGROUPCREATE

Possible Causes

  • Gap between panel sections exceeds the grouping threshold
  • Panels are on different Z elevations
  • Row misalignment breaks continuity detection

Solutions

  • Branch groups panels based on proximity. Large gaps (typically > 2 panel widths) create separate groups.
  • Flatten all panels to Z=0 if working in 2D. Use FLATTEN or CHANGE command.
  • Ensure rows are consistently aligned. Even small offsets can break the grouping algorithm.

Panel count is wrong after grouping

Related: PANELGROUPCREATE

Possible Causes

  • Duplicate blocks stacked on top of each other
  • Non-standard panel block names not recognized
  • Block definitions contain nested blocks

Solutions

  • Run OVERKILL to remove duplicate geometry.
  • Ensure panel blocks match Branch's expected naming convention or configure custom block names in BRANCH.
  • Explode complex blocks to their base components if nested.

String Solving

Issues with SOLVE command and string generation

SOLVE produces suboptimal or strange string paths

Related: SOLVE

Possible Causes

  • Panel groups have irregular shapes that confuse the region carving algorithm
  • String length setting doesn't match panel count well
  • Obstruction zones interfering with path calculation

Solutions

  • For complex roof shapes, split into multiple panel groups that are more rectangular.
  • Adjust string length in BRANCH to better divide into your panel count. The +/- header suggestions help.
  • Check for hidden obstruction polylines that may be blocking string paths.

SOLVE fails with 'No valid solution' error

Related: SOLVE

Possible Causes

  • Panel count cannot be evenly divided by string length
  • Region carving algorithm cannot find valid partition
  • Token authentication expired mid-operation

Solutions

  • Use ADDPANELS to transfer panels between groups until counts divide evenly.
  • Try adjusting string length up or down by 1-2 panels.
  • Run LEAFLOGIN to refresh authentication if session expired.

Strings cross over each other unnecessarily

Related: SOLVE

Possible Causes

  • The optimization algorithm found a local minimum
  • Panel insertion points are not at consistent locations within blocks

Solutions

  • Run SOLVE again—the algorithm may find a better solution.
  • Use FLIPSTRING to manually reverse problematic strings.
  • Check that panel block insertion points are consistently placed (typically center or corner).

Jumper cable prompt doesn't appear after ADDPANELS

Related: ADDPANELS

Possible Causes

  • ADDPANELS wasn't completed successfully
  • Source and destination groups are the same

Solutions

  • Ensure you completed the full ADDPANELS workflow (select source group, select destination group, pick panels).
  • The jumper prompt appears during the next SOLVE, not immediately after ADDPANELS.

Data Export

Issues with CABLEEXPORT command

CABLEEXPORT fails or produces empty Excel file

Related: CABLEEXPORT

Possible Causes

  • No strings exist in the drawing
  • Excel file is open in another application
  • Strings missing required XData attributes

Solutions

  • Run SOLVE first to generate strings before exporting.
  • Close any open Excel files before running CABLEEXPORT.
  • If strings were created manually, ensure they have proper string data attached (run STRINGDATA to verify).

Homeruns & Inverters

Issues with HOMERUNS, ADDINVERTER, and INVBALANCE

HOMERUNS command doesn't create any lines

Related: HOMERUNS

Possible Causes

  • No solved strings exist in the drawing
  • Inverter block not placed or not recognized
  • Target layer is locked or frozen

Solutions

  • Run SOLVE first to create string endpoints for homerun routing.
  • Place inverter using ADDINVERTER before running HOMERUNS.
  • Check HOMERUNOPTIONS to verify the homerun layer is unlocked.

ADDINVERTER can't find inverter block

Related: ADDINVERTER

Possible Causes

  • Inverter block definition doesn't exist in drawing
  • Block name doesn't match configured name
  • Block is in an external file that hasn't been inserted

Solutions

  • Insert the inverter block definition from your block library first.
  • Configure the correct block name in HOMERUNOPTIONS.
  • Use INSERT command to bring the block definition into the current drawing.

INVBALANCE doesn't improve distribution

Related: INVBALANCE

Possible Causes

  • Strings are already optimally balanced (all green in the inverter list)
  • Only one MPPT input is being used per inverter
  • No cross-inverter swaps are within distance threshold

Solutions

  • If all inverters show green status, panel counts are already matched per MPPT — no swaps needed.
  • Ensure multiple MPPTs are configured for your inverter in BRANCHOPTIONS.
  • Try Auto-Balance All to apply all non-conflicting swaps across the drawing at once.
  • For cross-inverter suggestions, strings must be within reach of the other inverter. Consider moving inverters closer with MOVEINV.

Homeruns route through obstacles

Related: HOMERUNS

Possible Causes

  • K-means clustering doesn't account for physical obstacles
  • No obstruction zones defined

Solutions

  • Branch's homerun routing uses direct paths—manually adjust polylines around obstacles after generation.
  • Consider running HOMERUNS, then editing the resulting polylines with AutoCAD's PEDIT command.

Data Persistence

Issues with string data, settings, and XData storage

String data lost after saving and reopening drawing

Related: STRINGDATA

Possible Causes

  • Drawing saved in older DWG format that strips XData
  • WBLOCK or partial save excluded XData
  • File corruption during save

Solutions

  • Save in AutoCAD 2018+ DWG format to preserve all XData.
  • When using WBLOCK, ensure you select all related entities.
  • Keep backup copies of drawings before major operations.

Settings reset between sessions

Related: BRANCH

Possible Causes

  • Settings stored in document XData, not globally
  • Started a new drawing without running LEAFSETUP
  • Template drawing doesn't include Branch configuration

Solutions

  • Run BRANCH to reconfigure settings for each new drawing.
  • Create a template (DWT) file with your standard Branch settings pre-configured.
  • Settings are per-drawing by design to support different project configurations.

Panel group headers missing after copy/paste

Related: PANELGROUPCREATE

Possible Causes

  • COPYCLIP doesn't preserve all entity relationships
  • XData app name not registered in destination drawing

Solutions

  • Use COPY command within the same drawing instead of COPYCLIP.
  • After pasting into new drawing, run PANELGROUPCREATE to regenerate headers.
  • XData may need to be rebuilt when moving between drawings.

Authentication & API

Issues with login, licensing, and cloud features

LEAFLOGIN fails or times out

Related: LEAFLOGIN

Possible Causes

  • Network connectivity issues
  • Firewall blocking Branch's authentication servers
  • Invalid or expired credentials

Solutions

  • Check internet connectivity and try again.
  • Ensure your firewall allows connections to Branch's API endpoints.
  • Try logging in through the Branch website first to verify credentials.

'Token expired' errors during long sessions

Related: LEAFLOGIN

Possible Causes

  • Authentication tokens expire after a set period
  • Computer was in sleep mode and session wasn't refreshed

Solutions

  • Run LEAFLOGIN to refresh your authentication.
  • Save your work periodically—Branch will prompt for re-authentication when needed.

License shows as inactive despite valid subscription

Related: LEAFSTATUS

Possible Causes

  • Subscription not synced with local client
  • Using wrong email account
  • Subscription recently renewed but cache not updated

Solutions

  • Run LEAFLOGOUT then LEAFLOGIN to refresh license status.
  • Verify you're logging in with the same email used for purchase.
  • Contact support if issue persists after re-authentication.

AutoCAD Integration

Issues specific to AutoCAD environment and API

Branch Solar toolbar tab not appearing

Related: CUI

Possible Causes

  • The Ribbon Tab isn't loaded in the current workspace
  • Workspace configuration wasn't refreshed after plugin installation
  • Custom workspace doesn't include the Branch tab by default

Solutions

  • Run the CUI command in AutoCAD.
  • In the top left window, find 'Workspaces' and click your current workspace (e.g., 'Drafting & Annotation Default (current)').
  • In the window that appears on the right, click the + icon next to 'Ribbon Tabs', then the + icon next to 'Branch'.
  • Click OK to close CUI—this refreshes the workspace and the Branch toolbar tab should appear.
  • If you don't see a 'Branch' entry under Ribbon Tabs, the plugin may not be loaded. Contact us through the website for support.

Branch commands not available in command line

Related: NETLOAD

Possible Causes

  • Branch plugin not loaded on startup
  • Plugin DLL blocked by Windows security
  • AutoCAD version incompatibility

Solutions

  • Type NETLOAD and manually load the Branch DLL from the installation folder.
  • Right-click the DLL file in Windows Explorer, go to Properties, and click 'Unblock' if present.
  • Verify your AutoCAD version is 2018-2026 (supported versions). AutoCAD LT is not supported.

Plugin installed but ribbon tab and commands don't appear (corporate/managed PCs)

Related: NETLOAD / CUILOAD

Possible Causes

  • Endpoint protection software (CrowdStrike, Carbon Black, Symantec, etc.) is silently blocking the plugin DLL from executing
  • IT group policy restrictions prevent .NET assemblies from loading in AutoCAD
  • AutoCAD recognizes the bundle in App Manager but the DLL never initializes, so the CUI file is never loaded
  • Windows has marked the downloaded DLL as blocked ("Mark of the Web")

Solutions

  • Step 1 — Verify the ribbon: Type CUILOAD at the AutoCAD command line. Browse to C:\Program Files\Autodesk\ApplicationPlugins\LeafSolarDesign2025+.bundle\Contents\<year>\LeafSolarDesign.cuix and load it. If the Branch ribbon tab appears, the CUI file is fine — the issue is with the DLL not loading.
  • Step 2 — Verify the DLL: Type NETLOAD at the command line. Browse to the same folder and select LeafSolarDesign<year>.dll (e.g., LeafSolarDesign2026.dll). If it loads successfully, both the ribbon and commands will work. If it fails, note the exact error message.
  • If NETLOAD shows "Assembly not loaded" or "Could not load file or assembly": Right-click the DLL in Windows Explorer → Properties → look for an 'Unblock' checkbox at the bottom of the General tab. Check it, click OK, and retry NETLOAD. Do the same for all .dll files in the folder.
  • If NETLOAD shows "System.IO.FileLoadException" or a security policy error: Your endpoint protection (CrowdStrike, Carbon Black, Symantec, etc.) is blocking the DLL. Ask your IT team to whitelist the folder C:\Program Files\Autodesk\ApplicationPlugins\LeafSolarDesign2025+.bundle\ so the plugin DLLs can execute.
  • If NETLOAD shows "Not a valid .NET assembly" or "BadImageFormatException": You may have the wrong AutoCAD version targeted. Confirm your AutoCAD year matches the DLL year (e.g., AutoCAD 2026 → LeafSolarDesign2026.dll). Contact support if the mismatch persists.
  • If CUILOAD works but NETLOAD fails, the ribbon tab will be visible but commands won't function. Send the exact NETLOAD error message to contact@leafautomation.ai and we can help diagnose the specific block.

Commands work but produce no visible result

Related: Multiple

Possible Causes

  • Results created on frozen or off layer
  • View zoomed to different area than where objects were created
  • Document locking issue preventing display update

Solutions

  • Run LAYER command and turn on all layers, then ZOOM EXTENTS.
  • Check that LAYERSTATE hasn't hidden relevant layers.
  • Try REGEN or REGENALL to refresh the display.

AutoCAD crashes during Branch operations

Related: Multiple

Possible Causes

  • Memory exhaustion on very large drawings
  • Conflict with other AutoCAD plugins
  • Graphics driver issues

Solutions

  • Save frequently and try processing large designs in sections.
  • Disable other third-party plugins temporarily to test for conflicts.
  • Update graphics drivers and try setting GRAPHICSCONFIG to a lower hardware acceleration setting.

Units seem wrong (panels appear tiny or huge)

Related: UNITS

Possible Causes

  • Drawing units don't match expected units
  • Inserted blocks from drawings with different unit settings
  • INSUNITS not set correctly

Solutions

  • Check UNITS command—Branch expects drawings in feet or inches depending on configuration.
  • Set INSUNITS before inserting blocks to ensure proper scaling.
  • Scale imported geometry to match your drawing's unit system.

Undo doesn't work correctly after Branch commands

Related: UNDO

Possible Causes

  • Complex operations span multiple undo marks
  • Transaction handling in plugin groups operations

Solutions

  • Use UNDO with a number to undo multiple steps at once.
  • Some Branch operations are atomic—they undo as a complete unit.
  • Save before major operations to have a recovery point.

SolarEdge PDF Import

Issues specific to IMPORTSOLAREDGEPDF workflow

PDF import fails completely

Related: IMPORTSOLAREDGEPDF

Possible Causes

  • PDF doesn't contain system layout page
  • PDF is proposal-only without panel positions
  • PDF is password protected or corrupted

Solutions

  • Re-export from SolarEdge Designer with 'System Layout' option enabled.
  • Ensure the PDF contains the visual panel layout diagram, not just text summaries.
  • Try re-downloading or re-exporting the PDF from SolarEdge Designer.

Imported panels are at wrong scale

Related: IMPORTSOLAREDGEPDF

Possible Causes

  • PDF doesn't contain reliable scale information
  • Different DPI settings in export

Solutions

  • After import, use AutoCAD's SCALE command to adjust geometry.
  • Reference known dimensions (like standard panel sizes) to calculate correct scale factor.
  • Typical panel dimensions: ~3.3' x 6.5' for 60-cell, ~3.4' x 6.9' for 72-cell modules.

String assignments not imported correctly

Related: IMPORTSOLAREDGEPDF

Possible Causes

  • PDF color coding lost in export
  • Complex multi-orientation designs
  • SolarEdge Designer version differences

Solutions

  • Use STRINGDATA to check what was imported, then manually adjust with ADDSTRING/DELETESTRING.
  • Re-solve strings with SOLVE if import didn't capture assignments.
  • Import captures layout geometry most reliably—string data may need verification.

General Best Practices

Before You Start

  • • Save your drawing before running Branch commands
  • • Ensure all panel blocks are on unlocked, visible layers
  • • Run BRANCH to verify module/inverter configuration
  • • Check LEAFSTATUS to confirm authentication is active

Workflow Order

  • • Always run BRANCH before other commands
  • • Create panel groups before solving strings
  • • Solve strings before creating homeruns
  • • Place inverters before running INVBALANCE

Drawing Preparation

  • • Use consistent panel block definitions
  • • Align panels to a regular grid where possible
  • • Remove duplicate geometry with OVERKILL
  • • Set correct drawing units (UNITS command)

Data Integrity

  • • Save in AutoCAD 2018+ DWG format
  • • Avoid WBLOCK with partial entity selection
  • • Use COPY instead of COPYCLIP within drawings
  • • Create template files with pre-configured settings

Diagnostic Commands

Use these commands to gather information when troubleshooting:

STRINGDATA

View all string data as JSON

LEAFSTATUS

Check authentication status

PANELGROUPSSOLVEDDEBUG

Debug panel group solver

BUGREPORT

Submit detailed bug report

Start Free Trial — 14 days free