developer_mh

Hallo Ralf, Krüppelwalm-Dächer werden bei uns immer in zwei Segmente unterteilt, da die entstehenden Dachflächen nicht zwangsweise den gleichen Neigungswinkel haben. Hier z.B.: Man kann aber natürlich trotzdem beide Teil-Dachflächen belegen und dann gemeinsam elektrisch verschalten, indem man im Reiter "Modulverschaltung" auf "Alle unverschalteten Modulflächen verschalten" klickt. Dann mit gehaltener Strg-Taste beide Modulflächen selektieren, auf "Modulflächen gemeinsam verschalten" und dann wie gewohnt verschalten: Ich hoffe, das hilft weiter. Beste Grüße, Martin

Hi Sebastian, sorry for the late answer, I think we overlooked it and forgot to reply. The data that is displayed in the carpet plots is identical to the data in the time series. So you just have to select the according time series, eg. "Irradiance onto horizontal plane", choose the full year as time period and then right click and export it to Excel. Hope that helps, kind regards, Martin

Hi Alisson, it seems that the picture that you attached is not there. Could you try and upload it again? Kind regards, Martin

Hi Jack, thank you for reporting this strange behaviour. Could you send us a project file so that we can reproduce the issue. You can also send it by private message here in the forum, so that it doesn't become public. Kind regards, Martin

Dear Bulent, thank you for your question. In PV*SOL, we use climate data from the well-known climate data specialist Meteonorm, see here: https://help.valentin-software.com/pvsol/2019/calculation/irradiation/climate-data/ PVsyst also uses Meteonorm, so in terms of irradiation data there shouldn't be any difference between PV*SOL and PVsyst. Do you have an example project where we can see PVsyst and PV*SOL energy yields side by side? Often the differences in the energy yield come from the models that are used to calculate the irradiance on the tilted plane of the PV modules. These models can be modified in the program options under Options -> Program Options -> Project Options -> Simulation: Regarding values from SolarGIS: Yes, it is not unusual that climate data values can vary within +- 15 % between the sources. SolarGIS uses mainly satellite data, if I remember correctly. Meteonorm uses mainly ground measurement stations in combination with satellite data. And then there is PVGIS which also uses satellite data and whose values differ both from SolarGIS and from Meteonorm. See some details about the meteorological approaches here: SolarGIS: https://solargis.com/docs/methodology/solar-radiation-modeling Meteonorm: https://meteonorm.com/assets/downloads/mn73_theory.pdf PVGIS: https://re.jrc.ec.europa.eu/pvg_static/pvgis5.pdf As you will soon realize, there is no true or false for climate data. Nor is there any "higher values are better". It depends on what you want to achieve. If you want to achieve a higher simulated energy yield than your competitor, yes, you might be willing to choose the data source with the highest irradiation for a given place. But what happens if this simulated energy yield is too high? Won't the customer be dissappointed? We think that on the long run, it will shed a negative light on the project planners and users of our software (and the whole industry), which is why we always try to provide simulations that are conservative, but still realistic. The climate data of Meteonorm do fit nicely in this "conservative" concept, where the yield that we simulate is nearly always topped in reality. But of course, you are free to import any other climate data into our software and simulate with that. A guide how to import climate data from other sources can be found here: https://help.valentin-software.com/pvsol/2019/pages/system-type-climate-and-grid/meteosyn/#options Hope that helps, kind regards, Martin

Here is the excel sheet, you can just paste your monthly values into the green fields and copy the blue fields to the clipboard PVSOL Modify Monthly Consumption Percentage Before Import.xlsx

Hi Tim, you are right, the import of the 12 monthly values in the dialog you posted in your first post are not accurate. This is a bug we know of quite some time, but this section of our software is/was a remainder from older times This is one of the reasons why we refurbished these old components now. In the next major release (which is planned for early 2020), an update of the consumption dialogs is included. In the meantime, if you work with net metering you can enter the monthly consumption values directly here: Or, if you are willing to modify the monthly consumption before importing them, you can do the following: Import the monthly energy values in kWh and calculate the monthly percentage (first two columns) Calculate the monthly modification factor with (days of month) / (365/12) Calculate the converted percentage with (real percentage) / (modification factor) then you can select the last column, copy it to the clipboard and paste it into the dialog that you showed Then click ok and enter the yearly energy consumption here Then you'll get the monthly energy consumption into PV*SOL as desired: Hope that helps, and sorry for the circumstances. Kind regards, Martin

