[𝗣𝗩𝘀𝘆𝘀𝘁 𝗶𝘀 𝗴𝗲𝗮𝗿𝗶𝗻𝗴 𝘂𝗽 𝗳𝗼𝗿 𝗮𝗻 𝗲𝘅𝗰𝗶𝘁𝗶𝗻𝗴 𝘆𝗲𝗮𝗿 𝗼𝗳 𝘀𝗰𝗶𝗲𝗻𝘁𝗶𝗳𝗶𝗰 𝗰𝗼𝗻𝗳𝗲𝗿𝗲𝗻𝗰𝗲𝘀 𝗶𝗻 𝟮𝟬𝟮𝟰!]

We are thrilled to announce our participation in two must-attend conferences in the solar energy and photovoltaic technology sector. Join us to share knowledge, discover the latest innovations, and network with industry experts.

𝟭.   𝗣𝗩𝗣𝗠𝗖 𝗪𝗼𝗿𝗸𝘀𝗵𝗼𝗽 – 𝗠𝗮𝘆 𝟳-𝟵, 𝗦𝗮𝗹𝘁 𝗟𝗮𝗸𝗲 𝗖𝗶𝘁𝘆
In our next presentation, our scientific collaborators Michele Oliosi, Agnès Bridel and Bruno Wittmer will showcase the advancements of PVsyst that will end up supporting the industry. During this conference, we will highlight the improvements and updates implemented in the PVsyst Version 7 software.
 
We will also describe the initial features of the upcoming PVsyst 8 release and, for the first time, introduce how PVsystCLI works.
 
𝟮.   𝗘𝗨𝗣𝗩𝗦𝗘𝗖 – 𝗦𝗲𝗽𝘁𝗲𝗺𝗯𝗲𝗿 𝟮𝟯-𝟮𝟳, 𝗩𝗶𝗲𝗻𝗻𝗮
Don't miss us at EUPVSEC, one of the largest European forums dedicated to photovoltaic technology.
 
Come discover how PVsyst is helping shape the future of solar energy. It's the perfect opportunity to interact with our experts, learn more about our latest solutions, and see how we can work together towards a more sustainable future.
 
We look forward to meeting you and sharing our passion for innovation in solar energy.

[Ongoing Development of PVsyst 8 and PVsystCLI]

Scheduled Release by the End of the First Half of 2024

We are thrilled to anticipate the upcoming release of two groundbreaking products.   Presently in the development phase, PVsyst Version 8 and PVsystCLI are set to deliver substantial enhancements to our product portfolio. We are targeting the release of these two products by the end of the first half of 2024. PVsyst Version 8   Some clarifications regarding the terms of use for PVsyst 8 licenses: Subscriptions for version 7 will be valid for version 8 during their validity period; Licenses purchased for version 8 will be valid for version 7.          PVsyst Version 8 represents a significant advancement in the functionality of our software, emphasizing our commitment to improving the planning and implementation of solar projects. Major updates in PVsyst Version 8 include: Enhanced Orientation Management: Unlimited orientations Integration of trackers and fixed orientations in the same simulation Specialized bifacial models for each orientation Configurable inverter inputs Improved 3D Scene Functionality: Terrain image import from maps Direct import of topography 3D view with geographical coordinates Advanced terrain image management Enhanced 3D editor user interface Orientation control tool Flexible object rotation on X/Z axis Enhanced Bifacial System: Manual Adjustment of Pitch Value in Backside Irradiance Model Selective Bifacial Modeling Enhancements to Vertical Bifacial Modeling Complete Overhaul of the Help: Online Help Access Transform to Array Guide Comprehensive Redesign of Help   Additional new features are currently in development and will be available soon. We will continue to inform you of our developments as they progress. PVsystCLI    Some clarifications regarding the terms of use for PVsystCLI licenses: The subscription is independent from PVsyst 8 and does not provide access to the PVsyst 8 software interface; The PVsystCLI license can be transferred once a month; PVsystCLI can be installed on a server and/or used via Remote Desktop. PVsystCLI provides a suite of features aimed at improving the efficiency and adaptability of simulations for solar projects. The main characteristics are as follows: Command Line Interface (CLI): Provides a streamlined, text-based interface for executing PVsyst simulations, allowing for automation and integration with other software tools, enhancing the workflow for advanced users.   Customizable Simulation Commands: Enables users to define specific simulation parameters and commands directly through the CLI, offering unparalleled customization for each project's unique requirements.   Efficient Meteorological Data Conversion: Facilitates the conversion of meteorological data files into formats compatible with PVsyst, streamlining the data preparation process for simulation.   Automated Simulation Process: Automates the execution of simulations based on user-defined commands, significantly reducing manual intervention and increasing productivity.   Detailed Reporting: Generates comprehensive final reports that include customizable charts and deliverables, providing in-depth insights into the simulation outcomes.   Comprehensive CSV File Output: Outputs extensive CSV files detailing the simulation results, enabling further analysis and data manipulation in other software applications.   Flexibility and Integration: Designed to work seamlessly within a broader technological ecosystem, allowing for integration with batch processes, other software tools, and automated systems.   High-Performance Simulations: Leverages the computational power of PVsyst for high-efficiency simulations, supporting complex projects and large datasets. These features make PVsystCLI an invaluable tool for solar energy professionals looking to optimize their project planning and analysis processes with high precision and minimal effort. More details : https://mailchi.mp/pvsyst.com/ongoing-development-of-pvsyst-8-pvsystcli

[𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗣𝗩𝘀𝘆𝘀𝘁 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟴 𝗮𝗻𝗱 𝗣𝗩𝘀𝘆𝘀𝘁𝗖𝗟𝗜]

We are excited to announce the impending release of two transformative products from PVsyst in 2024: PVsyst Version 8 and the new PVsystCLI.

𝗣𝗩𝘀𝘆𝘀𝘁 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟴: 𝗥𝗲𝗱𝗲𝗳𝗶𝗻𝗶𝗻𝗴 𝗣𝗵𝗼𝘁𝗼𝘃𝗼𝗹𝘁𝗮𝗶𝗰 𝗦𝘆𝘀𝘁𝗲𝗺 𝗗𝗲𝘀𝗶𝗴𝗻

PVsyst Version 8 marks a significant leap in our software's capabilities, reflecting our dedication to advancing solar project planning and execution.

Key Enhancements in PVsyst Version 8 include:
𝟭. 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗢𝗿𝗶𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁:

• 𝗨𝗻𝗹𝗶𝗺𝗶𝘁𝗲𝗱 𝗡𝘂𝗺𝗯𝗲𝗿 𝗼𝗳 𝗢𝗿𝗶𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻𝘀: Customize projects without constraints on the number of orientations.
• 𝗧𝗿𝗮𝗰𝗸𝗲𝗿𝘀 & 𝗙𝗶𝘅𝗲𝗱 𝗢𝗿𝗶𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻: Unique capability to combine trackers and fixed planes within the same simulation.
•𝗗𝗲𝗱𝗶𝗰𝗮𝘁𝗲𝗱 𝗕𝗶𝗳𝗮𝗰𝗶𝗮𝗹 𝗠𝗼𝗱𝗲𝗹𝘀 𝗳𝗼𝗿 𝗘𝗮𝗰𝗵 𝗢𝗿𝗶𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻: Enhance accuracy in bifacial system design.
• 𝗜𝗻𝘃𝗲𝗿𝘁𝗲𝗿 𝗜𝗻𝗽𝘂𝘁 𝗖𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻𝘀: Mix any two orientations per inverter input for greater system design flexibility.

𝟮. 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝟯𝗗 𝗦𝗰𝗲𝗻𝗲 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹𝗶𝘁𝘆:

• 𝗧𝗲𝗿𝗿𝗮𝗶𝗻 𝗜𝗺𝗮𝗴𝗲 𝗜𝗺𝗽𝗼𝗿𝘁 𝗳𝗿𝗼𝗺 𝗠𝗮𝗽𝘀: Streamline the integration of real-world terrain into project planning.
• 𝗗𝗶𝗿𝗲𝗰𝘁 𝗜𝗺𝗽𝗼𝗿𝘁 𝗼𝗳 𝗧𝗼𝗽𝗼𝗴𝗿𝗮𝗽𝗵𝘆: Achieve more accurate shading and layout analysis.
• 𝗚𝗲𝗼𝗴𝗿𝗮𝗽𝗵𝗶𝗰 𝗖𝗼𝗼𝗿𝗱𝗶𝗻𝗮𝘁𝗲𝘀 𝗶𝗻 𝟯𝗗 𝗩𝗶𝗲𝘄𝘀: Enhance design accuracy with visible geographic coordinates.
• 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱 𝗧𝗲𝗿𝗿𝗮𝗶𝗻 𝗜𝗺𝗮𝗴𝗲 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁: Enhanced control and detail for terrain representation.
• 𝗜𝗺𝗽𝗿𝗼𝘃𝗲𝗱 𝗨𝘀𝗲𝗿 𝗜𝗻𝘁𝗲𝗿𝗳𝗮𝗰𝗲 𝗶𝗻 𝟯𝗗 𝗘𝗱𝗶𝘁𝗼𝗿: Intuitive, reorganized menus for an enhanced user experience.
• 𝗢𝗿𝗶𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗖𝗼𝗻𝘁𝗿𝗼𝗹 𝗧𝗼𝗼𝗹: New feature for precise orientation adjustments.
• 𝗙𝗹𝗲𝘅𝗶𝗯𝗹𝗲 𝗢𝗯𝗷𝗲𝗰𝘁 𝗥𝗼𝘁𝗮𝘁𝗶𝗼𝗻 𝗼𝗻 𝗫/𝗭 𝗔𝘅𝗶𝘀: Additional design versatility with expanded object rotation capabilities.

