Jump to content

dtarin

Members
  • Posts

    626
  • Joined

  • Last visited

Everything posted by dtarin

  1. Change your setting in hidden parameters. But it looks like that you need to recalculate, as that is very close, and shouldnt give the error.
  2. I think he meant that we would like to misalign the modules to the eastern direction. Entering a positive value for misalign points them to the west. Entering a negative value for misalign points them east, but this it not allowed. I also would like to misalign to the eastern direction, but do not know how (or if it is possible) to do so.
  3. This is exactly what I said in my first answer to this post. The active energy production will not be affected, until the Pnom limit (in kVA) will be reached. The power factor acts as a diminution of the nominal output power (Pnom) expressed in terms of active energy [kW]. In your example: Pnom (apparent) = 60 kVA => with 85% PF Pnom (active) = 51 [kW] will be applied for limiting E_Grid when running the symulation. PVsyst works in this way of course. Andre, Will PVsyst work in the same way with inverters which have a temperature de-rate curve established in the OND file, such that the entire de-rate curve is multiplied by PF?
  4. Hello, It would be extremely useful if it were possible to import multiple meteo files at once and automate the creation of multiple MET and SIT files.
  5. Hello, From the simulation menu, I press output file, and then I select to change file. The file type that is shown is a MET File, and I cannot see other csv files in the directory. See attached image.
  6. Try changing the discriminating angle, set to 1 degree. See image.
  7. Hello, I have a system with multiple orientations but only one sensor mounted for one orientation collecting POA irradiance at a one minute interval. Is it possible to use this POA irradiance to calculate GHI, and then use this GHI to calculate POA for other orientations? Or can I convert directly from one POA to another?
  8. It would be helpful to add a timer to the hourly simulation progress, or include it in the output file(s). For long simulations, it would help budget time and plan work accordingly.
  9. Hello, I just upgraded to 6.6.2, and I am missing the options to add variables to my simulation output and also in batch simulation mode. Thank you.
  10. Hello, I am running a simulation with an OND file that had a night loss parameter. I set this value to zero and saved the OND file, variant, and project. When I run a batch calculation though, the runs are all done with night loss still there. When I run a single simulation, the night loss is not there in the 8760 data. Thank you.
  11. There is no straight answer. Dimensions for a table depends on different factors like cost, the conditions of the ground, type of racking, type of modules, size of system, etc. Sheds will give you a more accurate estimate when partitioning into strings and calculating electrical loss due to electrical effect; the table method will slightly underestimate this. Tables give more flexibility in being able to position on top of ground objects, you can use them in zones, etc. If you zone is very large, it could be why it is crashing. Break it up into N zones, get one section into position, then work on another. Once created, you can copy all the modules and paste and position. Also if you provide images it can help to provide an answer.
  12. I am referring to other parameters of a PV table/shed, like the inactive band size or module spacing.
  13. Hello, In the new shade scene construction, it gives an option to select the module for that shading object. I have a project with two different modules, and the shade scene seems to pick which module is attributed to which array by default, and does not change. If I select the module it is not defaulted to, it reverts back. Is this a bug, or is there something I am not doing or understanding correctly?
  14. abdulrahman95 , Is this what you mean by curved suface? You can create a ground object which matches the terrain, then create a zone of tables/modules on top of the ground object, and then select position tables on scene. This doesnt work for every PV field (ie tracker).
  15. The measuring tool was modified in the newest release, and I think it is now missing one of the most useful features. It does not lock onto objects in the same manner as before, such that when you snap it to two corners and move one of the objects, it does not stay locked and show you the distance as it changes. Placing objects around the array or setting the pitch for PV sheds/tables make use of this now missing feature.
  16. Hello, Is it possible to modify the module type for more than one PV table at a time? Selecting multiple and pressing ctrl+m to modify does not work for me. For complex array layouts with many independent sheds, this is a very tedious task. Using 6.6.1. Thank you.
  17. I have also had an error in 6.61 importing ground images. The image covers up the array, but does not cover objects like trees or buildings.
  18. It would be nice if the units were included in the column header.
  19. I have seen older versions of PVsyst project higher losses compared to newer versions when running the same project.
  20. Hi Andre, The PVsyst help section states, "...you should be aware that the resulting simulation will not be valid for the first production year..." Could provide some additional information or explanation on why the light-soak gain is not valid for first year energy? I was thinking it might have to do with the time it takes to stabilize, but would like to hear from you on the matter. Thank you.
  21. Hello, According to this page, http://forum.pvsyst.com/viewtopic.php?f=20&t=1594, it states, "...Now it is often believed that when the bottom cell row is shaded, the by-pass diodes will limit the electrical loss to the sub-module row, i.e. the string electrical production will remain 2/3 of the normal production. This is only true (about) if you have one only string per MPPT (violet curve)..." With microinverters, we have one module/string each with its own MPPT. Is it correct then to create the partition size in the shade scene based on the submodule size, as in for a single module, creating three strings in height x 1 in length?
  22. Thank you for the reply. The help does not provide much guidance in determining this weight factor. I am more concerned with how and when to utilize the according to module method for calculating shading losses. I cant seem to get an answer on if it is the most accurate method to estimate shading losses, or if it is something else. If the according to strings method is the upper limit, is the according to module layout the lower limit, and the best estimate somewhere in between?
  23. Is using the method you described above a reliable or accurate method to generate global incident energy for multiple orientations? I have sites with multiple orientations but only 1 weather station, so I am curious to know if this can be used to create a simulated POA for system performance testing for multiple orientations.
  24. Thank you for the reply, that was my guess for approaching the implementation (hadnt gotten to trying it out). As for your comment on overproduction, I cant think of a way to test or benchmark this. Perhaps Andre or someone at PVsyst with a better understanding of what is happening could comment on this.
×
×
  • Create New...