Hi Glenn, in addition to my colleague's comment I'd like to add that in our current PV planning software PV*SOL premium 2019 you'll find all the features that were available in the SMA Offgrid Configurator as well, and lots more. See here for a features overview: https://pvsol.software/en/features-pricing or https://www.valentin-software.com/en/products/photovoltaics/57/pvsol-premium You can also test these applications for free for 30 days. Kind regards, Martin

Hallo Ralf, ja, diese Erweiterung steht bei uns auf dem Zettel. Terminlich können wir dazu zwar noch nichts sagen, aber wir arbeiten dran. Beste Grüße, Martin

Hallo OD111, eine Möglichkeit wäre, eine Art Projekt-Vorlage zu machen und diese bei jedem neuen Projekt zu laden. Dazu einfach das gewünschte Lastprofil auswählen und das Projekt unter einem aussagekräftigen Namen speichern, z.B. "Projektvorlage - Verbrauchsprofil Einfamilenhaus Mitteleuropa.pvprj". Das kannst du in Zukunft dann zu Beginn eines neuen Projektes laden, dann direkt unter einem neuen Namen speichern ("Speichern unter" -> aktueller Projektname) und dann weiterarbeiten. Beste Grüße, Martin

Hallo Tobi, Welche Module sind denn nicht korrekt in der Datenbank? Bei uns geben ja die Hersteller die Daten ein insofern können wir leider nicht jederzeit garantieren, dass alle Daten korrekt sind. Aber wenn wir wissen, um welche Module es sich handelt, können wir das den Herstellern so weitergeben. Ansonsten hast du das richtig gemacht. Das Modul kopieren, einen Leistungsoptimierer auswählen und die restlichen Eingaben so stehen lassen. Die Warnung bezüglich der Mismatching-Verluste kann man wahrnehmen und dann je nach Anwendungsfall ernst nehmen oder ignorieren Es entstehen durch unterschiedliche Stanglängen auf jeden Fall Mismatching-Verluste, dessen sollte man sich bewusst sein. Es empfiehlt sich auch, diese nach der Simulation in der Energiebilanz zu überprüfen. Aber wenn man sich dessen bewusst ist, und diese Verluste in Kauf nimmt, kann man die Warnung ignorieren, ja. Tutorials würden wir sehr gerne mehr machen, momentan fehtl uns leider ein wenig die Zeit dazu. Aber wir nehmen deine Anregung auf, danke dafür. Beste Grüße, Martin

Hi Niclas, yes, I think it has nothing to do with the PV*SOL version. Have you imported this exact file before and it worked? Or was it another file? Did you change anything else in your system? Kind regards, Martin

Hi Niclas, can you check if there is another process accessing these directories? E.g. do you have an antivir software where you could add an exception for that folder, just to test? Kind regards, Martin

Hallo J.Ackfeld, leider haben wir momentan keine "saubere" Lösung, um BHKW in PV*SOL zu simulieren. Eine unsaubere, aber ggfs. gangbare Lösung wäre, den Verbrauch um eine Grundlast von 10 kW zu reduzieren, wenn das das derzeitige Lastprofil überhaupt hergibt. Das ginge nur, wenn beim derzeitigen Lastprofil die Leistung von 10 kW nie unterschritten wird. Diese Reduktion der Last wäre dann sozusagen der Beitrag, den sonst das BHKW leistet, sodass sich die PV nur um den Anteil kümmern muss, der die 10 kW übersteigt. Konkret würde man das so machen, dass man das Lastprofil exportiert (nach der SImulation auf der Seite "Präsentation" in den csv-Export) Dann in Excel diese Datei öffnen und die stündlichen Verbrauchswerte herauskopieren (Jahreswerte und Monatswerte werden nich gebraucht), am besten in eine andere Excel-Datei. Dort kann dann die gewünschte Modifikation vorgenommen werden. Hier habe ich z.B. ein 1kW abgezogen und dann das Profil in Wh umgerechnet (*1000). Dieses neue Profil dann speichern (ohne die erste Spalte und ohne Kopfzeile), und dieses dann wieder in PV*SOL importieren, auf der Seite Verbrauch -> Neuer Verbraucher -> Lastprofil laden und importieren Ich hoffe, das hilft erstmal weiter. Ist leider eine etwas unkonfortable Lösung, die auch nicht in allen Fällen passt. Beste Grüße, Martin

