> 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/model-and-simulation/cybersecurity-with-exata-cps/run-an-exata-standalone-simulation.md).

# Run an Exata Standalone Simulation

## Introduction

EXata CPS can be used independently of <code class="expression">space.vars.Software</code> to design, execute, and analyze communication network simulations. Running EXata CPS in standalone mode is useful for validating network behavior, debugging communication scenarios, and investigating protocol performance before integrating the network with a real-time simulation.

## Configure standalone execution in EXata CPS

1. Open the EXata CPS GUI.
2. Select **Run Settings**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-6acde8093dfc90ee6abf5de1ee86ed97474ab8a0%2Fexata-run-settings.png?alt=media" alt="" width="155"><figcaption></figcaption></figure>

3. Under **Execution Mode**, enable **Standalone Execution**.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-a47b86f0017ff6cffefe1b3a0c01868f58bdbcae%2Fexata-standalone-cps8.png?alt=media" alt=""><figcaption></figcaption></figure>

4. Click **OK**.

The workstation is now configured to launch EXata CPS simulations on the OPAL-RT simulator in standalone.

{% hint style="danger" %}
Select **Standalone Execution** only when running EXata CPS independently of <code class="expression">space.vars.Software</code>. **Clear this option before running a cyber-physical co-simulation or HIL co-simulation**.
{% endhint %}


---

# 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/model-and-simulation/cybersecurity-with-exata-cps/run-an-exata-standalone-simulation.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.
