developer_mh

Dear Emad Elkhwaga, please have a look at our help pages where we try to explain all the tracking options and parameters: https://help.valentin-software.com/pvsol/2018/pages/pv-modules/#tracking Also, please refer to this forum thread: And finally this one here: Hope that helps, kind regards, Martin

Dear Maha Dardir, please have a look at our help pages where we try to explain all the tracking options and parameters: https://help.valentin-software.com/pvsol/2018/pages/pv-modules/#tracking Also, please refer to this forum thread: And finally this one here: Hope that helps, kind regards, Martin

Dear PV*SOL users, we are proud to announce that we have published our new help pages now. You can find them here: https://help.valentin-software.com/pvsol/en/ We hope that you'll find them useful in the future, and we'd be glad to hear what you think of them. Thanks and kind regards, Your PV*SOL team

Hallo Arne, also, ich finde, das sieht eigentlich ganz gut aus.. Der Generator springt an bei Unterschreitung der Startschwelle (45%) und hört auf bei Überschreitung der Stoppschwelle (65%): Darüber hinaus wird der Generator auch bei den Pflegeladungen bei Bedarf gestartet, zum Beispiel hier bei der Voll-Ladung von 88% auf 97% (da hier nicht ausreichend PV-Leistung vorhanden ist): Wenn Sie dazu noch weitere Fragen haben, bitte immer gerne. Ansonsten haben wir ja neulich auch unsere Hilfe-Seiten überarbeitet, vielleicht finden Sie da noch was Interessantes: https://help.valentin-software.com/pvsol/2018/berechnungsgrundlagen/netzautarke-systeme/ Viele Grüße, Martin

Hi Michael, thanks a lot for the project files. In this case you use a DC coupled battery system. DC coupled systems are connected to the first PV inverter only, so adding or removing PV arrays doesn't change the energy that flows in or out of the batteries. In the circuit diagram you see that for the battery, there is no difference between your two system designs: I hope this helps, kind regards, Martin

Hello Michael, thanks a lot for your question. I am sure we will find the solution there. Is there any chance that you can provide the project files for the two cases? Otherwise it will be hard for us to understand what is going on in the system. You can send the project file as private message. Thanks and kind regards, Martin

Hallo palomita, Vielen Dank für die Nachfrage. Zum Nachvollziehen der Simulationsergebnisse wäre die Projekt-Datei sehr hilfreich. Was die Ladestrategien angeht, haben wir da tatsächlich vergessen, bei der letzten Erweiterung die Bezeichnungen anzupassen. Momentan wäre Folgendes richtig: Ladestrategie -1: Entladen 2: I-Ladung (maximaler Strom) 3: I-Ladung (normal) 4: Boost 5: Full 6: Equalizing 7: Float 8: Netzladung (nur für E-Autos in Ongrid-Systemen) 9: Entladung nicht aktiviert (nur für E-Autos in Ongrid-Systemen) Zu beachten ist dabei, dass hier die Stundenwerte ausgegeben werden. Die Simulation erfolgt aber in der Regel in Zeitschritten von einigen Minuten, weswegen dann während einer Stunde auch unterschiedliche Ladestrategien gefahren werden können. Diese werden dann durch das |-Zeichen getrennt dargestellt. Während der Float-Ladung wird den Batterien nur minimal Energie zugeführt, in Ihrem Beispiel liefert die PV dafür genug. In Full-Ladungs-Phasen wird der Generator in jedem Fall gestartet, falls die PV nicht genug Energie liefern kann. Das Erreichen der Start/Stop-Schwelle geht leider aus den von Ihnen angehängten Ergebnissen nicht hervor, weswegen da wie gesagt die Projekt-Datei sehr hilfreich wäre. Vielen Dank und beste Grüße, Martin

Hello Jan Sorensen, you can find more information on the cycle load of batteries here in our new help: http://help.valentin-software.com/pvsol/2018/calculation/battery-systems/lead-acid-batteries/ This is written for lead acid batteries but the section about life cycles (starts between Fig 2 and 3) applies equally for lithium based batteries. Hope this helps, kind regards, Martin

Hi Bernd, when you are in MeteoSyn, follow these steps: go to the list view of your locations, select the location you want to remove, right click, go to containing folder, delete the corresponding *.wbv file there go back to the MeteoSyn GUI, to the 'Options' tab click 'Update database' Hope that helps, kind regards, Martin

Hi Maha, you can easily add your own PV modules (or any other type of product) to the databases by opening the database dialog (Menu 'Databases' then 'PV Modules'). Then select the manufacturer, in your case 'Jinko Solar'. Then you can either select a module, right click on it, and click 'copy'. Or you can add a new one by clicking 'new'. In both cases you can enter the datasheet information and save the new module by clicking 'ok'. Here you'll find some more infomation: https://help.valentin-software.com/pvsol/2018/databases/components/pv-modules/ Hope that helps, kind regards, Martin

Hallo DucDiesel, das klingt stark nach einem korrupten Projekt. Damit sollte man sich in jedem Fall an die Hotline wenden, da die ein paar Tricks und Kniffe kennen, wie man solche Projekte wieder ans Laufen bekommt. Am besten per Mail mit Kundennummer und angehängtem Projekt (vorher private Daten entfernen!) an hotline@valentin-software.com. Keine Garantie, dass man noch was machen kann, aber in vielen Fällen geht noch was. Wir arbeiten auch intensiv daran, dieses Problem in den Griff zu kriegen. Scheinbar unterbinden manche Virenscanner in Einzelfällen das Speichern der 3D-Projektdaten in die Projektdatei. Alles Gute und beste Grüße, Martin

