-
Posts
775 -
Joined
-
Last visited
Posts posted by dtarin
-
-
I too would like to be able to change the units on the uncertainty report page. As far as I know, it cannot be changed.
-
-
There is a glitch in the single line where if the user zooms in on the single-line, the distance labels disappear for the MV and HV runs. To get it back, one must toggle the main labels button. The distances also disappear when printing.
-
My guess is that you have defined an HV transformer under detailed losses, and so it is showing up in the single line. Remove the HV transformer, and it will show only the MV transformers to the injection point.
-
Have you defined a frame size?
-
You define the ac losses. Enter them according to your design.
-
Your AC losses are probably too high. Is 3.2% accurate? I dont think I've ever seen a plant with AC losses that high.
-
I'd like to re-suggest the ability to define a monthly soiling profile in batch simulations. This will facilitate running time-series analysis for soiling losses.
-
-
Yes, or the crosshairs.
-
Thank you.
-
In general, it looks as though PVsyst has a minimum built in, irrespective of what is stated in the OND file. EArrayMPP must be greater than 0.5% of Pnom, and I think there might also be an irradiance requirement, although I can't find the details at the moment. Changing the setting below did not change behavior in my test. Results were pretty consistent with the 0.5% requirement, but there were four hours where there was inverter output below this.
-
-
Change the tilt to -90 or 90 after it has been created and placed into shade scene.
-
It is common to install Tamb and Wspd sensors ~2m above grade (for 2P systems maybe higher). ASCE measurements for wind are taken at 10m height.
-
This might be because by default you have defined module spacing in the X direction, but the file you imported does not include this (because it is 1 in portrait). So PVsyst first imports the correct orientation and dimensions, but after saving, closing and reopening, it is applying the default module spacing. Since the X dimension + X spacing is greater than the tracker dimensions originally imported, PVsyst is automatically adjusting. It has in my experience changed it to landscape when this occurs, I haven't seen it change to 0 in portrait before.
Go into advanced settings and change the following. @Stéphane Degré If PVsyst were to identify 1P vs 2P, it could ignore X spacing in the former.
-
Hello,
Similar to the Aging tool where we can save each year as a new variant, it would be great if we could do the same for batch runs.
-
It may have run, but did you check that the results in the waterfall reflect a change in pitch? It's been my understanding one needs to use an array of trackers for this to work.
-
This should be under "how to" or another forum category fyi.
If you are using a shade scene which has individual trackers (like from a PVC import), you cannot vary pitch in batch mode. Varying pitch in batch simulations only works on regular arrays (in shade scene, go to create > array of trackers) or using unlimited sheds. If you have multiple arrays of trackers, you will likely need them all at the same X coordinate as well or with enough spacing that they wont run into each other. If you're running GCR analysis, these two methods should be sufficient. When using the array of trackers, specifying the tables in backtracking management is not needed.
-
Export the 8760 and create a custom weather file then reimport.
-
rotate 180 degrees
-
Another place to check is under advanced parameters setting the default value. But looking at it from another perspective, rounding in either direction is a difference of < 0.05% at the meter, and a second decimal might imply some level of precision that may or may not be there.
-
Have you defined LID only under detailed losses? If you define LID in the PAN file, it should stick; used 7.2.21 to test. Select "take value from module spec" in detailed losses.
-
Pxx Calculations
in Suggestions
Posted
It would be useful to see some additional features for the uncertainty tool and I would like to suggest the following.