Jump to content

Stéphane Metz

Members
  • Posts

    112
  • Joined

  • Last visited

Posts posted by Stéphane Metz

  1. Hi Meurville,

    The IFC format is not supported by PVsyst. As mentioned, only 3DS, DAE, H2P and PVC are supported.

    The solution is to convert your IFC files into one of the supported formats (DAE or 3DS) with a dedicated tool such as Sketchup.

    Regards,

    Stéphane M.

  2. Hi Mohammed,

    Indeed, PVsyst does not allow for the moment to fill the zones with domes. However, there is a workaround that can help you with your park filling estimate:

    1. First create a zone as you did with an azimut of 90°:
      image.thumb.png.8d1454204b5245e0161033e243deda1c.png
       
    2. Then quit the zone editing tool, select all your tables, and change their origin with the advanced selection tool (CTRL+G):
      image.thumb.png.223b7c82fa74b4dbd985b90dfcbf55ca.png
       
    3. After select only the tables you want to rotate in the opposite orientation (here East), and change their azimuth to -90°:
      image.thumb.png.851b702d5bcee4878a206732bd966df8.png

    4. The result corresponds to East-West "domes":
      image.png.b28423ac0cdaffab2bb0c1b4c7f5051d.png

    Hoping to have been able to help,

    Stéphane M.

  3. Hi @VUG,

    Your PV fields follow a ground slope, this introduces baseslope angles of each PV fields. That means that the real tilt/azimuth angles are not the same as the nominal ones.

    You can use the orientation educational tool to better understand this concept:

    image.thumb.png.658b4d8b6a748c25798a33f283e8eea6.png

    So, in this case, PVsyst has detected several averaged orientations and grouped your fields there.
    Note that PVsyst is currently limited to 8 orientations, you’ll have to deal with this constraint.

    To see the orientations, you can use the orientation management tool:

    image.png.40356e918dafa2e3a180164957b046d7.png

    To limit the number of orientations, try to re-identify orientations with higher tolerance:

    image.png.645762e51a50587b9e2bfd9dcc4d0548.png

    Or delete all orientations, create 1 or more new orientations and manually assign the fields, the averaged orientation will be determined automatically:

    image.png.ae09b0bda9fe2e5af9df70cac2ef376c.png

    Note that the azimuth used in PVsyst is the real azimuth and not the nominal azimuth, because it is the real azimuth of the orientations that is used for the calculations.

    Regards,

    Stéphane M.

  4. Hi @anish.silwal,

    You can use the "List and management of objects" tool (CTRL+G):

    image.png.52fbdfb2a165ac75b5c39a74ebb681fe.png

    Select the trackers you want to edit, and change the desired value in bulk:

    image.thumb.png.2d4c1e66eb85b0092233c55f1957bb0a.png

    Note: in you screenshot, trackers are defined "By sensitive sizes". Be careful, in this case it's not possible to modify these values, because they are relevant only when tables are defined "By modules".

    S. Metz

  5. Dear @garf,

    Indeed, it is only possible to mix orientations 1 and 2. This is a current software limitation. If you want to mix orientations 1 and 3 for example, you will have to switch orientation 3 to orientation 2.

    FYI, we are currently working on version 8 which will remove a lot of this kind of limitation.

    Regards,

    S. Metz

  6. Hi Awie,

    Well, I took a look at your 3D file. The problem comes from the new 180° rotation feature introduced in 7.3.3:

    image.png.32d3447d8707dfd92e86195039bdfebb.png

    This doesn't work properly with PV objects. I opened an incident ticket here, it will be fixed in the next patch.

    In the meantime, uncheck this box (it is automatically checked in the southern hemisphere), and manually rotate the entire scene 180° if necessary after import.

    Thank you for reporting this problem to us.

    Regards,

    Stéphane M.

  7. Hi @iulian.trisca,

     

    Regarding your 2 points:

    1. This only happens if you haven't created any zones yet. This problem is also present in previous version. We will fix this for the next patch.
    2. This is a display issue specific to Trimax Solar PV modules, it is also present in previous version. We will fix this for the next patch.

     

    Thanks for bringing these issues to our attention.

    Regards,

    Stéphane M.

  8. Hi @C. Amorevole,

    Your problem is a frequent case in PVsyst, since the PV tables follow the slopes of the ground. You must define one or more so-called "averaged" orientation(s).

    From the 3D scene, open the orientation management window, and launch an automatic detection with a large enough tolerance to obtain the desired orientations:

    image.thumb.png.e760c18d5beef00b74c1894f4aba96e4.png

    You can also manually create your orientations if you wish (more details here).

    After creating the orientations in the 3D scene (8 at most), you will have to harmonize them with those defined in the system and assign the subfields to these orientations.

  9. Hi hcolin,

    Indeed, the value is limited to 100. It is an arbitrary value considering that beyond this value, the area is no longer really realistic. 

    Unfortunately this value cannot be directly changed, but I can forward your request to the DEV team. For our information, what values would you have liked to put?

    Regards

×
×
  • Create New...