> 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/rt-lab/simulink-blocks-reference/mmc-library/deadtime.md).

# Deadtime

## Description <a href="#description" id="description"></a>

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

The **Deadtime** block, located in the **MMC/Control blocks** library, applies a programmable dead time that is a multiple or fraction of the simulation time step **Ts**. The dead time can be provided through an external input port or set as an internal parameter. When the **DeadTime** option is checked, the block uses the external input; otherwise, it uses the internal parameter value.

## Mask parameters <a href="#maskparameters" id="maskparameters"></a>

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-4f8b0dd8b277ae3c1c3687b1e773e862016828d3%2FMMC_deadtime_mask.png?alt=media" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="246.727294921875">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>DeadTime(Check to enable external port / Uncheck for internal)</strong></td><td><p>Enables or disables external control of the dead time.</p><p><strong>Checked:</strong> Dead time is provided by a block's <strong>input</strong>.</p><p><strong>Unchecked:</strong> The block uses an <strong>internal calculation</strong> based on the <strong>Dead Time</strong>… parameter.</p></td></tr><tr><td><strong>Dead Time (Multiple of positive integer/fraction of time-step, Ts)</strong></td><td><p>Scalar value that specifies the dead time in multiples of the time step <strong>Ts</strong>.<br>Examples:</p><ul><li>if set to 1, then Dead Time = Ts</li><li>if set to 2.5, then Dead Time = 2.5*Ts</li></ul></td></tr></tbody></table>

## Inputs <a href="#inputs" id="inputs"></a>

<table><thead><tr><th width="154">Input</th><th>Description</th></tr></thead><tbody><tr><td><strong>Sin</strong></td><td>Signal to which the deadtime will be applied.</td></tr><tr><td><strong>Dead Time</strong></td><td>Positive real number expressing the desired dead time as a multiple/fraction of the time step <strong>Ts</strong><em>.</em></td></tr></tbody></table>

## Outputs <a href="#carriersignalgenerationblock-outputs" id="carriersignalgenerationblock-outputs"></a>

<table><thead><tr><th width="164">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Sout</strong></td><td>Input signal delayed by the specified dead time.</td></tr></tbody></table>


---

# 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/rt-lab/simulink-blocks-reference/mmc-library/deadtime.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.
