> 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/troubleshoot-deployment-errors-using-real-time-target-logs.md).

# Troubleshoot Deployment Errors Using Real Time Target Logs

During system definition deployment, the VeriStand engine collects and records information in a log file saved on the real time target. Real Time Simulator Logs can provide valuable clues about the state of the Power Electronics Add-On in the event of a deployment or run-time error.

## Procedure

These log messages can be viewed directly in the VeriStand editor using the **Target Log Viewer**. :

{% stepper %}
{% step %}

### Open the NI Measurement and Automation Explorer (NI MAX)

In the configuration tree, expand **Remote Systems** and locate your Real Time PXI simulator.
{% endstep %}

{% step %}

### Right-click the simulator and click File Transfer

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FD0x3e6IJq3L7pKqmqb2w%2Fimage.png?alt=media&amp;token=5a3d8df3-445c-4a0c-9b27-88101068dfa6" alt=""><figcaption></figcaption></figure>

This opens the default web browser to navigate the simulator files over FTP.

{% hint style="info" %}
The files on the target can also be accessed using a third-party SSH tool such as PuTTY, MobaXTerm, etc.
{% endhint %}
{% endstep %}

{% step %}

### Open the log file

Navigate to **/c/ni-rt/NIVeriStand/Logs/** and identify the desired log file using the date in the file name: **VeriStand Engine Log \<Date>.txt***.* Open the file to view its contents or copy them to a local text file.

Status messages originating from the Power Electronics Add-On (OPAL-RT Circuit) can be identified by the text **SEA***:* at the start of the line.

<figure><img src="https://2999842053-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe9Kk9pJCHht2LLBSxPap%2Fuploads%2FIXYQSaWDfDdikiyJGYMy%2Fimage.png?alt=media&amp;token=8997a0ac-ed99-4318-8a2e-d1091157ea94" 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/troubleshoot-deployment-errors-using-real-time-target-logs.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.
