Jump to content

developer_mh

Administrators
  • Posts

    1,822
  • Joined

  • Last visited

  • Days Won

    169

Everything posted by developer_mh

  1. Hi Vishnu, in this case it would be best to contact our technical support team at hotline@valentin-software.com, they can help you out properly. It would be helpful if you could also attach the corresping project file. Kind regards, Martin
  2. Hi stubzy, please have a look at these resources that will help you to understand the shading calculation in PV*SOL more in detail: https://help.valentin-software.com/pvsol/2019/calculation/irradiation/horizontal-shading/ https://help.valentin-software.com/pvsol/2019/calculation/pv-modules/shading-due-to-nearby-objects/ And then some threads from the forum where we discuss the various shading results: Hope that helps. If you have any further question, please don't hesitate to ask. Kind regards, Martin
  3. developer_mh

    T>J

    Hi stelpanel, from what I understand from that brochure here https://english.rvo.nl/sites/default/files/2019/04/Brochure SDE Spring 2019.pdf is that you receive a feed-in tariff for your produced energy that is dependent on the "correction amount", i.e. the current market price of energy. In total, if I understand it right, you will always get 9, 11 or 13 ct/kWh as a result, partially from the subsidy, partially from the market price. In this case, calculating SDE in PV*SOL is easy. Just create a new feed-in tariff with the according remuneration (9, 11 or 13 ct/kWh) and select it on the page "Financial Analysis". Please correct me if I understand the SDE+ system wrong. Kind regards, Martin
  4. developer_mh

    T>J

    Dear stelpanel, I will translate your post using deepl.com: We will have a look into this, but please be aware that it might take a moment until we find the time to respond. Kind regards, Martin
  5. Hi Marta, we are sorry that you are experiencing this error. We are looking into the issue. There is no need to open more than one thread here in the forum. And you don't need use the report function, this is intended to report inappropriate content to the moderators. Thank you for filing the bug report. As it is a larger project, it might take a while to debug. Thank you for your understanding, kind regards, Martin
  6. Hi Kamal, these kind of bends occur when you have unequal number of modules in your strings. The curve section from 0V to the point where the bend occurs is where the two strings both deliver a current for the given voltage. After the bend, up to the open circuit voltage of the longer string, only the longer string (with 21 modules) can deliver current, the other string is not contributing anymore. Kind regards, Martin
  7. Hallo ojsolar, die Gebäudedarstellungen werden automatisch generiert. Wenn man mit der Ansicht nicht zufrieden ist (bei großen Gebäuden ist das manchmal der Fall), kann man auch eigene Screenshots mit dem Screenshot-Manager der 3D-Umgebung machen und diese als Übersichtsbild festlegen: Dann wird das gewählte Bild auch im Projektbericht verwendet. Beste Grüße, Martin
  8. Hi Karam, no, I would not say that connecting strings with different module numbers is a red line in general. Why not try it out in PV*SOL directly? We calculate the losses due to string mismatch with great accuracy, so you can just see how much energy you loose in you PV system and see for yourself if you can accept these losses. You can also see the resulting IV characteristics of your parallel strings in the results page (under Simulation -> Diagram Editor -> Type of Diaram: Characteristics) Kind regards, Martin
  9. Hi Fritz, the Module-independent shading is reducing the global radiation on the module, sure, but it is not part of the PR calculation. It just leads to a reduction of the radiation, like it would if you take climate data for another location with less solar radiation, for instance. In contrast, the losses due to the reflection on the module surface are both reducing the global radiation that is available for electrical conversion _and_ it is accounted for in the PR calculation. Yes. Or more precisely, yes, given that the modules are connected to the same MPP tracker and are part of the same module area. The lowest diffuse shading value of the modules connected to one MPP tracker is taken as module-independent shading factor. No, the shadow calculations work for all kinds of shading objects in the same manner. Concerning the UA, you are referring to this help page, I guess: https://help.valentin-software.com/pvsol/2019/calculation/pv-modules/module-temperature/ The heat loss rate is part of the PV module temperature calculation and is therefore also part of the PR calculation. To put it the other way round: All the losses you see in the energy balance, between (Global Radiation at the Module + Reflection on the Module Interface), and the PV energy (AC) minus standby use, is integrated in the PR calculation. Hope that helps, kind regards, Martin
  10. Hi Vishnu, the feed-in management or maximum power clipping or "Einspeisemanagement" in German can be edited on the page "System Type, Climate and Grid". https://help.valentin-software.com/pvsol/2019/pages/system-type-climate-and-grid/#ac-grid https://help.valentin-software.com/pvsol/2019/navigationsseiten/anlagenartklimaundnetz/#ac-netz There you can enter the power clipping in % of the installed DC power, and you can choose if the inverters are limiting the power or if it can be done at the feed-in point. In case of the latter, possbile self consumption or battery charging can take place before limiting the PV production. The results (the actual losses due to clipping are shown on the results page. DEpending on what type of clipping you choose, the values are presented differently. If you don't have electrical appliances (consumers) in your system, the losses can be found in the energy balance of the PV system: If you have electrical appliances and you choose power clipping at the feed-in point, the losses can be found on the overview pages: In the diagrams: In the table views: And of course in the energy flow graph: And a side note: If you analyse clipping behaviour and you want to know the energy losses, we strongly recommend using one-minute resolution for the simulation. Hope that helps, kind regards, Martin
  11. Hi ZhAta, it is true that formally the MPP voltage is too low and the current is too high if you connect 6 x 22 JA Solar JAP6(K)-60-270/4BB modules to a Fronius Eco 27.0-3-S. With the check temperatues of 15°C (U_Mpp_Max), 70°C (U_MPP_Min) and -10°C (U_OC) there is no way around it. You could have 5 x 24 modules, then the current limit isn't hit and the MPP voltage limits are fine, but still the Open Circuit voltage will be exceeded. But the question is, how much energy do you loose if you connect your system like this? I simulated your system with one-minute resolution (to get a realistic estimation of the clipping losses) and it looks ok: The down-regulation on account of the MPP voltage is relatively high, 1287 kWh, but it is still only -0,76% of you energy that you loose. It is then up to you, the planner, to decide if you want to accept these losses. If you are bound to these specific modules and this inverter, I guess you have to You can try different configurations, simulate them and see what you prefer. Hope that helps, kind regards, Martin
  12. Hallo Richard, aus dem Fehlerbericht ist herauszulesen, dass es zu Problemen beim Laden von den Tarifen kommt. Die Version, die ihr benutzt ist leider ziemlich alt, so dass wir diesen Fehler höchstwahrscheinlich in der Zwischenzeit schon behoben haben. Daher lohnt es sich immer, mit der aktuellsten Version zu arbeiten. Es sind auch viele, viele neue Features darin und ihr könnt sie 30 Tage kostenlos testen: https://www.valentin-software.com/produkte/photovoltaik/57/pvsol-premium Beste Grüße, Martin
  13. Hi Ricardo, I mean you could still use the configuration as in your version 2. The maximum current is only exceeded by 0.54 A, I guess that the energy losses due to current clipping will not be too high. I just simulated it with one-minute values for Berlin, and the current clipping (down-regulation) is really insignificant. Kind regards, Martin
  14. ah, you were faster. So the database entry is wrong. I will inform our database team.
  15. Hi Ricardo, how it would be done in the real world is a very good question. I guess you should ask the Huawei people I quickly scanned the user and installation manual for the SUN2000-20 KTL but I did not find any settings that would tell the inverter how to handle the MPP trackers and DC inputs. The ability to operate the MPP trackers together is something that the manufacturers enter into our database. So perhaps it would be best to ask the technical support of Huawei. support@huawei.com Kind regards, Martin
  16. Hi Fritz, the performance ratio is calculated as the ratio of the total energy yield to the theoretically possible energy yield. That is, we take the energy output in kWh, E_total, and divide it by G * A * eta, where G is the irradiation on the module surface, A is the surface area of the plant and eta is the STC efficiency of the modules. So, to answer your question, what exactly is G, the irradiation on the module surface? I will copy an energy balance here in order to illustrate the different shading and reflection items: We calculate the reflection onto the module surface as the "Global Radiation at the Module" minus the "Reflection on the Module Interface", since this is influenced by the module properties. So the PR in this case would be PR = 14194,57 kWh / ((1122,50 +27,61) kWh/m² * 83,83 m² * 0,181) = 0,8134, or 81,3% We have two shading items in the energy balance: Module-independent shading in the meteo block, and module-specific partial shading in the PV field block. The first is not accounted in the calculation of the PR, the second is. The module-independent shading is the diffuse shading that is affecting all modules equally. The diffuse shading is evoked by obstacles (near or far) that are blocking the view to the sky hemisphere and is applied to the diffuse fraction of the solar irradiation only. We calculate the diffuse shading factor for every module and determine the maximal value that applies to all modules. In real world situations this minimal factor will most likely only cover the horizon or shading by far objects. When you have regular rows of modules then the diffuse shading factor for the inner modules will be higher due to the shading by the row in front, but the first row will have a lower value for the diffuse shading, so this value will be selected for all modules. All the rest of the diffuse shading and the direct shading is considered in the module-specific partial shading. Does this answer your question? You can also take a look here, there are some more details about irradiation and shading and so on: https://help.valentin-software.com/pvsol/2019/calculation/ Kind regards, Martin
  17. Hi Jan, that is right, the modules need to have a distance from the ground in order to receive irradiation onto the rear side. Try to use mounted systems in 3D, either on the ground or on roofs, then there will be bifacial gains. Kind regards, Martin
  18. Hi simonsolar. right now it is not possible to enter non linear temperature coefficients or IAM. We are aware of the fact that there is a need for this and we have it on our list, but right now we can't name a possible release date for these features. Kind regards, Martin
  19. Hi James, glad that you like it. And thank you for your kind words Kind regards, Martin
  20. Hi Jtebuck, there are various kinds of clipping mechanisms in PV*SOL. 1) There are inverter clippings due to voltage, current or power limitations that take place directly in the inverter. You can see these effects in the results in the energy balance: 2) Then there are maximum power clippings that you can edit on the page "System Type, Climate and Grid" in the AC mains section: I guess this option would be the best to suite your needs. The clipping threshold is set in % of the PV power installed on the DC side, so you would have to calculate the corresponding percentage beforehand. Let me know if this is what you need. Kind regards, Martin
  21. Hi Raphael, yes, it is sufficient to install just the latest version. All installers of PV*SOL comprise the whole functionality. Kind regards, Martin
  22. Hi Marta, yes, this message is shown when the total upload size exceeds 10 MB (which was the limit for all users). I raised it to 20 MB now so you can retry and upload the other screenshots. Kind regards and have a nice weekend, Martin
  23. Hallo, die einzige Möglichkeit, die ich da sehe, wäre genügend Module in die Strings zu packen, also mindestens 13, die ausreichend bestrahlt werden. In diesem Fall würde das aber nicht gehen. Eine andere Lösung wäre, einen anderen Wechselrichter mit einer niedrigeren MPP-Spannung zu verwenden. Der SE6000H z.B. arbeitet auf 380V, das wäre in diesem Fall schon sehr viel passender: Beste Grüße, Martin
  24. Hi Marta, I am not sure if I can reconstruct your problem correctly. Could you describe step by step what you do (click) after opening PV*SOL? This would be helpful. Ideally you could provide a screenshot of each step. Which version do you use? Do you use climate data that you generated yourself? Kind regards, Martin
  25. Hi Gustavo, you would need to fill up the data series for 365 days. If you have a 15 min resolution, you need 35040 values for one year. Since you have only 337 days of measurement, PV*SOL 'complains' that the number of records is wrong. The solution is to provide a full year of data, then it works. Kind regards, Martin
×
×
  • Create New...