> 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/watkins-johnson-converter.md).

# Watkins-Johnson Converter

This example shows the operation of a Watkins-Johnson (WJ) converter.

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

## Description

The Watkins-Johnson (WJ) converter employs a tapped-inductor giving an extra degree of freedom compared to the classical buck converter. The theoretical transfer function of the WJ converter is:

$$
V\_{out}/V\_{in} = D - K/D \times (1-K)
$$

where D is the duty cycle and K = N1/(N1+N2) is the turns ratio of the tapped inductor.

{% hint style="info" %}
Note: The above equation is valid in continuous conduction mode only.
{% endhint %}

For a given conversion ratio, the WJ converter has the advantage of employing a larger duty cycle than the traditional buck converter.

In this example, the tapped inductor is built using the SPS mutual inductance. By double-clicking on the Tapped Inductor block, you can specify the value in henrys and the turns ratio of the tapped inductor.

## Simulation

Run the simulation and observe waveforms on the Scope. The mean value of the load voltage (V<sub>out</sub>) should be very close to the theoretical value:

$$
V\_{out} = 24 \times (0.857-0.75) /(0.855\times (1-0.75) ) = 12.01 V
$$

## Command

Example model name: power\_WatkinsJohnsonConverter

{% code lineNumbers="true" %}

```matlab
open('power_WatkinsJohnsonConverter')
```

{% 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/watkins-johnson-converter.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.
