This task allows you to define the module specifications that will be used in your site.
Import from a PAN File
You can import a module specification from a PVsyst
*.PAN file. Only text-based PAN files are supported (from PVsyst version 6.40 onwards). PAN files in binary format (usually from older versions of PVsyst) can unfortunately not be read.
Supported module types
SolarFarmer supports importing the following module configurations from PAN files:
Silicon (Mono and poly crystalline)
|Cells across width||Cells along length||Total cells||Cells in each submodule|
|Cells across width||Cells along length||Total half-cells||Half-cells in each submodule|
|6||20||120||2 * (20/20/20)|
|6||22||132||2 * (22/22/22)|
|6||24||144||2 * (24/24/24)|
|5||30||150||2 * (15/45/15)|
|6||26||156||2 * (26/26/26)|
|8||24||192||2 * (24/48/24)|
|8||32||256||2 * (32/64/32)|
Portrait (strips down the length of the module) or landscape (strips down the width of the module).
Cadmium Telluride, Amorphous Silicon (single / tandem / triple junction), Microcrystalline Silicon
HIT (Heterojunction Intrinsic Thin film)
This technology of module specifications is supported (using the configurations above).
Defining the Properties
If you choose to import a PAN file or create a brand-new module specification, you are presented with multiple properties, organised into groups.
The Electrical Configuration tab contains more electrical-related properties, along with a chart displaying various properties of the specification.
Any validation errors in the values will be highlighted in red, with additional validation information appearing at the top in a red (errors) or orange (warnings) drop-down. Any errors must be rectified before the module specification can be used in the energy yield calculation.
You can also choose to export the module specification values to a file (
*.ModuleSpec). This is a proprietary SolarFarmer format
and can be imported into other SolarFarmer workbooks.
You can specify whether a module specification is bifacial or not with the properties in the 'Bifacial' group (this is also set automatically when you import from a PAN file). If checked, the module is defined to be bifacial and will be modelled in the energy calculation.
The bifaciality factor is the fraction (in %) of the front side efficiency to convert back side irradiance to electricity. Other bifacial-related factors (shade, transmission and mismatch factors) are set later for each layout region.
For silicon crystalline modules you can specify whether a module specification is half-cell in the 'Half-Cell Module' group (this is set automatically when you import from a PAN file). If checked, the module is defined to be half-cell and will be modelled in the calculation accordingly.
The cell arrangement options are updated to reflect the properties. The appropriate one will be set after you import a PAN file:
Angular Losses Model (IAM)
The Incidence Angle Modifier (IAM) describes how much of the irradiance incident on the surface of the module penetrates the surface and enters the solar cells that make up the module, where conversion of light to electrical energy takes place.
SolarFarmer supports 5 different angular loss models:
ASHRAE model. Defined by a single parameter b0 (typical value of 0.05).
CIEMAT model (proposed by N. Martin & J.M. Ruiz). Defined by a parameter ar. See CIEMAT in the Calculation Reference for more details of this.
Fresnel normal glass. A predefined profile for optical losses as a function of the incidence angle applicable to normal glass based on Fresnel equations. See Pointwise in the Calculation Reference for more details of this.
Fresnel anti-reflective (AR) coated glass. A predefined profile for optical losses as a function of the incidence angle applicable to anti-reflective (AR) coated glass based on Fresnel equations. See Pointwise in the Calculation Reference for more details of this.
User defined profile model. You can define a user-defined profile for the angular loss model in PVsyst. We support this option. Currently you can only define the points by importing the values from an existing PAN file.