pvlib / pvlib-python

A set of documented functions for simulating the performance of photovoltaic energy systems.
https://pvlib-python.readthedocs.io
BSD 3-Clause "New" or "Revised" License
1.13k stars 955 forks source link

Module and inverter parameters from data sheet to pvlib-python #474

Closed Jawairia123 closed 6 years ago

Jawairia123 commented 6 years ago

I am trying to model a PV system using pvlib-python. The required PV modules and the inverter models are not present in any of the databases that's been used in either pvlib or SAM by NREL (updated version).

These models are:

Module = GCL-P6/72H 330 Inverter = SG2500HV (by Sungrow)

I want to know is there any standard way or any approach to input parameters from datasheets directly?

Thanks in advance!

cwhanse commented 6 years ago

Briefly, yes there are standard ways but they are not coded in pvlib.

As background, a module performance model requires certain parameter values (e.g., Rshunt for the CEC model) that are not found on datasheets. For modules, there are techniques to obtain parameters for some module performance model (e.g., De Soto, CEC) from datasheet values. The SAM SDK includes these functions, so you may be able to use SAM to get a set of module model parameters.

For inverters, it's a bit more difficult. The efficiency curves are needed; these could be digitized from the figure commonly found on an inverter cutsheet. The parameters for the Sandia inverter model can then be estimated by a fitting method. The method is not difficult (I have a spreadsheet somewhere) and I believe it is also coded in SAM.

Estimation of model parameters from data is an important gap which pvlib currently lacks. We welcome pull requests :)

vanpnguyen commented 6 years ago

cwhanse,

Could you provide step by step procedure to load a locally saved PV module file (CEC model) to Python? Also could you provide the template file for the CEC model so that i can populate the parameters from datasheet / SAM SDK?

Thanks,

cwhanse commented 6 years ago

We don't yet have the CEC model implemented but you can use the Desoto model with CEC parameters, it will give you very similar results.

The Desoto model parameters are:

If you have those values in your locally saved file, then you can create a dict my_module with each of the parameter names as a key (e.g., my_module[I_L_ref] = <value> and then use the dict in your modeling sequence, e.g., PV = PVSystem(…., module_parameters=my_module, ...) etc.

I noticed that our tutorial on the use of pvsystem.py has issues in the Desoto section, so I appreciate your question.

I don't know what you mean by a 'template file for the CEC model'

Finally, we prefer that questions about use of pvlib be asked in the googlegroup or stackexchange forums.

Best,

Cliff

mikofski commented 6 years ago

@Jawairia123 seems like in the future this issue might be better asked at pvlib-python Google group thanks!

Jawairia123 commented 6 years ago

Hi,

I tried using Desoto model with CEC module parameters and it's working. I am looking at system losses at the moment. So issue of working on CEC database is kinda resolved.

I was able to run pvwatts model but there I found this issue that currently the modelchain can't handle (pvwattts modeled) system with multiple modules in series and parallel to an inverter. So that's a drawback.

It doesn't end here. There are quite a lot number of module and inverter models that we can't find in Sandia/CEC databases and how we can implement them directly having only datasheet values is a big gap.

I am still looking to possible solution and suggestions.

Regards Jawairia

cwhanse commented 6 years ago

We prefer questions about use of pvlib to appear at https://groups.google.com/forum/m/#!forum/pvlib-python

Getting to module model parameters from datasheets is not currently supported in pvlib - see my response above. You may want to look at the capability in SAM - see this thread https://sam.nrel.gov/node/69678

Best regards,

Cliff

wholmgren commented 6 years ago

This a combination of usage question and duplicate of other issues, so closing the issue.