Hi Niclas, since we haven't changed anything in the 3D model importer or the 3D environment, I believe that it is a coincidence that this error occurred only today. The error message says that some other process is accessing the files. Perhaps you can try to close all PV*SOL instances and then delete all folders inside C:\Users\{YOUR-USERNAME}\AppData\Local\Valentin EnergieSoftware\Temp\PVSOL premium 2019 Did you change anything else on your computer other than the PV*SOL update? Kind regards, Martin

Hi Tim, SolarEdge updated their configuration rules that describe which inverter can be connected to which power optimizers in which country etc. Our inverter configuration is now compliant with these updated rules and users will get hints accordingly. Hope that helps, kind regards, Martin

Hi Carlos, in order to debug this, it would be helpful if you could provide some more information. Which version of PV*SOL 2019 are you using? Can you send the log file "PVSOLpremium.log" ? It is located under C:\ProgramData\Valentin EnergieSoftware\log Also, please send a dxdiag file (hit Windows key, then type "dxdiag", hit enter and then choose "Save All Information"). You can also send these files in a private message. Thanks and kind regards, Martin

Hi Tim, the year that we simulate isn't a specific one. It is a general year, just the 8760 hours of one typical year at a given location. The climate data is taken from real years with a range of 10 to 20 or even 30 years and is compiled into a single typical meteorological year (TMY), that contains e.g. the January of 2006, the February of 2013, March 2014, and so on. See more on that topic here: https://help.valentin-software.com/pvsol/2019/calculation/irradiation/climate-data/#what-are-climate-data-sets-what-does-typical-mean-year-mean So, this single TMY is "yearless", so to speak. It stands for a typical year in the time range that is denoted in the climate data. Hope that clarifies the matter, kind regards, Martin

Dear Tim, yes, that is true. This is because we only simulate one year, and the calendar component that you showed in your screenshot needs a year to be set. 2014 is just an arbitrary value, a placeholder for any year, if you want. Sorry for the confusion, kind regards, Martin

Hi Juan, sorry for the late answer. Somehow I overaw this question.. right now it is not possible to simulate an offgrid system with DC coupled batteries, I am afraid. The offgrid logic that we implemented is based on the SMA products, so there is no DC option, sorry. Kind regards, Martin

Hi b_yilmaz, yes, you can achieve this by using the polystring feature. You can combine any thinkable configuration of modules together. https://help.valentin-software.com/pvsol/2019/pages/inverters/polystring-connection/ Hope that helps, kind regards, Martin

Hi Alex, yes, it is true, this option is missing right now. We will consider it for future versions. Right now you can export the project report as Word file and then add the desired graph manually. You can save all diagrams in PV*SOL by right clicking on them. Hope that helps for the moment, thanks for your feedback. Martin

Hi Alexclavijon, in order to debug this, it would be helpful if you could provide some more information. Which version of PV*SOL are you using? Can you send the log file "PVSOLpremium.log" ? It is located under C:\ProgramData\Valentin EnergieSoftware\log Thanks and kind regards, Martin

Hi RobS, here you can find more information on how to set P90 parameters: https://help.valentin-software.com/pvsol/2019/pages/financial-analysis/bankability-p50p90/ Please note that this option is only available for full feed-in PV systems. That is, if you have electrical appliances in your system, you won't see the P90 option. Kind regards, Martin

Hallo FXR, diese Einstellung kann beim AC-Netz vorgenommen werden: https://help.valentin-software.com/pvsol/2019/navigationsseiten/anlagenartklimaundnetz/#ac-netz Beste Grüße, Martin