developer_mh

Hallo Klauss, hallo masp, Üblicherweise kommt diese Meldung, wenn PV*SOL Projekte, die in einer neueren Version gespeichert wurden, in einer ältern Version von PV*SOL wieder geladen werden sollen. Beste Grüße, Martin

Hi Carlos, hi Jimmy, exactly, the EnEV results are relevant for Germany only. They should only appear for PV systems with location in Germany. Kind regards, Martin

Hi again, this bug will be fixed in the upcoming release PV*SOL premium 2022 R5. Thanks again for reporting! Martin

Hi Venco Gary, in your feed-in tariff, you have the share of remunerated energy set to 0%. You should set it to 100% if all of the energy that is fed into the grid is remunerated. Then you'll get non-NaN values: Your project has a lot module areas (nice project by the way!). In order to save memory, we restrict the results per module area on projects with less than 20. You can change that setting, on your own risk. Close PV*SOL, then open the PVSOL.ini file in a text editor. You can find it here: C:\Users\USERNAME\Documents\Valentin EnergieSoftware\PVSOL premium 2022\PVSOL.ini Locate the attribute MaxNumberOfModuleAreasForResults and change the value to more than 31, as your project as 31 module areas. Save the file and start PV*SOL again. Then force a new simulation under Options -> Force simulation. Then the module area results should show up. Hope that helps, kind regards, Martin

Hi, thanks for reprting this. We will be looking into it. Kind regards, Martin

Hi Jakub, there is no such app that I know of. But I have to admit that I haven't done any research on that topic recently. There is a device that we recommend to catch horizon lines on site: https://www.solmetric.com/buy210.html You can see roughly how it works on our help pages, in section "Recording horizon lines": https://help.valentin-software.com/pvsol/en/pages/pv-modules/shading/#horizon-line Hope that helps, Martin

Hallo Lukas, beim Zeichnen von Polygonen kann man die genauen Koordinaten der Punkte angeben, indem man einen Rechtsklick darauf macht und dann "Bearbeiten" wählt. Vielleicht hilft das weiter. Das mit den 4m Verschiebungstiefe versuche ich mal in Erfahrung zu bringen. Beste Grüße, Martin

Hi Codrin, in addition to what Jimmy wrote, you can set the maximum allowed exceedance of the input current in the configuration limits dialog: Hope that helps, kind regards, Martin

Hello Luai, in order to explain the direct use, grid feed-in and so on, let me copy a energy flow diagram from PV*SOL here: Direct own use is the fraction of the PV energy that is used directly to cover the loads, in this case 2830 kWh. The own power consumption ratio would be 2830 kWh / 9160 kWh = 30,9 %. The solar fraction is the amount of the consumption that can be covered directly by the PV. So in this example it would be 2830 kWh / 8401 kWh = 33.7 %. Concerning your second question, it would be very helpful if you could send me over the project file (here in the forum as private message). Kind regards, Martin

Hi Jimmy, we are sorry that you are experiencing this flaw with the outdated maps more often now. It seems that Google is updating its map material region-wise, and most probably you are planning a lot in a region where Google is currently updating. We do not have a release date for R5 yet, I am afraid. It will be released in the coming weeks, but when exactly is not yet decided. Kind regards, Martin

Hi M4KROS, the specific annual yield is the annual yield of the PV system (in kWh, AC) divided by the installed DC power in kWp. This means that literally everything from the solar irradiation and ambient temperature, over module inclination, orientation, shading, soiling, electrical configuration, inverter performance, cable losses and so on is taken into account. If you need to know in detail how a PV plant performs, a good start is always to check the energy balance in the results section: Then, also, if you need to investigate some losses more in detail, you can go to the diagram editor, choose time series or carpet plots to analyse single data series. You can also export them to Excel or LibreOffice Calc if you wish. Hope that helps, kind regards, Martin

Hi Paul, you'll have to activate the polystring option in the configuration dialog. Then you can combine the strings and modules as you wish, in series or parallel. Hope that helps, kind regards, Martin

Hallo AoS, doch, eigentlich geht das schon. Könntest du mir das Projekt zukommen lassen, dann kann ich mal schauen. Gerne hier im Forum als private Nachricht. Beste Grüße, Martin

