Skip to main content
Release Notes 1.32 - 1.33

Mounting plan, Ballast calculation, PDF report export, Irradiance analysis of EW system on sloped roofs

Agne Janusevska avatar
Written by Agne Janusevska
Updated over a week ago

In this release, we will cover:

  • How to work with mounting provider PanelClaw;

  • PanelClaw ballast calculation;

  • PanelClaw PDF report export;

  • Irradiance analysis of EW systems on sloped roofs

PVcase Roof Mount integration with mounting provider PanelClaw

PVcase Roof Mount streamlines the process of PV design on the rooftop. With this release, users can now choose and adapt mounting systems more efficiently within one tool, significantly reducing the need for double work. This integration with one of the providers saves users valuable time and effort by allowing them to perform these tasks directly within the product.

User flow

Module settings

  1. Adding modules:

  • Users must provide a weight for each module, which is mandatory for mounting.

  • If a module without a specified weight is selected in the ‘Layout settings’, users must return to ‘Module settings’ to provide the weight.

Layout settings

  1. Enabling mounting feature:

  • The user must ensure that 'Mounting' is enabled to move on with mounting.

  • The default mounting provider is PanelClaw (more providers will be available in the future).

2. Module selection in Layout settings:

  • The system checks if the selected module matches the requirements.

  • Users are advised and cannot proceed with the selection if not supported.

3. Mounting product:

  • The default mounting product is Wave (more options will be available in the future).

4. Spacing settings and corridors:

  • Users can’t change the spacing between modules because it is a default setting related to the Wave product that provides PanelClaw.

  • Corridors can be changed manually by the user's preferences.

5. Placing modules and limitations:

  • Users click 'Place modules' and select the PV area/roof for generation, per usual flow. Modules are generated.

  • The user needs to be aware of the applicable roof requirements for this generation, which state that no inclination of the rooftop is allowed.

  • If modules are placed too close to the parapet (closer than 30 cm), the system will automatically address this by moving the modules to the 30 cm mark for safety reasons.

Mounting ballast calculator

After layout generation, when the mounting choice is enabled, the user must ensure that the mounting plan, wind, and snow load are calculated and .pdf is exported. Therefore, select the ‘Mounting calculator’ button.

  1. Generating reports:

  • Users can select a PV area or rooftop to generate the report.

  • After PV area is selected, the user can reselect it.

2. Geolocation:

  • The software uses the existing geolocation for calculations chosen in the Settings unless the user changes it within the calculator under 'Coordinates'.

3. Terrain and environment details:

  • The software displays details of the terrain and environment according to country/compliance standards.

  • The tooltip on the Terrain category offers more information when hovering over the '?' icon.

4. Roof material:

  • Users must select a rooftop material from the dropdown menu to ensure that the mounting product is adapted to it.

Exporting project plan

To export the project plan:

  • Click on the 'Export project plan'.

  • Choose a location where you want to save the plan, and that’s it — you exported the plan.


Irradiance analysis of EW systems on sloped roofs

In this release, users are now able to run yearly shading loss analysis and yearly in-plane irradiation analysis for EW systems on sloped roofs. Users can retrieve the analysis results by following the same flow as before:

  • Click on Shading Analysis

  • Set project location by clicking on the globe icon or entering latitude, longitude

  • Click on Run Irradiance Analysis

  • Click Display to see analysis results

For more in-depth explanation of our irradiance analysis feature, head to Release Note 1.29.

Did this answer your question?