This tutorial contains GIF images.
If they fail to load please visit the help center via web browser.
You can zoom this page with Ctrl+.


In this tutorial we will discuss steps that need to be taken in order to import your 3D layout to PVsyst for yield estimation.

Export

PVsyst 7 now supports a new unique PVcase format - .PVC. Using this format the importation is way easier and you don't need to select additional information like the tilt angle or correct measurement units - it will be automatically recognized.

After selecting .DAE or .PVC format, you will have two options:

  1. Frames - PVcase will export frames and trees;
  2. Terrain and frames - PVcase will export frames, trees and selected terrain meshes as well.

πŸ›ˆ Note: Terrain and frames option will appear if you have a terrain mesh already generated in the layout.

Frame export

If you select only Frames, please select the location for the export and a .DAE/.PVC file will be saved.

Terrain and frame export

If you select Terrain and Frames, select the mesh and finally select the location for the exportation and a .DAE/.PVC file will be saved.

πŸ›ˆ The density and size of the mesh impact the import speed of PVsyst.
πŸ›ˆ If you would like to learn how to prepare terrain mesh on topographic survey, click here:

How to import .PVC format to PVsyst software:

1. Open PVsyst 7 software and select the Near shadings tab.

2. Click on Construction / Perspective.

3. Press File β†’ Import β†’ Import a 3D scene (3DS, DAE, PVC) , and select your exported .PVC file.

4. In Import results PVsyst will automatically read the units that were used while creating the project in PVcase.

5. Click OK.

πŸ›ˆ The density and size of the mesh impact the import speed of PVsyst.

How to import .DAE format to PVsyst software:

1. Open PVsyst sofware and select Near shadings tab.

2. Select Construction / Perspective tool.
3. Press File β†’ Import β†’ Import a 3D scene (3DS, DAE) , and select your exported .dae file.
4. In Import results windows select the input size - depending on your drawing this can be either in metric or imperial units.
5. In Import results windows select PV objects sub tab and check Frames
(3D frames , 3D trees and 3D mesh will be imported automatically).

πŸ›ˆ The density and size of the mesh impact the import speed of PVsyst.

Additional notes:

Automatic identification

When defining PV fields in a shading scene, PVsyst will always try to identify their orientations automatically, grouping all similar fields into the same orientations. This is the normal behavior because the field properties give all the information needed to do so.

Problems arise when the fields are not created with a regular layout, for example when they follow the ground slope, meaning that there are too many different orientations. When this happens, we need to either increase the grouping tolerance or find other ways to get realistic orientations.

This can be solved by deleting all of the orientations and assigning the frames to the same orientation. PVsyst will retain all of the individual table orientation properties even though it will show one orientation in the final report, while you actually have more.Β 

"An error occured in PVsyst":

This error can occur when you import the 3D scene and don't save it. To workaround this you must first close the "Near Shading" window by clicking on the "Close" button. Then you can re-open the Construction / Perspective window again and it should be working just fine.

"X fields in the shadings don't have a corresponding orientation in the 'Orientation' part":

At this point you have to click the Update Orientation Parameters.
When you click this it’s updated and should fix itself, if it does not you have to fix the orientation parameters. Β 

Additional orientations done by PVsyst:

After importing into PVsyst there might be a third orientation created mistakenly. You have to delete this orientation.

PVsyst orientation behavior from PVsyst help

Zones of tables

Fields are grouped within the same zone, and with other zones if they share the same tilt and azimuth definitions.

Random scene

The first field is considered as a reference, then PVsyst tries to match other fields and if they don't it defines a new orientation.

For all scenarios, PVsyst then computes an average tilt and azimuth for each orientation from its fields.

This is the way orientations are defined automatically since PVsyst 6.64, but before that they were always defined using the "Random scene" algorithm which was not accurate enough and could lead to very odd orientation definitions. Also, there were no averages computed afterwards, the orientation tilt and azimuth were the ones from the first reference field.

Warning messages will pop up if you try to open an old variant with newly identified orientations that differ from the stored ones, therefore creating an incompatibility between the variant Orientation part and the shadings part. You can click on Yes and save your variant again to validate it again.

Did this answer your question?