Jump to content

developer_mh

Administrators
  • Posts

    1,855
  • Joined

  • Last visited

  • Days Won

    173

Everything posted by developer_mh

  1. HI Bert, thanks for the project files. What you see there as "hourly discontinuities" is the effect of hourly calculated shadows from the 3D environment. That is, they are calculated on a 10 min basis, but then averaged to 1h values prior to handing them over to the main PV*SOL application for performance reasons. One can see that the phenomenon is not visible until the module specific shading (and low light behaviour, which is of course dependent) come into play: And then: So, no error here, just hourly shading values. In future we want to be able to use 1min values of the shading as well, but this requires much more performance (factor 60), so unfortunately this is not so easy to accomplish. Hope that helps, kind regards, Martin
  2. Hi Bert, thank you for the question. Could you provide a project file, please? You can send it here in the forum by private message (to me). Or by email to hotline@valentin-software.com, with a short note that they shall forward it to me. Kind regards, Martin
  3. Hi V Solar, in PV*SOL you can only place modules on plane (i.e. not round) surfaces. For this reason you have to create the cylindrical shape out of approximations with plane sections. See this post here for some hints. I guess you want to place the PV modules on top of the oil tank? You would then have to create the dome out of small triangles (in Sketchup for example), like a geodesic polyhedron (http://www.wikiwand.com/en/Geodesic_polyhedron) PV panels on top of oil tanks... I like the picture there Kind regards, Martin
  4. Hallo Spap, hast du die Kosten für das Batteriesystem in den Wirtschaftlichkeitsparametern eingegeben? Auf der Seite Wirtschaftlichkeit -> Parameter zur Wirtschaftlichkeit -> Bearbeiten -> Kostenbilanz kannst du sie eintragen. Beste Grüße, Martin
  5. Hi Barbadori, PV*SOL doesn't show something like this out of the box, no, sorry. You would have to export the simulation results to a spreadsheet application (e.g. Excel) and craft it yourself, I guess. Kind regards, Martin
  6. Hello John, although it warms my heart to see a screenshot of PV*SOL expert, which is about six years old, I would recommend to use the current version of our software, PV*SOL premium 2021. We can't provide support for Expert anymore, I am afraid. https://valentin-software.com/en/downloads/ Kind regards, Martin
  7. Hi Keir, right now there is no other possiblity than to modify the values beforehand in a text editor or Excel or so, i.e. cut the values from line 1 to 5856 (01/09/19 00:00 to 31/12/19 23:30) and put them at the end of the file. But I will put this request on our list, it should be no problem to implement it. Kind regards, Martin
  8. Hallo loho, nein, diese Kombination geht in PV*SOL tatsächlich nicht. Eine Möglichkeit, die mir jetzt so spontan einfällt, wäre, das Ladeprofil des E-Autos aus den Ergebnissen einer netzgekoppelten Anlage zu extrahieren und als Lastprofil in einem netzautarken Projekt zu importieren. Beste Grüße und viel Erfolg bei der Projektarbeit! Martin
  9. Hi Tim, does this happen all the time or only after you do something special (like search coordinates, for example). As a side note: it is best to use the semicolon if you search for coordinates, not the comma, to separate latitude and longitude. Kind regards, Martin
  10. Hi Jordn, yes, this is true. This is often the case when we switch to new major versions, as we often have to change something in the internal structure of the project file. Kind regards, Martin
  11. Dear Tomasz, we don't have the modules in our database yet, but I will inform our database team. Just to be sure, you refer to those modules here: https://www.solaredge.com/products/smart-solar-modules#/ In the meanwhile, you can also try to enter the module yourself. All necessary data should be on the datasheet (except for the low light behaviour, there you can just select 'standard'). https://help.valentin-software.com/pvsol/2021/en/databases/components/pv-modules/ Kind regards, Martin
  12. Dear Berend, yes, this is possible. It depends on the module characteristics and the distribution of irradiance intensities. This module (used in the project that you sent to our hotline, thanks for that) has a positive relative efficiency in the irradiance range between 200 and 1000 W/m² (light grey curve is slightly above 100%). In relative terms, the module is therefore a little more efficient in the range of 200 to just under 1000 W/m² than under STC conditions; only below 200 W/m² does the relative efficiency drop. With such modules, you can often see a positive effect of the low light behaviour. Kind regards, Martin
  13. Hallo Bene-Solar, ja, das wäre gut, danke. Gerne hier im Forum per privater Nachricht. Viele Grüße, Martin
  14. Hallo Mart, ja, das ist derzeit so, die Strahlung auf die Modulvorderseite wird ausdifferenziert in den direkten und diffusen Anteil, die Strahlung auf die Modulrückseite hingegen nicht. Intern rechnen wir zwar genau so mit dem direkten und dem diffusen Anteil, aber es wird derzeit nicht gesondert ausgegeben. Bei vertikal aufgeständerten Modulen kannst du aber davon ausgehen, dass der Diffusanteil auf der Rückseite bei vergleichbarem Sonnenstand und ähnlicher Globalstrahlung etwa gleich ist. Den Bifazialitätsfaktor musst da noch nicht mit einbeziehen, der beschreibt ja nur, wieviel Prozent der auf der Rückseite auftreffenden Strahlung dann überhaupt verarbeitet werden kann. "Verluste durch Bodenreflexion" - dass da noch Verluste steht, ist ein Fehler, sorry. Bei der zusammenfassenden Energiebilanz ist einfach von "Bodenreflexion (Albedo)" die Rede, es handelt sich hierbei ja um Gewinne. Beste Grüße, Martin
  15. Hallo Ralf, das ist ein bekanntes Problem, das wir leider im 3D-Programm-Teil nicht richtig in den Griff bekommen. Es hängt mit der Bildschirm-Skalierung zusammen, die es jetzt immer häufiger gibt, da die Bildschirme immer höher aufgelöst sind. Eine Lösung wäre, die Bildschirm-Skalierung auf 100% zu stellen. Wenn dann aber alles so klein ist, dass es nicht mehr lesbar ist, helfen vielleicht folgende Tricks: Beste Grüße, Martin
  16. Hallo Philipp, nein, diese Option, also ein reines PV-Diesel-System, oder sogar ein reines PV-System ohne zusätzliche Energie-Quelle, ist leider noch nicht verfügbar in PV*SOL. Beste Grüße, Martin
  17. Hallo Art, wenn sich deine Frage auf die Situation nach Zusammenlegung der Zähler bezieht: Ja, das kann man so ein PV*SOL machen, es gibt ja dann keinen zählerischen Unterschied zwischen den Verbrauchern aus dem Eltern- und Sohn-Haushalt. Wenn sich deine Frage darauf bezieht, ob man auch den Übergang darstellen kann, also die vorherige und die Situation danach, zusammen in einem Projekt, dann lautet die Antwort leider: Nein. Viele Grüße, Martin
  18. Hi Ricardo, in situations where you want to create a database product that is not officially available, I would recommend to start with a copy of an existing product of the same manufacturer that is as close as possible to the product you want to enter. For example, from the same product line or so. In this case here, candidates are the SUN2000-36KTL and the SUN2000-50KTL. I would suggest that you take the missing values of the MPP efficiency from them. They are a bit different though, but most of the times, also in other Huawei inverters, the values 99.8 and 99.95% seem to prevail. Kind regards, Martin
  19. Hi Jimmy, Ja, you wouldn't believe the multitude of errors that you can have when programming Windows applications. It is like fighting against wind mills But anyways, the important thing is that we can identify the errors quickly and provide bugfix updates. This is really one unlikely bug. It is built deeply into the GUI components of WPF (the GUI element framework that is used for this dialog), but only affects this dropdown list for high DPI monitor scaling settings. But I guess we found a work-around for that. We will release it with R3 of PV*SOL premium 2021. Thanks for your feedback, kind regards, Martin
  20. Hallo, die Datenblätter, die dem Bericht hinzugefügt werden, sind nicht die originalen Datenblätter der HErsteller, sondern sozusagen eine Auflistung der Parameter, die bei uns aus der Datenbank kommen (in der Regel durch die Hersteller eingegeben). Insofern muss man da auch nichts selbst hinzufügen. Viele sonnige Grüße zurück, Martin
  21. Hi Ricardo, thanks for the files. The MPP adaptation losses come from the inverter parameters here: In one project, you use the SUN2000-40KTL-US with 96%, in the other project, it is the SUN2000-40KTL (without -US), with 98% MPP efficiency. That is where the difference in the energy balance comes from. And then, these values seem quite low to me. At least in the higher range of >20% the MPP converting effiency should be higher than 96%. Hope that helps, kind regards, Martin
  22. Hi Ricardo, could you provide the two project files, please? You can send them with a private message here in the forum. Thanks and kind regards, Martin
  23. Hi Infinitech, with a single license you can only run PV*SOL on one computer. You can, however, move the license from one computer to another, using the "Change Registration" dialog under Help -> Registration. But you can do this only once every six months. This is really only meant for situations where you set up a new computer or re-install your OS or something like that. Hope that helps, kind regards, Martin
  24. Hi Jimmy, I was just about to ask you if creating template projects wouldn't be an option for the default value issue. Glad that this way works for your needs. But I will put the wish of more default options on our list. Concerning your other points: Parts list: We didn't change this for 2021, the delete buttons were always there, but only for items that you user created "Third is the map selection in 3D view. When I first start the map selection the page is just white and it won't load. " - Does this happen all the time when you open the map view? And then thanks for your words about the features you liked We are always doing out best to deliver a software product that is really helpful for the users. But no matter how hard and intense we test (we have a huge bunch of automated tests, and we do nothing but manual testing weeks before we release), there are always issues in the first releases of a major version that we do not find. Sorry for that. Kind regards, Martin
  25. Hi Jimmy, just a short hint for the issue with the small/unusable buttons in 3D. Could you try to apply the work-around that is described here and see if it helps, please? Also, another one here: The paths need to be adjusted for 2021, of course. Please let us know if that helps. Concerning the rest I will get back to you - for now, thanks for the feedback! Kind regards, Martin
×
×
  • Create New...