> 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/hypersim/library-blocks-reference/target-inputs-and-outputs/target-output-digital.md).

# Target Output, Digital

## Description

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-421d31550b51b5f31290b6d35ba99b6545f36c6e%2Fimage%20(482).png?alt=media" alt=""><figcaption></figcaption></figure>

The **Digital Target Output** block, located in the **Target Inputs And Outputs** library, outputs predefined events that can be triggered by a ScopeView acquisition. It provides functionality beyond simple signal routing. You can predefine multiple events and apply them to any or all of the four I/O sensor outputs. You can also enable or disable the general operation to vary test cases. When disabled, steady-state conditions apply.

The Task mapping connector links this block to a network task so it computes with that task. Use this to optimize performance when computational load is high.

## Mask parameters

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-007c113512521f70235c5e09bdcbc106d678ffa0%2Fimage%20(483).png?alt=media" alt="" width="477"><figcaption></figcaption></figure>

<table><thead><tr><th width="233.20001220703125" valign="top">Parameter</th><th>Description</th></tr></thead><tbody><tr><td valign="top"><strong>Description</strong></td><td>Free-form field to document the block.</td></tr><tr><td valign="top"><strong>Time units</strong></td><td>Unit used for all timings (s, ms, or cycles).</td></tr><tr><td valign="top"><strong>Operation status</strong></td><td>Enables or disables general operation when a ScopeView acquisition starts.</td></tr><tr><td valign="top"><strong>Steady-state condition</strong></td><td>Initial state for all four signals (ON/OFF).</td></tr><tr><td valign="top"><strong>Base frequency</strong></td><td>Used to calculate timings when the unit is Cycles (Hz)</td></tr><tr><td valign="top"><strong>Enable(1..8)</strong></td><td>Enables or disables specific commands when a ScopeView acquisition starts.</td></tr><tr><td valign="top"><strong>Type (f, i, u)</strong></td><td>Fixed: fixed time of operation at each acquisition; default type when not specified. Syntax: f:time (e.g., f:0.2 or simply 0.2).<br>Incremental: range of times with a fixed increment at each acquisition; resets to the initial time when the maximum is reached. Syntax: i:initial time/final time/time increment (e.g., i:0.1/0.2/0.01).<br>Uniform: random time in a uniform distribution at each acquisition. Syntax: u:minimal time/maximal time (e.g., u:0.1/0.2).</td></tr><tr><td valign="top"><strong>Referenced component</strong></td><td>Links the command operation to a breaker operation time or another digital output component. Specify the <em>component_name</em>. If the component is in a subcircuit, use <em>subcircuit_name.component_name</em>.</td></tr><tr><td valign="top"><strong>Referenced time</strong></td><td>Time (T1, T2, ...) to reference in the referenced component.</td></tr><tr><td valign="top"><strong>DO operated</strong></td><td>Selects the output signals to operate when conditions are met.</td></tr></tbody></table>

## Conserving ports

<table><thead><tr><th width="239.60003662109375">Port</th><th>Description</th></tr></thead><tbody><tr><td><strong>Task mapping</strong></td><td>Connects the block to a network task so it computes with that task.</td></tr></tbody></table>

## Inputs

This block has no inputs.

## Outputs

This block has no outputs.

## Signals available for monitoring and external I/O connections (via sensors form)

All block inputs and outputs are available as signals for monitoring and for external I/O connections.

Additional signals are also available and are listed below with their descriptions.

<table><thead><tr><th width="240.39996337890625">Signal</th><th>Description</th></tr></thead><tbody><tr><td><strong>CMD(01..04)</strong></td><td>All four output events can be monitored.</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/hypersim/library-blocks-reference/target-inputs-and-outputs/target-output-digital.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.
