Jump to content

Michele Oliosi

  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, NASA SSE in PVsyst is ancient data and I especially wouldn't rely on its wind speed data, probably it is zero as a placeholder for no data. They have had an update recently, I think, but we haven't updated on our side yet.
  2. Indeed, PVsyst doesn't really treat the ground collision. It will be up to you to define the tracking range so that it doesn't hit the ground. I think all simulations steps in which the trackers are “below ground” cannot be trusted, although in appearance the results do not seem too bad.
  3. It depends on whether you have chosen the “fast” mode or the “slow” mode. In the fast mode, the interpolation is used in the simulation. In the slow mode, the interpolation is shown in the iso-shading graph, but the simulation does the calculation properly with the 3D scene. It is a shading factor for albedo, i.e., it is applied to the albedo irradiance contribution to the front-side of the modules. This is why it is not weighted per energy, but is just a geometric factor.
  4. Hi, I see, thanks for checking this. We would need to see the file to find out what is going on. Can you send us the source file over at support@pvsyst.com ? We will have a look asap.
  5. Hi, yes, with caveats. Your trackers should all have the same nominal orientation, but they can follow the terrain. An error regarding discrepancies in the orientations may still be shown, but this can be bypassed by changing some tolerances in the advanced parameters. As a result, the reference orientation will be the average of all tracker orientations. There used to be a limit in the tracker axis orientation RMS deviation from the average to apply the backtracking. This is now mostly gone. However, the backtracking algorithm still moves all trackers similarly, according to the simplest backtracking on flat ground specifications. We do not yet handle independent trackers.
  6. Not really, but you can also choose to ignore these gaps. In some situations, they do not really affect the shadings much.
  7. Ok, so the difference occurs before the evaluation of EArray. My following hypothesis about what is happening is: The electrical shading factor table is changing from one simulation to the other. You can check whether this is the cause for the difference by switching to “linear shadings” and see if the difference persists. The fact that the table changes can be due to 2 different reasons: Since you are changing the pitch, the 3D scene is changed. This means that the shading factor table is recalculated. You should check that the backtracking works as intended. If you have perfectly flat ground, there should not be any electrical shadings, so you can output the variable ShdElec and check whether it is zero. The shading factor table of your variant has been calculated in a previous PVsyst version. In this case, the batch mode will make sure it is recalculated with the latest version. You can make sure this doesn't happen by viewing the Table in Near Shadings and clicking on “Recompute”.
  8. Hi ! Currently, only the torque tube gap can be included in the tracker design. If the motor / pile gap is significant, I would suggest splitting the tracker into several trackers, with the size between the gaps as their individual size.
  9. Ok, we will need to dig deeper. How about other quantities, such as EArray? In the report you find the yearly value in the table. You can also output this variable from the batch.
  10. I see. This is normal then, because the edited GHI and DHI were chosen in order to give back GlobInc close to GlPMeas when transposed. If you change them, you will not get back the same value. When comparing transposed measured GHI and DHI to GlPMeas, you are accounting for: fundamental uncertainty in the measurement (calibration, noise, ...) uncertainty in the measurement system installation (orientation, position...) Hay model uncertainty Because of this I cannot tell you what is the single source of the 4.9% discrepancy. One thing that is on our roadmap is use one of either measured GHI or DHI in addition to GlPMeas in order to have a better equivalence at the GHI and DHI level. I agree that it would be better with such an option.
  11. Each inverter has a nominal maximum power, which will determine the clipping level. This is defined in the OND, but of course you can also modify and save a new OND file.
  12. There seems to be a "time zone" setting in the NREL TMY header, for example: 723740,"WINSLOW MUNICIPAL AP",AZ,-7.0,35.033,-110.717,1490 Did you try changing its value ? It may be zero currently and needs to be changed to -6.0, or the opposite way. Let us know if this works
  13. The difference is related to clipping here. In the first variant, you have some grid limitation or inverter clipping, which leads to power peaks being all concentrated to the 12175-12200 kW bin.
  14. Hi, There is nothing to do at the moment. Unfortunately, PVsyst cannot add a slope to the bifacial backside irradiance calculation. However, in the simulation, the front side irradiance is computed accurately with the 3D scene data, this doesn't change. Only the backside irradiance evaluation will suffer from not being a correct representation of the 3D scene. We will need to improve the model to correctly cover these situations, but it will take some time.
  • Create New...