developer_bh

Hey Njigba, Unfortunately I cannot give you any specific feedback on this wish other than that this topic is not on our schedule at the moment. This does neither mean that it will never be realized, nor the opposite. Some users figured out how to use PVSOL via wine on mac/linux. While there is no official support, this might be interesting for you. I cannot guarantee that this works of course. You could also try emulating windows on your mac with parallels f.e.. Best regards, Ben

Hallo Steven, in der neuen 3D Umgebung an der wir momentan mit Hochdruck arbeiten wird es die Möglichkeit geben Sperrflächen für jeden Plan anzuzeigen oder optional auszublenden. Viele Grüße, Ben

Please see my answer in your other thread

Hello! The (altitude) data is retrieved from external sources. In the program there is no official way to edit the altitude at the moment. However, I will provide you with a script that allows you to change the altitude of a given weatherfile (.wbv). Please follow these steps Download the ps1 script (powershell script, windows) from the attachment of this answer Copy the WBV (f.e. "Berlin.wbv") you want to change in the folder of the script (f.e. Desktop/WbvBackups) twice ("Berlin.wbv" - file to change the altitude, "Berlin_backup.wbv" file as a backup of the old state) Delete the WBV in MeteoSyn via Listview context menu (Headsup - this will delete the file, so make sure you have the backup from step 2) Open a shell in the folder (f.e. Desktop/WbvBackups). You can do this in the explorer by navigating to the destination folder and typing "cmd" in the path, then press Enter. Activate the script by the following command : powershell -File "PATH_TO_THE_SCRIPT" -filePath "PATH_TO_WBV" -newValue ALT_VALUE powershell says it will open the powershell (you usually need administrator rights for that) the string after -File directs to the script path the string after -filePath directs to the WBV path the number after -newValue is the new altitude Import the changed file in meteoSyn Check if the new altitude is correct. Do a simulation with the new file to make sure it works as intended. If everything succeeds you may delete the backup from step 2. I hope this is a good work around for now!? I will forward the feature request to the team to make this process easier from within the program, but cannot give you a specific date for the implementation. Best, Ben change_wbv_altitude_value.ps1

Hello, you can change the used model to get a better accuracy depending on the situation in the simulation options. You can also adjust other parameters in that dialog. You will find detailed explanations here : https://help.valentin-software.com/pvsol/2019/calculation/irradiation/diffuse-irradiation/ https://help.valentin-software.com/pvsol/2019/calculation/irradiation/irradiation-onto-inclined-plane/ Here is a quick overview of some models. Erbs model: This model uses empirical correlations to derive the diffuse radiation from the total radiation. It is often used for hourly or daily data and is well suited for mid and low latitudes. Liu-Jordan model: A simple and widely used model based on the assumption that the diffuse radiation is evenly distributed from the sky to the solar modules. It takes into account the solar constant and the zenith angle of the sun to separate the components. Hay-Davies model: The Hay-Davies model takes into account both the direct radiation and the diffuse radiation components caused by scattering in the atmosphere. This model differentiates the diffuse radiation into isotropic and anisotropic components, with the latter being preferentially scattered in the direction of the sun. Perez model: The Perez model is an advanced model that divides diffuse radiation into several components, including isotropic sky diffusion, anisotropic scattering by clouds and reflected radiation. It is particularly suitable for accurate simulations under different atmospheric conditions and is often used in complex PV simulation software. The Hofmann model is usually a good choice. You find more details about it f.e. here https://www.mdpi.com/1996-1073/10/2/248 At the moment you can only use models based on GHI data. Best regards, Ben

Hello Luis, We are working on the new 3D environment, which includes functions such as Undo-Redo. Unfortunately, I can't give you a specific release date yet. Best regards, Ben

Hallo Dirk, wir arbeiten hart um unsere Software zu verbessern. Kürzlich gab es eine große Verbesserung mit der Einführung der Google-Solar API. Parallel dazu entwickeln wir, wie Sie wissen, eine neue 3D Umgebung. Zusätzlich gibt es weitere Verbesserungen, so können Sie beispielsweise bald eine neue Klimadatenquelle erwarten. Als Lizenzeigentümer haben Sie vollen Zugang zu allen Verbesserungen. Mir ist aus der Historie bewusst, dass Sie gewisse Punkte schon seit längerer Zeit erwarten. Wir nehmen das ernst und sind bestrebt dies umzusetzen. Ich habe Ihre Wünsche nochmals an das Team weitergeleitet. Aufgrund der Vielzahl an Kundenwünschen und der großen Anzahl bereits gebundener Ressourcen kann ich allerdings keine festen Zusagen machen. Viele Grüße, Ben

