> 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/pe-add-on-simulink/simulation-control-monitoring-and-logging/validate-pwm-and-static-digital-input-signals.md).

# Validate PWM and Static Digital Input Signals

When interfacing the test system with external hardware, it is important to confirm that the signals input to the real time target are properly received and interpreted by the simulation software. In the case of a HIL system, we may need to validate both **static digital signals** and **PWM gating signals acquired by the Digital Input channels**.

Follow the procedure below to monitor Digital Input channel data in the Power Electronics Add-On.

{% stepper %}
{% step %}

### On the chassis

Connect digital signals to the digital input channels of the FPGA board. Refer to the documentation for the selected [**Hardware Configuration**](https://www.opal-rt.com/docs/pe-add-on-simulink/hardware-configurations-reference/default-hardware-configurations.md) to confirm the supported digital input voltage range and to associate the physical pins on the card to the Digital Input Channel names in VeriStand.
{% endstep %}

{% step %}

### In the System Definition file

In VeriStand, navigate to **Power Electronics Add-On** >> **Hardware Configuration** >> **FPGA*****X*** >> **Digital Inputs** in the System Definition file.

Under **Digital Input Settings**, select **Enable PWM Measurement Channels.** A folder called **Advanced** will be created under the **Digital Inputs** section of the tree.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2F3ThQhIZELEpUg1GMqnmy%2Fimage.png?alt=media&amp;token=528790a0-124d-4c6d-8d1d-342f3fe9b07f" alt=""><figcaption></figcaption></figure>

Save and close the System Definition File.
{% endstep %}

{% step %}

### In a screen in the VeriStand project

1. Open or create a Screen (.nivsscr) file in the VeriStand project and add numeric indicators to monitor the desired Digital Input channels.
2. To monitor a PWM signal acquired on a Digital Input channel, map a numeric indicator to the corresponding **Duty Cycle** and **Frequency** channels under **Hardware Configuration** >> **FPGA&#x20;*****X*** >> **Digital Inputs** >> **Advanced.**
3. To monitor a static (non-PWM) signal acquired on a Digital Input channel, map a numeric indicator to the appropriate VeriStand channel in the **Digital Inputs** section of the tree (**DI00**, **DI01**, etc.).
4. Deploy the simulation and monitor the signals in the user interface. Verify that the PWM signals are operating at the expected duty cycle and frequency. Static signals will display a 1 when HIGH and a 0 when LOW.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FPxMt1nriSR9kHpZvrhxS%2Fimage.png?alt=media&amp;token=1fe8f775-978b-4530-b42f-edf628c7179a" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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/pe-add-on-simulink/simulation-control-monitoring-and-logging/validate-pwm-and-static-digital-input-signals.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.
