Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Hallo Tim, vielen Dank für die Zusendung der Projektdatei. Es handelt sich um einen Bug. Unsere Entwicklungsabteilung arbeitet an einer Lösung. Kurzfristig hast du leider nur die Möglichkeit, den Schaltplan zu exportieren und die Kabelanzahl in einem Bildbearbeitungsprogramm anzupassen.
  3. Hello, Thank you for your inquiry. You can configure multiple module areas on different roof areas together. First, define which modules should be configured together. Select the desired modules from the first module area, right-click on the selected modules, and choose "Add to 'Define Module Areas' Dialog." Then use the dropdown menu in the top menu bar to switch to the second building. Now select the desired modules of the second module area, right-click on the selected modules, and choose "Add to 'Define Module Areas' dialog." Then click the "Define Module Areas for Configuration" button: You can rename the module areas if necessary (right-click → Rename). Then click "Configure": In the inverter configuration window, select both module areas and click "Configure module areas together": Select both checkboxes for "Polystring configuration" and "Connect strings with the same number in series," and assign both module areas to string 1: String 1 now runs across two separate roof areas: You have already implemented the parallel configuration of two strings, each with 19 modules, on the same roof area:
  4. Last week
  5. Hello everyone, I am redesigning the string layout of an existing PV system after removing some modules. The physical module layout should remain as close as possible to the existing installation. In the new design, every string must have exactly 19 modules in series. I have two separate questions: 1. Some 19-module strings have to run across several separate roofs. The roofs have the same tilt and orientation. Is it possible in PV*SOL to define one electrical string whose modules are placed on different separate roofs? 2. Independently from that, some strings have to be connected in parallel, for example two separate strings with 19 modules each as one parallel string group. How should this be modelled correctly in PV*SOL? The strings crossing several roofs are not necessarily the same strings that are connected in parallel. My main question is: Can PV*SOL handle both cases in one project, while keeping the real physical module placement as much as possible? If this is not possible directly, what would be the recommended workaround for a realistic yield comparison? Thank you very much for your help.
  6. Hello, Thank you for your inquiry. On the "System Type, Climate and Grid" page, you can select the "Stand-alone PV System" (with and without a backup generator) system type. Planning stand-alone systems in PV*SOL is based on the SMA Off-Grid Configurator program, which we originally developed for SMA. This program contains the design rules that SMA has specified for us. These rules cannot be changed or deactivated. For example, only systems with AC-coupled battery systems can be planned; DC systems are unfortunately not possible. We understand that these rules may not necessarily apply to other manufacturers and may entail further limitations. For greater flexibility in component selection and improved transparency during the planning process, we recommend that you initially plan your stand-alone system as if it were a grid-connected system: On the "System Type, Climate and Grid" page, select a grid-connected system. Set the feed-in limit to zero; then no energy will be fed into the grid: The value under "Total consumption covered by grid" indicates the energy that cannot be covered by the PV system. This energy must be provided by the backup generator or (if you are not planning on a backup generator) "approach zero".
  7. Hello, Thank you for your message. Registration on the Rexplorer website is not required. You can generate an API key within the PV*SOL premium 3D environment. If you do not yet have an API key for Rexplorer, or if you have not yet entered it in PV*SOL premium, only the button for managing the API key will appear. Clicking the button will take you to the window where you can manage the API key. In this dialog, you can manage your Rexplorer API key. If you don’t have a Rexplorer API key yet, simply leave the API key field blank. An account will then be automatically created on Rexplorer using the email address displayed above, and an API key will be generated. When you sign up, your email address will be transmitted to Rexplorer’s servers. Rexplorer’s Privacy Policy and Terms of Use apply. If you already have an API key from Rexplorer, you can simply enter it here. If you have forgotten your API key, you can retrieve it in the Rexplorer portal. You can find further information about the Rexplorer API and managing the Rexplorer API key in our help section.
  8. Hallo Tim, vielen Dank für deine Anfrage. Bitte sende uns die Projektdatei (*.pvprj) an hotline@valentin-software.com, dann sehen wir uns das an.
  9. Moin zusammen, ich habe folgendes Problem in PV*SOL Premium 2026 R6: Wenn ich die Kabelverluste detailliert betrachte, wird bei einem Wechselrichter die Anzahl der Kabel unter „Pläne und Stückliste“ im Schaltplan falsch dargestellt. In der Übersicht unter „Kabel“ ist die Verteilung korrekt. In meinem Beispiel werden dort 3 × 15 m und 1 × 15 m angezeigt. Im Schaltplan bzw. in der Stückliste erscheinen jedoch stattdessen 4 × 15 m und 4 × 15 m. Ich habe bereits versucht, die Kabel anzupassen und auch die Verschaltung der Wechselrichter neu zu erstellen, da ich vermutet habe, dass sich die Übersicht dadurch aktualisiert oder zurücksetzt. Leider hat das bisher nicht geholfen. Gibt es eine Möglichkeit, dieses Problem zu beheben, ohne das komplette Projekt neu anlegen zu müssen? Vielen Dank im Voraus! Beste Grüße Tim
  10. Thank you very much for your reply , i tryed to create an Rexplorer account but from unkown reason i don`t get the CODE via email. Thank you very much for your time. Appreciate
  11. KALA

    Off-grid System

    Hello. Configuring an offgrid system with PVsol is impossible. How come it has not been fixed ? Any support from PVsol ???
  12. Dear Mark, Thank you for your inquiry. Open-circuit voltage is temperature-dependent. This temperature dependence is defined by the temperature coefficient, which can be found on the module data sheets. The configuration limits take into account a minimum temperature of -10°C, as encountered in temperate latitudes. If you are planning a system in subtropical or tropical regions, you can adjust the lower and middle of the three temperature limits upwards. For example, if the outdoor temperature in Namibia fluctuates only between 9°C and 34°C throughout the year, you would set the lower temperature limit to 5°C and the middle limit to 20°C:
  13. Dear Mark, Thank you for your message. Yes, we confirm that you must use the exponent 1.3278 instead of 0.55.
  14. Ho is this possible below if you have 9 x Jink0 590Watt BDV panels installed. The VOC of these panels is 52.9Vdc and multiplied by 9 gives you 476.1Vdc, and not 519Vdc as per PVSol below:
  15. hotline_oh

    Inverter Data

    Hello, Thank you for your inquiry. Your datasheet appears to be outdated. The official Deye website lists the maximum operating current as 78 A and the maximum short-circuit current as 132 A.
  16. Hallo, vielen Dank für deine Anfrage. Auf der Seite "Kabel" navigierst du in der linken Baumansicht zum gewünschten Wechselrichter und fügst je ein Schaltzeichen für den Leitungsschutzschalter ein: Für den Funkrundsteuerempfänger findest du in der Liste der Schaltzeichen verschiedene Möglichkeiten. Den Zweirichtungszähler mit integrierter dynamischer Einspeiseabregelung findest du unter "Schaltzeichen nach Verbraucher": Es werden beide Wechselrichter abgeregelt: Wenn du darstellen willst, dass nur einer der beiden Wechselrichter abgeregelt wird, bleibt dir nur die Möglichkeit, den Schaltplan in ein Bildbearbeitungsprogramm zu exportieren. Der Schaltplan kann in den Formaten PDF, PNG und SVG exportiert werden.
  17. Mark

    Inverter Data

    Good Day, Can you please make sure the data in PVSol Database is correct for the specified 16kW Single Phase Inverter. Something does not look correct if I compare the DC data with the Datasheet of the inverter. Max DC Input Power should be 25.6kW Max Input Current should be 96A Max Short Circuit Current should be 180A
  18. Thanks, so in place of the 0.55 constant I must use the 1.3278 constant. Correct?
  19. Merci! Vielen Dank für deine Antwort! Eine Frage zum Schaltplan: Ich möchte gerne 2 verschiedene Wechselrichter für mein System nutzen und brauche entsprechend 2 verschiedene Leitungsschutzschalter! Wie kann ich je Wechselrichter unterschiedliche LS darstellen? Sowie den FRSE mit Abzweigung vom großen WR darstellen? Vielen Dank schonmal für die Info!
  20. Hello, Thank you for your inquiry. Please send your project file (*.pvprj) to hotline@valentin-software.com so that we can take a closer look at it.
  21. Dear Mark, Thank you for your message. The formula is correct, but the exponent (0.55) is not a standard constant; it varies depending on the battery type and even within a single battery type. PV*SOL Premium uses a value of 1.3278; this value models lithium iron phosphate batteries with sufficient accuracy. Unfortunately, we are unable to model higher accuracy (using variable exponents).
  22. Hello, Thank you for your inquiry. You are currently registered in the license portal as both the license manager and the license user for your license. Please log in to the license portal and set up a new license manager and a new license user. Then, deactivate your own license usage and activate the second license user for your license. You can find further information on the roles of license manager and license user in our online help.
  23. Hello, Thank you for your inquiry. Two planning methods are rather unsuitable: - Using the Rexplorer API, because the L-shaped building (two intersecting gable roofs) is unfortunately not rendered correctly. (However, you can use this method effectively to retrieve building and roof dimensions by drawing layout areas onto the 3D models and displaying their measurements; please see the attached project file.) - Using the Google Solar API, because the image quality is rather poor. We would therefore recommend importing a Bing Maps section, as the image quality is significantly better and allows you to easily position the various obstructions (roof windows, chimney, etc.) based on the texture. We would: - extrude two gable roofs, - adjust the building dimensions accordingly, - disable building collision, and - overlap the two building sections. In this video tutorial, we demonstrate how to assemble a complex roof from multiple roof sections using an L-shaped bungalow as an example. (Please use the English subtitles for translation.) The disadvantage of planning with a Bing Maps section (compared to the Rexplorer API and Google Solar API) is that you cannot automatically account for shading caused by the church tower and the tree (located northwest of the house). In this case, you must manually insert the objects that cause the shading. Rugendorf with Bing Maps and extrusion.pvprj Rugendorf with Google Solar API.pvprj Rugendorf with Rexplorer.pvprj
  24. Hello, Thank you for your inquiry. If you wish to position elevated modules in an open space or on a flat roof, you must first define the mounting system. You cannot rotate the mounting system. If you wish to position a second module table next to the first one with a different orientation, create a second mounting system with the new orientation. We explain how to define and position a mounting system in this video tutorial, starting at the 4-minute mark:
  25. Hello. I am leaving my current position, and as a result I would like to change the email address associated with our PV SOL license. How can I do that?
  26. max

    Incorrect shading

    Hello, I tried this software maybe year or two ago, tried it again now, and seems I still have shading issues with imported models. I've checked and this impacts not only rendering but calculations also I guess. Is there workaround or fix? I have crazy results with this glitch. I don't know how to explain this, like shadow casts inside of object on backface and then inverts from other side at some angles. Seems there are no issues with inbuilt geometry, but even simplest box imported from 3ds max (3ds obj) gives headache. I've attached my 3ds model. And unfortunately this making this software unusable for me. Standard approach is to draw blueprint of walls in acad, refine it in 3d software, import. PVSOL just can't create more or less complicated geometry of roof. And last two screenshots are example of incorrect shading result with imported geometry and inbuilt geometry walls. This looks like minor glitch in import module because native geometry works just fine, and I hope it can be fixed (or it will be fixed), my geometry is really simple here single_model_sliced.3ds
  27. Title: Advice needed – modeling a complex multi-plane roof in PV*SOL (beginner) Hello everyone, I am still fairly new to PV*SOL and would really appreciate some guidance from the more experienced users here. I am currently working on a project with a rather complex roof geometry. The building has several roof planes with different orientations and inclinations, including hipped sections, multiple ridges and valleys, and a few smaller adjoining roof areas (please see the attached aerial view from the PV*SOL map import). The customer's explicit wish is to have the entire roof fully covered with modules – on all available roof surfaces. This is a fixed requirement on their side, so I am not looking for advice on whether it makes sense, only on how to model and realize it cleanly in PV*SOL. My main questions: • What is the best workflow for building this kind of multi-plane roof in the 3D view? Should I model each roof surface separately and then combine them, or is there a more efficient approach? • How do you handle the transitions between hipped/triangular surfaces and the trapezoidal areas so the module placement stays clean? • Are there any tips for keeping the orientations and tilt angles accurate when working from the Google/orthophoto import? • Any general best practices you wish you had known as a beginner with irregular roofs? Since I am just starting out, any advice – even small tips – is genuinely helpful to me. Thank you very much in advance for your time and support. Best regards
  1. Load more activity
×
×
  • Create New...