> 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/rt-lab-i-o-library/tsb-in.md).

# TSB In

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-311245782f920266e72bb1c6c6f208f62aeb1189%2F9028ba7b-fa52-4fe5-94b2-91692b290047.png?alt=media" alt=""><figcaption></figcaption></figure>

The **TSB In** block, located in the **RT-LAB I/O/Opal-RT/Common** library, acquires firing pulse data from a Digital Input module installed in the simulator or expansion unit and provides it to the model. The output value represents the **average ON‑time over the simulation time step**: a value of **`0`** indicates that the signal remained low for the entire time step, a value of **`1`** indicates that the signal remained high for the entire time step, and values between **`0` and `1`** indicate the **fraction of the time step during which the signal was high** (for example, a value of `0.9` means the signal was high for 90% of the time step). The block can also output an **RTE‑compatible signal**, allowing direct connection to the **ARTEMiS TSB** and **RT‑Events TSB** blocks.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-77d67ec3b35c1fcfc4cee939784bd1e7c7590927%2Ff549ba35-8b8a-4a05-93d6-ba653a7a1d6c.jpg?alt=media" alt="" width="448"><figcaption></figcaption></figure>

<table><thead><tr><th width="211">Parameter</th><th>Description</th></tr></thead><tbody><tr><td><strong>Controller Name</strong></td><td>Specifies the <strong>OpCtrl</strong> block this block is bound to. Enter the same <strong>Controller Name</strong> as defined in the corresponding <strong>OpCtrl</strong> block.</td></tr><tr><td><strong>DataOut port number</strong></td><td>Specifies the Digital Input module and subsection from which this block acquires signals. Subsection 1 corresponds to channels 0–7, subsection 2 corresponds to channels 8–15, and so on.<br>Configure the <strong>DataIn port number</strong> according to your <strong>System Description Document</strong> or <code>.conf</code> file. DataOut ports returning TSBIn data are identified by the feature <code>TOM</code>.</td></tr><tr><td><strong>Slot infos</strong></td><td>Read‑only field displaying the expected physical location (Slot, Section, Subsection) of the Digital Input module derived from the selected <strong>DataIn port number</strong>. If the port number is invalid, <em>Slot 0 Module X Subsection 0</em> is displayed.</td></tr><tr><td><strong>Maximum number of TSBIn channels controlled by this block</strong></td><td>Read‑only field displaying the maximum number of channels available in the selected subsection.</td></tr><tr><td><strong>Number of TSBIn channels</strong></td><td>Specifies the size of the block output vector, corresponding to the number of channels returned at each calculation step. The value must be less than or equal to the <strong>Maximum number of TSBIn channels</strong>. Due to the data transfer mechanism, channels cannot be individually selected; the block returns data for the first N channels of the subsection, where <em>N</em> is this parameter.</td></tr><tr><td><strong>Sample Time (s)</strong></td><td><p>Specifies the block sample time, in seconds. A value of <code>0</code> sets a continuous sample time, inherited from the parent subsystem. A value of <code>−1</code> specifies an inherited sample time from the model.</p><p>The functionality block and its associated <strong>OpCtrl</strong> block must execute at the same <strong>sample time</strong>.</p></td></tr><tr><td><strong>Output signal type</strong></td><td>Select the signal type for the <strong>Values</strong> block output: <strong>RTE</strong> (RT-Events signal) or <strong>double</strong>.</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

<table><thead><tr><th width="102">Output</th><th>Description</th></tr></thead><tbody><tr><td><strong>Values</strong></td><td><p>Outputs the processed firing pulse timing data for the selected channel subset. Each output value indicates the state or the relative timing of a state change within the simulation time step: <code>0</code> indicates a low state for the entire time step, <code>1</code> indicates a high state for the entire time step, and <strong>values between <code>0</code> and <code>1</code></strong> indicate the <strong>relative instant within the time step at which a state transition occurs</strong>. The output vector size is determined by the <strong>Number of TSBIn channels</strong> parameter; use a <strong>Demux</strong> block to access individual channel signals.</p><p>When <strong>Output signal type</strong> is set to <strong>RTE</strong>, the output can be connected directly to <strong>ARTEMiS TSB</strong> or <strong>RT‑Events TSB</strong> blocks. When set to <strong>double</strong>, the output is provided as a standard double‑precision signal.</p></td></tr><tr><td><strong>Status</strong></td><td><p>Outputs the block status:</p><ul><li><code>0</code>: No error.</li><li><code>-1</code>: Block not associated with an <strong>OpCtrl</strong> block (check the <strong>Controller Name</strong> parameter), or FPGA initialization failure.</li><li><code>-2</code>: Data reception timeout, typically caused by model synchronization issues.</li><li><code>-3</code>: Data reception error: fewer data received than expected. Missing values are replaced with <code>0</code>.</li><li><code>-4</code>: Data reception error: more data received than expected. Extra values are discarded.</li></ul></td></tr></tbody></table>

## Characteristics and limitations

<table><thead><tr><th width="246.22216796875">Characteristic</th><th>Value</th></tr></thead><tbody><tr><td><strong>Connector pin assignments</strong></td><td>Refer to the <strong>System Description Document</strong> provided with your order, or refer to the pin assignment of the <a href="https://opal-rt-technologies.gitbook.io/opal-rt-technologies-docs/op53xx/"><strong>OP53xx series I/O module</strong></a> associated with each subsection.</td></tr><tr><td><strong>Direct feedthrough</strong></td><td>No</td></tr><tr><td><strong>Discrete sample time</strong></td><td>Yes</td></tr><tr><td><strong>XHP support</strong></td><td>Yes</td></tr><tr><td><strong>Work offline</strong></td><td>No</td></tr><tr><td><strong>Maximum model time step</strong></td><td>160 µs</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/rt-lab-i-o-library/tsb-in.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.