Hallo Lukas, am besten arbeitest du in diesen Fällen nicht mit Stockwerken, sondern extrudierten Objekten. Diese kann man beliebig aufeinander setzen, und auch mit Attikas versehen: Die äußere Attika-Fläche kann jedoch leider nicht mit belegt werden. Beste Grüße, Martin

Hi Rob, this is not possible right now in PV*SOL, but we already have this feature request on our list. What I would recommend right now is to model the cable for each inverter as if it was part of the long distance cable. As an approximation this is possble if your inverters roughly have the same power. As the loss power is calculated with P = I_big² · R_big, and R_big = ρ · l / A_big. So through your big cable with cross section A_big you have the current I_big, which is the sum of the currents of your individual inverters. If we suppose that all inverter currents are the same at any time (which they aren't, but we have to assume it as an approximation), we can say that I_big = n · I_inv, with n being the number of inverters. So the cross section of each individual inverter cable would have to be divided by n in order to obtain approximately the same result. Example: You have one big cable of 300m length with 300mm² cable with 4 inverters connected to it. This is roughly the same, in terms of power loss, as 4 individual cables with 75 mm² (300 / 4). If each inverter would have an output current of 10A, the power loss in the big cable would be (4 · 10 A)² · R_big = 1600 A² · 0.028 Ωmm²/m · 300 m / 300 mm² = 44.8 W If each inverter has its own cable, then it is (10A)² · 0.028 Ωmm²/m · 300 m / 75 mm² = 11.2 W, but you have that four times, so its 4 · 11.2 W = 44.8 W Hope that helps, kind regards, Martin

Hi TurtlesOG, try to deselect "Corrigir distorção" in the extrude dialog and see if the texture is correct now. Kind regards, Martin

Guten Morgen Tom_ebr, das geht relativ einfach und ist hier beschrieben, Abschnitt "Lastprofile importieren" https://help.valentin-software.com/pvsol/2022/de/navigationsseiten/verbrauch/#gemessene-verbraucher Viele Grüße, Martin

Hi Tiago Motta, we are currently investigating this issue. The attica shading problem and the problem with obj models are possibly unrelated, though. It would be very helpful if you could provide the original obj files, along with the information which photogrammetry software you used to create it. Also the PV*SOL project that you took the screenshots of would be very helpful. Could you please send these files to our technical support team at hotline@valentin-software.com? Just add a short hint in your email that they should forward it to me. Thanks a lot and kind regards, Martin

Hi TurtlesOG, hi Jimmy, it is possible to combine module areas of the same orientation and inclination already in the "Define Module Areas" dialog: Hope that helps, kind regards, Martin

Hi GdE, here is a translation of you question, made with deepl.com: You can use the net metering option in PV*SOL. On the economy page, switch to net metering. There you can enter the tariff zones and prices. Then, in the consumption page, you can enter the monthly consumption values. See also this forum thread for example: Hope that helps, kind regards, Martin

Hi Silvester, coudl you provide more details about the error? Can you make a screenshot? Also, the logfiles would be interesting. You can find them here: C:\ProgramData\Valentin EnergieSoftware\log C:\ProgramData\Valentin EnergieSoftware\log You can send them to me with a private message here in the forum. Thanks and kind regards, Martin

Dear Flavio, does this happen every time that you try to select a PV module in 3D? Could you click on "send bug report", please and let us know the time and date? That'd be helpful, thanks. Also, could you provide your log files, please? You can find them here: C:\ProgramData\Valentin EnergieSoftware\log The files with PVSOLpremium in their name would be helpful. You can send them to me here in the forum as private message. Kind regards, Martin

Hi Marius, the optimizers are only shown in the circuit diagram, I am afraid. Kind regards, Martin

Hallo N_G, die Rückseitenstrahlung wird tatsächlich simuliert, mit dem View-Factor-Modell. Mehr dazu hier: https://help.valentin-software.com/pvsol/2022/de/berechnungsgrundlagen/pv-module/bifaziale-module/ Beste Grüße, Martin

Hallo N_G, nein, das geht auch in der Test-Version. https://help.valentin-software.com/pvsol/2022/de/navigationsseiten/anlagenart-klima-und-netz/meteosyn/#optionen Beste Grüße, Martin