> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/smart-power-simulation-software-sps/example-models/renewables/partial-shading-of-a-pv-module.md).

# Partial Shading of a PV Module

This example shows partial shading of a 250-W PV module consisting of 60 cells connected in series.

<figure><img src="https://799605156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdlNg8IbOdahCpFCyzxSN%2Fuploads%2Fgit-blob-ca0b35d8488612c07b10fc0837af46b6a5b27180%2Fpartialshading_PVmodule_example.png?alt=media" alt=""><figcaption></figcaption></figure>

## Description

The PV module is connected to a variable DC voltage source for measuring its I-V and P-V characteristics. It is modeled as three strings of 20 series-connected cells in parallel with bypass diodes that allow current flow when cells are shaded or damaged. Standard irradiance of 1000 W/m2 is applied on the first string of 20 cells while partial shading is applied on strings 2 (cells 21-40) and string 3 (cells 41-60), resulting in respective irradiances of 300 W/m2 and 600 W/m2.

## Simulation

Simulate the model. The global I-V and P-V characteristics are plotted at the end of simulation. Note that the P-V curve exhibits three maxima. When this PV module is connected to a voltage-sourced converter, this may be challenging for the Maximum Power Point Tracking (MPPT) algorithm to converge on the highest peak. The Global Maximum Power Point (GMPP) (Pm= 104 W) indicated by a red circle on the figure is 34% lower than the expected maximum power (250/3\*(1 +0.3 +0.6) = 158 W).

## Command

Example model name: power\_PVArray\_PartialShading

{% code lineNumbers="true" %}

```matlab
open('power_PVArray_PartialShading')
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/smart-power-simulation-software-sps/example-models/renewables/partial-shading-of-a-pv-module.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