Hi Patrik, that is a nice idea. Actually we thought that building companies would model the building that can then be imported in PV*SOL and not the other way round ? But it is nice to hear that people are considering to use PV*SOL as a building modelling tool. I will forward this idea to my colleagues of the 3D team. Kind regards, Martin

Hey Patrik, in this case you would have to extrude one half of the building first, edit the inclination of the roof and then extrude the other half of the roof. Hope that helps, kind regards, Martin

Hi PS Renewables, right now it is not possible to enter more than 1000 V for the AC mains. But it is a good point, we should raise the maximum value for HV systems to more than 1000V. It will be available in the next release (PV*SOL premium 2018 R7). Kind regards, Martin

Hi Diego, please contact our hotline at hotline@valentin-software.com, they also have access to the licence management. Kind regards, Martin

Hi Stuart, could you try to load the example project 'Photo plan' and check if Photo Plan works there? Kind regards, Martin

Hi all, if you want to use Excel to convert the decimal coordinates e.g. from Google Maps into the pseudo degree.minute representation that is necessary for the dat file format, you can use this formula: =(A1-FLOOR.MATH(A1))*60/100+FLOOR.MATH(A1) Hope this helps, kind regards, Martin

Hello Maha, to achieve this, you can use the 'Configure Module Areas together' feature. See this post here on a similar question: When you search the forum, you will find some more information on that. Hope this helps! Kind regards, Martin

Hi Tim, if you refer to .dwfx and .dwf file format from Autodesk, I am almost sure that you can export your models into .obj or similar in their programs. I don't have AutoCAD here, so I can't test it, but it should work. Kind regards, Martin

Hi James, I tried to reproduce the change of the irradiation values, but here I also get around 875 kWh/m² in a fresh install of PV*SOL premium 2018 R5. So I suppose that the climate file might perhaps date back to PV*SOL premium 2018 R4, which was before we updated MeteoNorm to version 7.2. MeteoNorm is the climate data provider we use in MeteoSyn. When I create a new climate file with a fresh install of PV*SOL premium 2018 R4, I also get around 950 kWh/m². In MeteoNorm 7.2 there are a couple of changes that also affect global irradiation sums. If we have a look at the map with the differences of the global irradiation in the region where Scunthorpe is located, we can see that there is an area of negative deviation of around -50 to -100 kWh/m²: http://www.meteonorm.com/images/uploads/demo_uploads/diff_ghi_v72_vs_v715_europe.png On their website you'll also find the changelog that lists the changes of the data and the models they use: http://www.meteonorm.com/en/support/changelog I hope that helps and re-establishes the confidence in our product If you have further questions, please don't hesitate to ask. Kind regards, Martin

Hi Hayder Ali, there are several mismatch effects that we consider: In all projects we assume a standard factor for the mismatch losses in PV modules due to the small deviations of the nominal power of the PV modules. That means, that if you buy a set of PV modules labelled with 250 Wp, you will get some that have exactly 250 Wp, but others that have slightly more, perhaps sometimes even a bit less. Due to these differences, the PV modules will not react equally to irradiance or temperature changes, small inhomogenities occur in the field, and so you will have small mismatch losses. You can change the default value of 2% (which is very conservative) in the simulation options: Another type of mismatch, and the more important one, is a consequence of inhomogeneous shading on the modules, or different orientations of the module areas. So the shading effect can only be simulated when using the 3D environment. Modules in PV systems with near shading objects will always receive different levels of solar irradiance, and in consequence the feature varying i-v characteristics. For all PV modules in a string, the i-v characteristics are superposed, and when there are parallel strings, these i-v curves are superposed as well. The MPP tracker only sees the superposed i-v curve of the PV field and searches for the point of maximum power on this curve. This point will be the maximum for the PV field, but it will be less than the sum of all individual points of maximum power per PV module most of the time. This difference is the mismatch loss due to configuration or shading. You can read more on the superposition of the i-v curves here: https://help.valentin-software.com/pvsol/2018/calculation/pv-field/ You find both mismatch losses in the energy balance at the end: I hope this helps. If you have further question, please don't hesitate to ask. Kind regards, Martin

Hi camilo, The 3D map feature was introduced in PV*SOL premium 2016 Release 1 (November 23rd, 2015), PV*SOL premium 7.5 R4 version is older than that, which means, that the feature is not in the version you use. To have access to the newest features, please update to the newest version, right now it is PV*SOL premium 2018 R5. You can also test it 30 days for free, nearly without restrictions: https://www.valentin-software.com/en/products/photovoltaics/57/pvsol-premium Good luck! Martin

Hallo Maria (und andere), das hier hat sich auf eine sehr alte Version von PV*SOL bezogen. In den aktuellen Versionen kann man ganz normal auch csv-Dateien als Lastprofil einlesen. Siehe hier: https://forum.valentin-software.com/topic/671-lastprofile/?tab=comments#comment-1675 Beste Grüße, Martin

Hallo Maria, du kannst bei den Verbrauchern auch csv-Dateien einlesen. Einfach auf Neuer Verbraucher, dann auf den ersten Eintrag "Lastprofile laden und importieren", dann oben auf "Neues Lastprofil importieren" et voilà. In dem Dialog kannst du die entsprechenden Werte einstellen und deine Datei einlesen. Viel Erfolg! Martin

Hi hazywayrunner, in PV*SOL you will always have to define some kind of inverter in order to have MPP and voltage conversion functionalities etc. If you are interested in a DC application, you could change the grid voltage to your DC voltage (say 12 or 48 V or the like) and define an inverter that is really behaving like a DC/DC converter then, but with MPP tracking functionality included. But you can't disable the inverters or the AC grid. You just use inverters as DC converters and the AC grid would be your DC grid Kind regards, Martin