Hello Ola, thanks for your input. I've forwarded it to the developer. The option will be included again in the upcoming R8 release. Kind regards, Ben

Hallo Holger, ein interessantes Thema! Projekte wie EO Solar sind nützlich für eine erstmalige grobe Schätzung des Solarpotenzials auf großen Gebieten. Sie bieten weniger Detailgenauigkeit bei der feinen Abstimmung von Variablen. Mir ist nicht bekannt, wie genau EO Solar das Potenzial einer Fläche berechnet. Eine Vermutung: - Auf der Grundlage der Daten zur Sonneneinstrahlung wird vermutlich die jährliche Leistung der PV-Anlage auf dem Dach des Gebäudes geschätzt. Die zugrundeliegenden Einstrahlungsdaten können sich massiv auf den projizierten Ertrag auswirken. - Die Umwandlung von Sonnenenergie in Elektrizität erfolgt zunächst durch die direkte Aufnahme der Sonnenenergie durch die PV-Module. Unter idealen Bedingungen geht man vermutlich davon aus, dass das gesamte verfügbare Dach mit PV-Paneelen bedeckt werden kann, so dass die von den PV-Paneelen erhaltene Sonneneinstrahlung das Produkt aus Sonneneinstrahlung und effektiver Dachfläche ist. Hier stellt sich die Frage, ob diese idealen Annahmen in der Realität jemals erreicht werden können. Neigungswinkel, Ausrichtungen, Aufbauten usw. werden hier ebenfalls nicht berücksichtigt. - Der Umwandlungswirkungsgrad der PV-Module, d. h. der Wirkungsgrad der Umwandlung von Sonnenenergie durch die PV-Panele in Elektrizität, ist von der Art der PV-Paneele abhängig, z. B. monokristallines Silizium und multikristallines Silizium. Hier stellt sich die Frage, welche Module man zugrundelegt. - Zusätzlich ist der Betriebswirkungsgrad relevant, d. h. die Tatsache, dass das PV-System während des Betriebs einen Teil seiner Energie verliert. - Und schließlich werden auch keinerlei Verschattungen berücksichtigt Es gibt also bereits in dieser kurzen Betrachtung viele Faktoren die zu einem recht großen Unterschied zwischen EO Solar Schätzungen und fein granularen Simulationen führen können. Viele Grüße, Ben

Hello Ola, I forwarded it to our 3D team. Thanks for Your contribution! Kind regards, Ben

Hello Boris and Nils, these models look amazing! Regarding your question: We are not removing any features. To implement the new Google Solar API feature, we had to touch a lot of code to make this work for you. Unfortunately, this bugfix didn't make it into the new version, but as my colleague said, it will be included in the next version. We are also looking into the other points you mentioned. Thank you for your feedback and sorry for the temporary inconvenience! Kind regards, Ben

Hello Thura, We accept them as a service for our users who use these files. The OND file can contain all the data PV*SOL needs to add a valid inverter to our database. But as my colleague said, there are no real specifications, the file can have different structures and input data. Some may only contain a fraction of the data we need. That's why there is a check before the import, where you can add the missing data manually. Kind regards, Ben

Hello, as my colleague already pointed out you can export the meteo data in the results. We only use TMY's, so if you look for specific data from single years we cannot do that. PVGIS offers that for free (no DWD data). On the TMY API page Mikio named you have the possibility to download CSV's to easily extract the data you need. If you need single years from DWD you can download them from their website (f.e. opendata.dwd.de), but you will need some special programs to read them (.nc format). Best regards, Ben

Hello Chloe, PVSOL uses different sources for climate data. These are generated externally by different organizations. The most used is Meteonorm - you can expect an update to Meteonorm 9 soon. We will also add another source (NREL) soon. There are no exact cycles for these updates. Best regards, Ben

