> 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/efpgasim-library/simulink-sps-workflow/static-digital-input.md).

# Static Digital Input

## Description

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Frf6jSz1kE8dreUVNBNJp%2Fimage.png?alt=media&amp;token=ad917d3f-6f80-4ce7-8448-8b5cc30eea2e" alt=""><figcaption></figcaption></figure>

The **Static Digital Input** block, located in the **cpuhilios\_lib** library, implements an 8-channel digital input subsection as either Static digital input, EventDetector input or Pulse-Width Modulated input.

## Mask parameters

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2FOyDj6fFN8V4NleitOHEQ%2Fimage.png?alt=media&amp;token=1689c72b-2c14-4ae5-9000-9951d95a13aa" alt=""><figcaption></figcaption></figure>

| Parameter                                               | Description                                                                                                                                                                                             |
| ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Controller Name**                                     | Bind this block to an OpCtrl block by entering the same 'Controller Name' as specified in the OpCtrl block The OpCtrl block controls initialization of the settings of one specific FPGA in the system. |
| **DataOut port number**                                 | Enter the number of the DataOut port to be controlled by this block, in the range \[1:32].                                                                                                              |
| **LoadIn port number for Digital Input type selection** | Enter the number of the LoadIn port used to communicate the Digital Input type selection for this block, in the range \[1:32].                                                                          |
| **Digital Input type**                                  | Select the Digital Input type from the list. This type can either be "Static Digital Input", "Event Detector" or "Pulse-Width Modulated Input".                                                         |

{% hint style="info" %}
Other parameters will appear depending on the Digital Input type selection. More information on these parameters can be found in the block documentation of either digital input type.
{% endhint %}

## Inputs

**I**nputs of this block are Digital-Input-type dependent. Refer to the block documentation of either digital input type for more information.

## Outputs

Outputs of this block are Digital-Input-type dependent. Refer to the block documentation of either digital input type for more information.

## Characteristics and limitations

| Direct Feedthrough   | NO  |
| -------------------- | --- |
| Discrete sample time | YES |
| XHP support          | YES |
| Work offline         | N/A |


---

# 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/efpgasim-library/simulink-sps-workflow/static-digital-input.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.