𝗣𝗩𝘀𝘆𝘀𝘁𝗖𝗟𝗜: 𝗦𝘁𝗿𝗲𝗮𝗺𝗹𝗶𝗻𝗶𝗻𝗴 𝗣𝗵𝗼𝘁𝗼𝘃𝗼𝗹𝘁𝗮𝗶𝗰 𝗦𝗶𝗺𝘂𝗹𝗮𝘁𝗶𝗼𝗻𝘀 𝗮𝗻𝗱 𝗗𝗮𝘁𝗮 𝗖𝗼𝗻𝘃𝗲𝗿𝘀𝗶𝗼𝗻

In response to the evolving needs of the industry, we are proud to introduce PVsystCLI, a command line interface designed to run simulations and convert meteorological data files with unprecedented efficiency and flexibility.

As we move towards the launch of these innovative products, we look forward to providing more detailed information on their features and benefits. PVsyst Version 8 and PVsystCLI are more than just tools; they represent our commitment to empowering your solar energy projects with the latest in technology and efficiency.

We appreciate your continued support and are eager to see how these advancements will enhance your work in 2024 and beyond.

[Where can I find .ond files?]

Dear Sir,

 We update the database using the requests of the manufacturers, and publish it with each new issue of PVsyst.

 We can't of course follow all the new products of all manufacturers in the world.  We don't want to include data without the acknowledgement of the manufacturer.

 Nevertheless you can easily create your own components by yourself.

 The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database.

 You have a tutorial for that on youtube:  https://www.youtube.com/c/PVsystTutos,   page  Component database

 Regards,
 

[Doesnt have solis inverter?]

Dear Sir,

 We update the database using the requests of the manufacturers, and publish it with each new issue of PVsyst.

 We can't of course follow all the new products of all manufacturers in the world.  We don't want to include data without the acknowledgement of the manufacturer.

 Nevertheless you can easily create your own components by yourself.

 The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database.

 You have a tutorial for that on youtube:  https://www.youtube.com/c/PVsystTutos,   page  Component database

[string configuration]

Dear Sir,

We update the database using the requests of the manufacturers, and publish it with each new issue of PVsyst.

We can't of course follow all the new products of all manufacturers in the world.  We don't want to include data without the acknowledgement of the manufacturer.

Nevertheless you can easily create your own components by yourself.

The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database.

You have a tutorial for that on youtube:  https://www.youtube.com/c/PVsystTutos,   page  Component database

Regards,
 

[How to optimize simulation time]

The speed of the simulation mainly depends on the complexity of the system and the complexity of the 3D scene you are trying to simulate.

Here are a couple of ideas:

• In the 3D scene:

When near shadings are used, the calculation of the shading factor basically requires to compare each elementary surface to each PV table (goes with the square of the number of elements)

1. You can simplify the calculation by using arrays of tables instead of single PV tables if your tables are well aligned;
    
2.  The shading calculation with trees is very slow, as each face of each tree has to be calculated independently. For tree arrays, you are advised  to use a single parallelepiped;
    
3. A significant time may also be due to the pre-calculations for the optimization of the shading factor calculation, or the check that each table should not interpenetrate any other table or objects. Try to avoid interpenetrating objects;
    
4.  Too much detail in the topography will lead to long import and simulation durations and possibly slows down the user interface.

There is a limit of 500’000 unique points when importing topography data through a CSV file, and a maximum of 1’000’000 triangles when the triangulation is performed. In the ground data details, you can use the simplification tool to reduce the number of points.

 

• System definition:
   

1. You can simplify the definition of the system if you have defined many sub-arrays with a single inverter. This will make the simulation very slow, and it is best to group identical inverters in the same sub-arrays;
    
2. Using the multi-MPPT feature will slow down the calculation. If possible, you can disable it, which means considering inverters as a whole;
    
3. With string inverters, the simulation is performed for each inverter input, which significantly increases the simulation time.

 