Hello @Jan K, thanks for reaching out. Both climate datasets you submitted have problems. You can see this in the climate details dialog. For the PVGIS file there are problems with the minute synthesis, most probably due to an offset in the timestamps. I'd recommend to use another file and/or source. Do not use this file in hourly-simulations. The second file you sent has some major problems with the data too, maybe because of the timestamps. I didn't do a deep dive yet, but thats most probably the cause. Offset means in that context that the global-radiation values over the daily course are not correlated with the sun-course, so f.e. if the GHI data starts one hour too early you will have unnatural peaks in the morning and too low data in the evening. PVSOL has an auto-correction for this in the minute simulation, but this fails when the offset is not regular or data is missing. That's what the error message means in the second climate file. In the first climate file the PVSOL auto-correction will kick-in in minutewise simulation, so if you want to keep this climate file, better use it in minute-simulations. Do not use the second until you repaired it, it will give you wrong results. Hope this will help you fix the problem. Best, Ben

Sehr geehrte Frau Schumann, Meteonorm verwendet ein eigens entwickeltes Verfahren bei der verschiedene Parameter einfließen und es z.T. vorkommen kann, dass die herangezogenen Zeiträume der Parameter sich unterscheiden. In Meteonorm 8.2 gibt es diverse Regionen, insbesondere die DACH Region, welche die Globalstrahlungsdaten aus der Periode 2001-2020 heranziehen. Auf ihrer Webseite heisst es im Changelog für die Version 8.2 Auf der Landing-Page von Meteonorm 8 sind noch die mittlerweile veralteten Angaben von 1996-2015 angegeben, die für Meteonorm 8.0-8.1 zutrafen und von uns auch dementsprechend ausgewiesen wurden (1996-2015). Viele Grüße, Ben

Hello Garry, thanks for reaching out to us. Please feel free to contact our database team via database@valentin-software.com . After you've received a login you may visit https://pvsol-database.valentin-software.com/ for further processing. Best, Ben

Hello Indy, the manufacturers can add products themself to our database. We kindly ask them to update / add products so I will forward your request to our team. However, the fastest solution is to add it yourself. You may copy the HPS-6000 and edit the values differing for the HHS-6000 (look at https://de.enfsolar.com/pv/inverter-datasheet/12961 f.e.). Best regards, Ben

If you want to keep the PVGIS file, I highly recommend doing minutewise simulation. There is an auto-correction of most values and you will most likely see south-oriented have higher values than southwest-oriented panels again.

Let's put it that way : It is not uncommon for PVGIS. But not all locations have flaws fortunately. They try to improve so it is still good to look at each location for anomalies and to reevaluate when a new version is out (f.e. PVGIS 5.3). Main things to consider are: missing GHI data unnatural GHI data missing temperature data offset in sun-course with GHI data The best way to dive into wbv data before the simulation started is the MeteoSyn Details view at the moment. The sun position is calculated afterwards and not included in the weatherfile. However it is based on timestamps in the weatherfile. You can also do a database-sanity-check in MeteoSyn and put Phase I to mode "Expert". In the following dialogue you'll see "findings" of the weatherfiles in your database. The current problem you mentioned here will not be detected yet. You also have the possibility to copy the simulation-results data into a table, f.e. paste it into Excel.

Dear Asger, today I further investigated your issue. The problem is that PVGIS has an offset in their timestamps, that the sun-course over the day does not match with the GHI data. You can see it for example on 14th of may in the picture below. That leads to an higher, unnatural GHI peak towards the end of the day. We try to further improve our precheck when fetching the data to prevent downloading these locations. Best, Ben

You have a notice in the MeteoSyn-Location-Details view about missing periods of GHI data. If you use this location this will be treated as no GHI for this period. Best regards, Ben

The high west value most probably comes from PVGIS data with irradiation peaks at the end of the day. Although this is no pattern which is as obvious as in my first response, you can still find those peaks in the PVGIS data. For example on october third you have higher global-radiation at the end of the day (black square) resulting in higher irradiation on the south-west pvmodule (red) in comparison to the south-pvmodules (blue). I did not investigate the whole year and did some maths on it due to limited time, but I'm pretty sure this is the reason.

Dear Asger, thanks for sending the project! The weatherfile used in the project is different from what you sent previously. The weatherfile in the project has at least two flaws : it has missing data in may and october. I guess this is the reason your project has these irregular results when using PVGIS. Hope this could help you? Best, Ben

Yes would be interesting indeed. You can click on my profile name and then you will find a button "Message".