dtarin
-
Posts
777 -
Joined
-
Last visited
Posts posted by dtarin
-
-
Set the partition and select all tables of the scene, and all tables will adjust even if you have 1, 2 or 3 string trackers. It will be defined based on the dimensions of the partition.
-
Near shadings consists of beam, diffuse, circumsolar, and albedo losses. @PVsyst, circumsolar is missing from the help menu, see attached.
-
It is indeed an OR function. You can apply your grid limit as defined in the menu at the inverter or the injection point after AC losses, but not both. To do both, export the 8760 and set different limits in excel: 1st at the inverter, then apply AC losses, then apply POI grid limit.
-
Diffuse shading
-
You have to use all mppt inputs.
-
Your inverter already has enough mppts, sorry I assumed you were modeling with something that didn't
-
-
Set dummy MPPTs in the OND file. You can set two for PCS 3 and 4, and create five sub-arrays in PVsyst for building 1, 2, 3, 4 and 5. You will then use the power sharing feature and set subarrays 1 and 2 (building 1 and 2) to PCS 3 using MPPT share and subarrays 4 and 5 (building 4 and 5) to PCS 4 using mppt share. Subarray 3 (building 3) I assume is 24 strings and you can put on two PCS in one subarray, no need for mppt share.
There are other threads which go into detail on how to do this.
-
You would use 0.91 in PVsyst. If you run PF in PVsyst with 0.95 with a long MV run and a transformer, and you apply a grid limitation at the injection point, and set the grid limitation loss separate, you will still have an inverter operating at 0.95PF. Changing the length of the cable will not change this. You can confirm this by checking the maximum output power of the inverter.
If you do not account for grid limitation loss separately, then the inverter output will be reduced further. PVsyst takes the grid limit loss and adds it to the Il_Pmax loss. For example, I have a 3.6MW inverter, I set a 0.95PF, with MV AC, XFMR loss, and a grid limit of 3.0MW applied at injection point but do not check account as a separate loss, my maximum inverter output (for this particular case) is 3034kW. When I check account as a separate loss, my inverter output is ~3420kW, or 0.95PF.
-
It will likely be resolved in the next patch. Downgrade to 7.2.17 in the mean time as this is unaffected by the issue.
-
You cannot batch simulate 3D scenes with terrain. If you have a standard block of trackers, you can vary that pitch, but they must be created from the tracker block and not be individual tables. It says there in the batch menu, "These parameters apply to regular arrays of sheds or trackers only!"
To generate reports, check Create PDF Report in the batch menu under Simulation parameters.
-
Funny
-
Two ways. One, you can use a weather file which corresponds to each, or two, using a standard TMY weather file, calculate your P90 factor, and multiply your P50 8760 data with it to get a P90 dataset.
-
Reference letter for each building, does this mean that B, H, N, and P are different buildings, and hence, would be separate arrays?
In any case, this is a pretty broad question without details, so I will give a range of answers. You can change the module wattage to fit your DC capacity better, round to the nearest string quantity that fits your DC target (as closely as possible), or use microinverters/optimizers. You may not be able to hit 79.58kW exactly, and will have to install something less that fits.
-
7 minutes ago, laurahin said:
1) In the PVsyst report, a variable "EArray" is shown in the "Balances and main results" table, but "Array nominal energy" and "Array virtual energy at MPP" appear in the waterfall diagram. It would seem confusing if the report really shows array output with different PP regulation assumptions in these two locations, but maybe nobody looks that closely.
I agree, PVsyst only allows the last two variables in the table to be selected by the user, but all variables in this table should be able to be edited and selected by the user. If there is a way to edit all variables, I haven't found it yet.
-
50kW is your bin class size, not 200. Count the number of "steps", it is 20 steps to 1000, bin size of 50. The Y axis is MWh per each bin class of 50kW.
-
There are more hours in the year at one of the power output level compared to another. Filter your 8760 to verify.
-
9 hours ago, Michele Oliosi said:
Yes ! We should have been more detailed in the documentation. Maybe some old FAQ post clarifies this, but I couldn't find it. Where did you get this info @dtarin
@Michele Oliosi With 8760 data. I have not seen it elaborated on the forums prior.
-
- EArrMPP = DC input into the inverter when max power point tracking
-
EArray = EarrMPP - (IL_Pmax + EGridLm)
- It is the mppt DC energy minus the clipping losses, even clipping due to POI limit.
- POI clipping will also move the inverter operating point in reality, so I suppose that it why it is included?
- The help says the following,
-
Quote
taking inverter operating point displacements into account
- EOutInv = EArrMPP - InvLoss
-
EGrid = EOutInv - (EACOhmL + EMVOhmL + EMVTrfL + .... + EGrdLim)
- This will change depending on if you have defined AC losses, whether you have accounted for unused energy from grid limit separately, etc.
In looking at the equations above, we can see that it is indeed possible for EArray to sometimes be close to EGrid. If you have not implemented a grid limit and display as separate loss, you wont have EGrdLim (it will = 0).
Regarding BESS, it depends on how your model is set up, so can't really say whether it is correct or not. This is DC coupled, correct? Are you sending EArray directly to grid (minus IL_Oper/Pmin/Vmin/Vmax/Imax) and IL_Pmax to batteries?
-
The software can only output hourly values.
-
Import the layout image and scale it, then draw zones on top of the image.
-
+1
Perhaps auto save changes into a running log that stores last N changes, in addition to a user-input comments/notes section.
-
It depends. What do your inverter losses look like? You don't necessarily have to change anything, but if you are getting high inverter losses , then maybe you want to reconsider the design.
-
I am running on two machines, laptop and desktop, and have not noticed a drop in performance.
Partition function does not work for tracker imported from pv case after last updated (7.20)
in Problems / Bugs
Posted · Edited by dtarin
For why PVsyst shows 80 modules instead of 81, check the module spacing you have in whatever software is generating the PVC file, and what you have by default in PVsyst. If for example you are using PVCase with a module spacing of .01m and your PVsyst default is .02m, you will not get the same number of modules. This does not really matter though. PVsyst is calculating shading losses here, nothing else, so if the area of the tracker block in total is representative, then I dont think it matters if it says 80 or 81. The generation calculations are done based on the system definition, not by the module quantity in the shading scene.
Try setting PVsyst default module spacing to 0.00 (X and Y), then reimport the PVC file.