• Shadings calculation:
   

1. When using the “Module Layout” for electrical mismatch effects, defining more than 1’000 - 1’500 modules leads to extremely long calculation times;
    
2. You can simplify the shadings calculation by using "According to module strings", and if necessary the "Fast (table)" option, instead of "Detailed electrical calculation (acc. to module layout)". The shadings calculation will be less accurate but it should be much faster.
    

Here is the link to the help page that explains how to set up partitioning:
https://www.pvsyst.com/help/index.html?shadings_partitioninstrings.htm

In the slow case, at each simulation step the shading factor is recomputed.

 

[Solaredge]

Dear Berthiaud, 

The SolarEdge architecture obeys very strict rules, established by SolarEdge. PVsyst strictly applies these rules.

These rules namely define the compatibility conditions between the optimizer and the inverter models, , as well as some maximum sizing and operating limits.

 Please ask the SolarEdge team.

[CanadianSolar modules]

Dear Massimo, 

We update the database using the requests of the manufacturers, and publish it with each new issue of PVsyst.

We can't of course follow all the new products of all manufacturers in the world.  We don't want to include data without the acknowledgement of the manufacturer.

Nevertheless you can easily create your own components by yourself.

The easiest way is to choose a similar existing device in the database, modify its parameters according to the manufacturer's datasheets, and save it under a new name, therefore creating a new file in your database.

You have a tutorial for that on youtube:  https://www.youtube.com/c/PVsystTutos,   page  Component database

[String sizing]

Dear Pvfrance, 

When you have a different number of strings on the MPPT inputs, you should create one sub-array for each configuration (for example one sub-array for the MPPTs with a single string, and another one for the MPPTs with two strings).

Then, in ‘power sharing’, you tell PVsyst which sub-arrays belong to the same inverter and how the power of the inputs is balanced.

I have attached a PDF document to this e-mail with short examples on how to proceed. You can also find more information in the help under:

‘Project design > Grid-connected system definition > Multi-MPPT inverters’

‘Project design > Grid-connected system definition > Multi-MPPT inverters: power sharing’

 

[PAN file import problem]

You must check that the manufacturer's name is written correctly and you must restart PVsyst after an import.

["Strongly Oversized" Warning in 12 MPPT Inverter]

The error message in red is normal. You have defined a PV power on your main input well below its nominal power (55 KWac). You need to increase the number of strings on this main input

[Error in Module layout]

Dear Michalis Angeli,

The « Module Layout » calculation is based on the internal geometric arrangement of the sub-modules.

See the help  “Physical models used > PV Module - Standard one-diode-model > PVModule Structure > Submodules”.

This submodules partition is defined in the PV module definition, page “Sizes and technologies”.

Now only the options “In length”, “In width” and “Twin Half cells” or Twin Third cells” have been implemented in PVsyst. 

More and more PV modules have other exotic configurations. You cannot use this option with other layouts.

This error message was added rather recently (some few months ago), for avoiding erroneous calculations.   It is possible that your previous simulation has been done before this protection.

In your old calculation, the electrical shadings calculation may be not quite accurate.

The only way for avoiding this problem is to cheat, by redefining your PV module with an allowed submodule layout.

However in this case, the electrical shading calculation accuracy cannot be guaranteed with respect to the reality.

[Layout and partition of modules]

We cannot adapt to technologies that are not clearly defined. 

Manufacturers dont' communicate on the internal electrical wiring of the cells.

We therefore cannot "guess" how the shading affects this PV module via the layout module.

You can use the shading scene to calculate a shading and electrical loss factor via "partition"

[Layout and partition of modules]

More and more PV modules have other exotic configurations. You cannot use this option with other layouts.

[Layout and partition of modules]

Dear Meurville,

The « Module Layout » calculation is based on the internal geometric arrangement of the sub-modules.

See the help  “Physical models used > PV Module - Standard one-diode-model > PVModule Structure > Submodules”.

This submodules partition is defined in the PV module definition, page “Sizes and technologies”

Now only the options “In length”, “In width” and “Twin Half cells” or Twin Third cells” have been implemented in PVsyst. 

More and more PV modules have other exotic configurations. You cannot use this option with other layouts.

 This error message was added rather recently (some few months ago), for avoiding erroneous calculations.   It is possible that your previous simulation has been done before this protection.

In your old calculation, the electrical shadings calculation may be not quite accurate.

The only way for avoiding this problem is to cheat, by redefining your PV module with an allowed submodule layout.

However in this case, the electrical shading calculation accuracy cannot be guaranteed with respect to the reality.

Regards,

 

