kjs55

Here's one way CCC could be incorporated into PVsyst, to enable more accurate modeling with standard hourly TMY datasets:

PVsyst V8.0.10 -> Grid-connected -> Load Demo utility project (_DEMO_Utility.PRJ) -> VC4 -> Detailed losses -> Ohmic Losses -> Uses a HV transformer -> Dropdown menu HV to MV Transformer does not work.

Let's imagine you have a 100 MWdc PV system with: - Split Si PV module design using half-cut PV cells in Orientation #1 with split partitioning, and - CdTe PV module design in Orientation #2 with no split partitioning How do you assign: - "according to module strings" with 100% "fraction for electrical effect" for Orientation #1, and - "linear shadings" for Orientation #2 ? Please advise. Thanks.

v7 and v8: Typo in the word "proportional"

Suggestion to add a third option for the ac losses power reference value, namely, a custom user-defined input value field. The reason for this is that sometimes ac losses are not defined at either of the two (2) presently available toggle options in PVsyst, namely, "PNomPV(ac) at STC" or "PNom (inverters)", but rather at some other ac losses power reference value (e.g., driven by the grid limit). Thanks.

Apologies if this is documented somewhere and I missed it (if so, please feel free to point me to the already existing answer). Are "secondary parameters" used in PVsyst's numerical simulations? Or, are these just informative settings? The only help documentation I can find says: "Secondary parameters": sometimes useful parameter. I'm not sure how to interpret this. Please advise. Thanks.

Apologies if this is documented somewhere and I missed it (if so, please feel free to point me to the already existing answer). Would you please explain how the internal transformer settings in the PVsyst .OND file are applied? Or, are these just "informative" settings? Thanks.

P.S. Please note the 5xxxx3 MWh value also shows up in the Report on the Loss Tree, in the "Balances and main results" table, etc.

PVsyst v7: Sum over E_Grid 8760 is 5xxxx2.3 MWh, which rounds to 5xxxx2 MWh. NB: 8760 has night losses. PVsyst Loss Tree (copied to Clipboard and pasted into Excel) yields 5xxxx3 MWh (no decimal places provided). If you remove one row from the 8760 summation, you get 5xxxx2.5 MWh, which rounds to 5xxxx3 MWh. So this tells me the PVsyst Loss Tree is missing a single row from its summation (namely, it's summing 8759 rows, not all 8760 rows). Please confirm it. (NB: Exact values masked for confidentiality reasons.)

PVsyst v7 & v8: In the PVsyst Report (output PDF file), please note the ambient temperature of all inverter power ratings. For example, please include: Unit Nom. Power (~>50 oC) = 765 kWac where the "at 50 oC" is added. Similar to: Max. power (~> 25 degC) = 840 kWac Please see attached screenshot. Thank you!

Open PVsyst v8.0.8 / demo projects within it, get this pop-up: Please advise.

Sorry, I don't have time to do a detailed bug report. If you cannot reproduce this, please add a comment and I'll add more details. v7 & v8: Activate Power Factor on PF tab of Energy Management. Then go to next tab Grid Limit and activate w/ Apparent Power basis. You'll see the units of Grid Limit change from MW to MVA. Now return to PF tab and deactivate it. Now return to Grid Limit tab. Units of Grid Limit remain as MVA instead of changing back to MW.

I also noticed that the value entered into Grid Limit doesn't round, it truncates. Why? And the allowable significant figures is inconsistent. You can either enter 0.17 kW with max. two (2) sig figs or 999.17 kW with max. five (5) sig figs. Why? The relative (%) impact of the truncation will of course depend on the value entered. It seems like an easy enough fix to allow a fixed number of sig figs, e.g., several (more is better, e.g., so that we can exactly match utility contracts which can be defined as irrational numbers). It also appears that the units go from kW to MW depending on the project's power capacity, so ideally the increased number of allowable sig figs could also be consistent regardless of the units. Thanks.

@S.Faulkner: See PVsyst Release Notes for v8.0.0 ("Corrections"): https://www.pvsyst.com/help/release-notes/index.html#exec-1--corrections "Simulation: the bifacial mismatch loss is now proportional to the Bifaciality factor"

@S.Faulkner: See PVsyst Release Notes for v8.0.0 ("Corrections"): https://www.pvsyst.com/help/release-notes/index.html#exec-1--corrections "Simulation: the bifacial mismatch loss is now proportional to the Bifaciality factor"