Jump to content

developer_mh

Administrators
  • Posts

    1,790
  • Joined

  • Last visited

  • Days Won

    167

Everything posted by developer_mh

  1. Hi Krzysztof, we have not encountered this error before, but it seems that you are on the right track. Did you try to run the Windows Update after installing the C++ redistributables? And also, as always in Windows, don't forget to restart your system. Kind regards, Martin
  2. Hi ChaseSecrist, I will forward this enquiry to our database team so that they can enter the inverter. How does PV*SOL say that the inverter is not compatible? Can you give us more detail on the configuration you wanted to achieve? Thanks in advance, kind regards, Martin
  3. Hi Miguel, you can also add your own company to the database and then use it. Go to database -> Companies, then choose "New" from the Actions Menu. Then, when you create a new product, yu'll have to open the full company dialog in order to see your company. In the dropdown on the left, only companies are shown that have products of the current product type. Hope that helps, kind regards, Martin
  4. Hallo bene-solar, ja, in der Tat, da ist uns ein Fehler unterlaufen. Hersteller, die keine lieferbaren Produkte mehr haben, werden derzeit nicht mehr dargestellt. Wir werden den Fehler im nächsten Release beheben (2020 R9). Dann muss man nur die Option "Auch Produkte, die nicht mehr lieferbar sind" aktivieren, dann bekommt man auch wieder Sanyo angezeigt. Beste Grüße, Martin
  5. Hallo Gerald, für die Berechnung der Abschattungsverluste empfehlen wir in jedem Fall die 3D-Umgebung. Gerade, wenn es um gegenseitige Abschattung geht. Ferne Objekte wie eine Silhouette aus Hügeln, Bergen, weit entfernt stehenden Häusern etc. kann man gut und mit ausreichender Genauigkeit über Horizontlinien abbilden. Aber bei nahen Objekten und Reihenabschattung sollte man unbedingt die Anlage in der 3D-Umgebung simulieren. Beste Grüße, Martin
  6. Dea JoelB, thank you for the projects. Offgrid projects are a bit more difficult to design since there is no grid that could absorb or provide energy when there is too much or too less in the system. In your case, example "Benisheikh Police Radio Station", there is a high consumption with annual values of about 37000 kWh, but the PV system only has 3.5 kWp. In Nigeria you can calculate with approx. 1500 kWh/kWp solar energy per year, so you'll get 3.5 * 1500 = 5250 kWh of PV energy. This is far too less for your consumption, and there isn't another energy source in the system. So the first thing to look at is the energy values of consumption, PV and batteries. Consumption and PV production have to be roughly in the same range, the more PV there is, the better. The battery size in kWh is then chosen dependent on the desired autonomy size. It will be about three times the daily consumption. The second thing to look at are the power values. If your PV system provides 100 kWp, but your battery can only work with 2 kW, you will have a lot of energy unused. The PV power, the battery power and the peak load power should be in the same range. To make things easier when starting with offgrid projects, you can activate the load shedding feature on the consumer's page. If there isn't enough PV or battery power or energy to supply the consumers they will be shut off temporarily. Hope that helps, kind regards, Martin
  7. Hi JoelB, would it be possible for you to send us the project file? That would make it a lot easier for us to identify the problem. You can send it to me via private message here in the forum. Thanks and kind regards, Martin
  8. Hello afbialecki, Im am afraid that these two options are not available in PV*SOL premium right now. But thank you for the suggestions, we will write them on our list of possible future features. What would be a naming scheme for the screenshots that you have in mind? Kind regards, Martin
  9. Hallo PeterZ, man kann die Module, die auf solchen Dachflächen platziert werden, miteinander verschalten, das geht. Aber man kann zwei unterschiedliche Dachflächen nicht wie eine große belegen, also dass Module evtl. auch über dem Stoß platziert werden könnten. Die zwei Gebäude als eins zu konstruieren und das fehlende Dachstück mit einer Sperrfläche von der Belegung auszunehmen, ist eine Möglichkeit, ja. Mit dem von dir genannten Nachteil, dass es in der Präsentation nicht optimal aussieht. Eine weitere Möglichkeit wäre, das Haus z.B. in Sketchup zu modellieren und dann in PV*SOL zu importieren. Photoplan oder die Dachbelegung wären zwei weitere Optionen, die dann aber nicht mehr auf der 3D-Planung beruhen, sondern im Hauptprogramm zu finden sind. Beste Grüße, Martin
  10. Hi ChaseSecrist, thank you for your question and the explanations. The setup you are inteding to reproduce will not be easy to accomplish in PV*SOL. The reason is that the amount of PV energy that can be used by the consumers is simulated (in contrast to be defined by the user). It depends on the load profile, the wattage at any point in time, and the amount of available PV power at that time. For example, if the PV power at 11am exceeds the power consumtion at that time, the exceeding PV power will be fed into the grid. On the other hand, if there is not enough PV power to supply the appliances, the remainder will be drawn from the grid. I do understand the need for your comparison, however. But I wonder how the problem of synchrony between PV production and consumption is regulated in the PPA? What if you as a electricity seller provide the energy, but the buyer can't use it entirely due to his load profile? Kind regards, Martin
  11. Hi Reint, perhaps there are some Autarco inverters selected that are no logner available? Just check the checkbox in order to see if there is somethng hiding. Kind regards, Martin
  12. Hi Reint, this is strange. Is it possible to provide a screenshot or a short screencast of the problem? If you don't want to share it publiclyyou can send me a private message here in the forum. Kind regards, Martin
  13. Hi iwanycka, thank you for your project file. As it is a rather large project (6000+ modules on 17 inverters with 9 MPP trackers each), I guess that the computer runs into memory problems. Try to close PV*SOL premium, and then open this file: C:\Users\USERNAME\Documents\Valentin EnergieSoftware\PVSOL premium 2020\PVSOL.ini Find the line that starts with <Results SaveHourlySimulationResults="False" SaveOneMinuteSimulationResults="False" SaveIVCurves="False" CalculateYieldLossDueToShading="True" MaxNumberOfInvertersForResults="20" ... normally around the middle of the file. Then change the attribute MaxNumberOfInvertersForResults="20" to MaxNumberOfInvertersForResults="10" Then start PV*SOL again and run the simulation of your project. The changed setting will tell PV*SOL not to record each individual result of each inverter for the energy balance, and that saves a lot of memory. Since you are not the only customer experiencing these kinds of problems, we will address this issue in the upcoming release (2020 R9) where we will introduce another attribute called "MaxNumberOfMppsForResults". There are a number of inverters with a lot of MPP trackers now, so we will have to track the total number of those as well in order to avoid memory problems. Kind regards, Martin
  14. Hi ChaseSecrist, when analyzin PV systems with PPAs, you should chose the "Grid-connected system" first: Then on the page "Financial Analysis" you'll want to delete the feed-in tariffs. You can enter the price of electricity that is sold to third parties in the corresponding field. The other financial parameters (assessment period, investment cost, loans etc.) can be entered in a dialog that opens when you click on the "Edit" button. Hope that helps, kind regards, Martin
  15. Hi Iwanycka, would it be possible to send us the project file (with the Sungrow 100CX), so that we can have a look into it? You can send it here vie private message. Thank you, kind regards, Martin
  16. Dear Miguel, thank you for your questions regarding the consumption profiles. All load profiles have a resolution of at least one hour. Most predefined load profiles have a resolution of 15min or 1min. In case of the BDEW profiles it is 15min. You can see the number of values when selecting the profile: Or, when having selected the profile, you'll see the resolution in the status on the right: The actual profile can be analysed after the simulation, at Results -> Simulation -> Diagram Editor. There you have either the option to select the consumption time series or the carpet plot: These diagrams will also be available directly on the consumption page in our new major release PV*SOL premium 2021 R1 (planned for November 2020), so that they are more accessible. This feature will also be added in the next major release PV*SOL premium 2021 R1 (planned for November 2020). It was available in past releases, however, so if you wish, you can refer to this thread to see your options: Hope that helps, kind regards, Martin
  17. Hello Lee, the message that there is no internet connection available is not related to paying for an update or so. Updates are always included if you have a valid software maintenance contract. When you purchase you get 6 months of updates for free. See more here: https://valentin-software.com/en/products/software-maintenance/ You can contact our sales team with your customer number so they can explain the details. Which version have you been purchasing? Try to download the newest version and do a fresh install, this might help: https://valentin-software.com/en/downloads/ Kind regards, Martin
  18. Dear Vishnu, yes, there have been some changes in the simulation core. If you can tell me the program version of PV*SOL that was used to run the simulations in the first place, I can identify the changes that are responsible for the change of the simulation results. You can also have a look at the changelogs here: https://valentin-software.com/en/products/pvsol-premium/ Kind regards, Martin
  19. very nice work, Jordn! This looks really amazing.
  20. Dear Ashraf, we were able to identify the problem. A solution will be published in the next release, PV*SOL premium 2020 R9. The solution will fix the issue that the automatic configuration is not able to find a valid configuration for the Sungrow SG110CX. Kind regards, Martin
  21. Hi Ricardo, thank you for notifying us of the missing inverter. I will forward this request to our database team, so that they can take care of it. You can also write to them directly for future requests at database@valentin-software.com. Kind regards, Martin
  22. Here's the link: https://downloads.valentin.de/pvsol/setup_pvsolpremium_2019_14.exe Kind regards, Martin
  23. Hi Mads, thank you for your question. Unfortunately we have not yet implemented this feature that we had in the past in the new consumption dialog. We will implement it as soon as possible. Right now the only solution for you would be to define such a load profile in PV*SOL (premium) 2019 and then import it in PV*SOL (premium) 2020. Kind regards, Martin
  24. Dear Ashraf Elawad, thank you for reporting this problem. We are currently analyzing the issue, and we will get back to you as soon as we have an answer. Kind regards, Martin
  25. Hi Ricardo, thank you for the file. I just opened it in PV*SOL premium 2020 R8 and it simulates fine, without crash. Perhaps you can check if you have these options set to "no", this saves some memory in some cases: Kind regards, Martin
×
×
  • Create New...