[Ohmic Losses - Dc cables]

Dear Michalis, 

In your case you must define the average length of a string.

Then PVsyst will calculate the resistance of the DC circuit taking into account the number of strings in your system.

At this location, the number of MPPTs is not taken into account in the calculation of DC losses. We will take into account the number of inverters and strings

Regards

[40th European Photovoltaic Solar Energy Conference (EUPVSEC)]

The EUPVSEC conference will start in 5 days, as a reminder :
We are pleased to announce that our collaborators #BrunoWittmer, #MicheleOliosi and #AgnesBridel will be present at the 40th European Photovoltaic Solar Energy Conference which will take place in Lisbon (Portugal) from September 18 to 22, 2023.

For more information : https://www.eupvsec.org

PVsyst will be presenting two posters
Poster N°1: Limits of the single diode model in view of its application to the latest PV cell technologies
Poster N°2: Accounting for sub-hourly irradiance fluctuations in hourly performance simulations

We look forward to seeing you there

[PVSYST training]

Dear Meurville, 

Thank you very much for your interest in a PVsyst training.

 

We propose some online personalized sessions in the form of Consulting and PVsyst project support, to answer specific requests (no standard sessions for the moment).

 

If you are interested in this service, you are kindly requested to request an online quote here: https://www.pvsyst.com/consulting/

 

We will establish a program relevant to your specific requirements.

Our sessions last for 2 hours (including participants question time) and are charged CHF 700.-

Our online sessions are limited to 5 participants per session.

 

We do not provide any guarantee relating to your simulation results.

 

In the meantime, we have designed several online video tutorials which we invite you to watch:

https://www.youtube.com/channel/UCMzsEWHk3f7XD_dg1lngmzg  or access our online course at: https://vimeo.com/pvsyst

 

If you have a technical question, please feel free to send an email to support@pvsyst.com

 

With best regards,

[THERMAL PARAMETER LOSSES PVSYST]

Dear Michalis Angeli,

In the absence of reliable measured data, PVsyst proposes default values without wind dependency   (i.e. assuming an average wind velocity):

- For free-standing (open-rack) systems, i.e. with air circulation all around the collectors), according to our measurements on several installations:  

Uc =  29  W/m²·k,            Uv = 0   W/m²·k / m/s

- Therefore for fully insulated backside  (no heat exchange at the backside, only one side contribution to the convecting heat exchange), the U value should be divided by 2:  

Uc =  15  W/m²·k,            Uv = 0   W/m²·k / m/s

- For intermediary cases (semi-integration, air duct below the collectors), the value should be taken between these 2 limits, but preferably lower than 22  W/m²·k as the air heat removing is often not very efficient. The default value proposed by PVsyst for any new project is  

Uc =  20  W/m²·k,            Uv = 0   W/m²·k / m/s

 We have chosen this value as general default, because we consider that it is more representative of usual rooftop systems, managed by "less professional" people who will not necessarily modify the PVsyst default. For big systems, we suppose that trained engineers will indeed adjust this parameter (for example at 29 W/m² for row-like big power plants). 

- For domes, a manufacturer has measured the U-value on several installations  (height about 40 to 70 cm above the ground): 

Uc =  27  W/m²·k,            Uv = 0   W/m²·k / m/s: 

Now if reliable hourly wind velocity data are present in the data, we don't have any reliable measured data with wind.

PVUSA proposes the following thermal correlation, widely used for the free-standing (open-rack) situations when wind speed data are available.

Uc =  25  W/m²·k,            Uv = 1.2  W/m²·k / m/s 

This corresponds to our default 29 W/m2, when the average wind velocity is 3.3 m/sec (rather usual in continental - not coast situations).
 

[Using optimizers in power sharing]

Dear Emi,

If you can, you should mix orientation 1 & 2 and then separate orientations 4 & 5.
Attention, its not at all conventional to put two strings of different length on a single MPPT input

[PAN file import problem]

Is is indicated in the PAN file that this PV module is no longer present on the market. 

You must therefore choose "all modules" in the "availability" filter.

[PAN file import problem]

Dear LFurzsina,

Maybe there is a problem in the definition of the PAN file. 

Can you send the PAN file to support@pvsyst.com ?

 

[AC Losses in tranformer]

Dear Shashank Sharma,

These losses appear in the following loss diagram:

 

[Using optimizers in power sharing]

Dear Emi, 

You can simulate virtually your entire project.

Attention it is not possible in PVsyst to mix two orientations with different lengths of strings. 

I just made your system under PVsyst, you just need to make a little change in the naming of the orientations in order to simulate your system correctly.