> 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/power-converters/switching-function-converter-controlled-by-averaged-firing-pulses.md).

# Switching Function Converter Controlled by Averaged Firing Pulses

This example shows the advantages of power electronics converters that can be simulated using one of four selectable modeling techniques

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

## Description

The converter in the circuit 0 is modeled by a switching function controlled by firing pulses produced by a PWM generator operating at 25 microseconds. The circuit 1 also uses a switching function converter and a PWM generator but is sampled at 5 microseconds. The converter in the circuit 2 is modeled by a switching function controlled by firing pulses averaged over a period of 25 microseconds. In this case, the PWM generator is in continuous mode.

## Simulation

Run the simulation and look at the simulation results to observe that good performance is obtained with the use of averaged pulses at higher sample time period, when compared to the performance obtained with regular pulses at lower sampling time.

## Command

Example model name: power\_AveragedPulses

{% code lineNumbers="true" %}

```matlab
open('power_AveragedPulses')
```

{% 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/power-converters/switching-function-converter-controlled-by-averaged-firing-pulses.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.
