Jump to content

Lazare Fesnien

Administrators
  • Posts

    269
  • Joined

  • Last visited

Posts posted by Lazare Fesnien

  1. Dear Kittitut,

     When receiving PAN files from manufacturers, these usually define some parameters – not mentioned on the datasheets – which considerably boost the performance of their modules in the simulation.

    These PAN files may often be directly provided by “independent” laboratories (claimed as “certified”).

    PVsyst tries to detect these anomalies, and gives you this information.  In these cases you are advised to use default parameters proposed by PVsyst, which are usually more realistic.

     There are mainly 2 classes of such uncertain parameters:

    • The IAM profile. We are convinced that the IAM of most PV modules should follow the Fresnel’s physical laws, either for normal glass or for AR coatings. We received measurements from very serious laboratories which are very close to Fresnel. And we had still this confirmation recently after an informal discussion with a responsible of a well-known laboratory in the USA.  See our FAQ   https://forum.pvsyst.com/topic/1190-how-to-determine-the-iam-profile/#comment-3181
    • The low-light efficiency as measured by some laboratories  is often biased by the fact that the filters used for the measurements at 200 and 400 W/m2 deliver slightly higher irradiance than nominal. I have analyzed many measurement reports from these labs,  and observed that the Isc/G ratio is not stable, as it should be. When correcting this the low-light efficiency usually stays between -3% and -2%, rarely higher. See our FAQ  https://forum.pvsyst.com/topic/1030-how-are-specified-the-pan-files-in-the-pvsyst-database/#comment-2731

    When using these boosted PAN files in your simulations, you have the risk of getting over-estimated simulation results with respect to the real system..

    Regards,

  2. This will describe how to use PVsyst on an Azure Virtual Machine, which is different from Azure Virtual Desktop. Azure Virtual Dekstop is not suitable for PVsyst as it is running on a specific Windows version which is actually a Server version.

    To be able to use PVsyst on Azure VM you need to make sure that you attach a secondary hard drive to the VM because the OS harddisk ID will always change when rebooting the machine.

    So basically you can create a basic HDD (not even an SSD) of 32GB (minimum available size now) and attach it to the VM prior to activating PVsyst.

    If you already activated PVsyst on the machine, you need to contact our support in order to reset your license : https://www.pvsyst.com/contact/

  3. We update the database using the requests of the manufacturers, and publish it with each new release 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

  4. To do this, you must create different sub-arrays.

    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’

  5. Thank You for Joining Our Webinars! 🌟

    We were thrilled to see so many of you participate in our two webinars on PVsyst 8 and PVsystCLI, and we sincerely thank you for your engagement and enthusiasm.
    Your questions were insightful and made the discussions even more enriching.

    📄 To continue the conversation and address your queries, we’ve compiled all the questions asked during the webinars, along with our answers, into a handy PDF document. It’s now available for you to browse and download.

    Webinar_Q&A.pdf

  6. We are thrilled to announce the launch of three new YouTube channels, each dedicated to a specific language to better serve your needs.
     
     
    👉 From now on, our current YouTube channel will feature content exclusively in English, while the new channels will host videos in their respective languages.
    We hope this initiative will make it easier for you to access our content in the language you’re most comfortable with.
     
    🔔 Don’t forget to subscribe to the channel that matches your preferred language to stay up-to-date with our latest videos! We wish you a joyful holiday season filled with happiness and success!
  7. We update the database using the requests of the manufacturers, and publish it with each new release 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

  8. We update the database using the requests of the manufacturers, and publish it with each new release 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

  9. Dear Tobi,

    The SolarEdge architecture follows very complex and strict rules specified by the folks at SolarEdge.
    PVsyst scrupulously applies these rules, they are irreversible.
    These rules define in particular the conditions of compatibility between optimizers and inverters. This implies that all components are specified in the internal PVsyst database.

    If an inverter is not referenced in the PVsyst database, it cannot be used.
    Please ask SolarEdge to update their products in PVsyst.

    Regards,

  10. Dear Hritik, 

    Where does the PAN file come from? Does it come directly from the manufacturer?
    There may have been a modification of the technical sheet between the creation of the PAN file and the marketing of the component.

    You can update the component yourself if you notice any differences.

    For the temperature coefficient you can choose to define it in mA/°C or by %/°C, PVsyst will automatically calculate the other value.

    Regards,

×
×
  • Create New...