# RT-LAB and EXata CPS Co-Simulation Starter Example

**URL:** <https://community.opal-rt.com/t/rt-lab-and-exata-cps-co-simulation-starter-example/95>\
**Category:** Models\
**Tags:** rt-lab, model, cyber-physical, exata, cybersecurity\
**Created:** [July 15, 2026, 1:00pm UTC](https://community.opal-rt.com/t/rt-lab-and-exata-cps-co-simulation-starter-example/95 "2026-07-15T13:00:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![DK\_19](https://avatars.discourse-cdn.com/v4/letter/d/c77e96/32.png) [@DK\_19](https://community.opal-rt.com/u/DK_19)\
**Post date:** [July 15, 2026, 1:00pm UTC](https://community.opal-rt.com/t/rt-lab-and-exata-cps-co-simulation-starter-example/95/1 "2026-07-15T13:00:00Z")

</div>

## Overview

A cyber-physical co-simulation workflow for combining RT-LAB electrical models with communication-network behavior through EXata CPS.

This model category is designed for users who need to study the impact of communication networks on electrical system behavior. It combines RT-LAB with EXata CPS to create a more realistic cyber-physical validation environment.

As power systems become more digital, cybersecurity and communication effects need to be tested alongside electrical behavior. Including this model in the first 10 makes the RT-LAB community feel more advanced and more differentiated than a standard demo library.

## Key Features

- Studying communication-network effects on real-time simulation behavior
- Testing network delay, interface mapping, and protocol interaction concepts
- Supporting research into digital substations, SCADA, and cyber-physical resilience
- Creating a bridge between power-system simulation and communication emulation

## Getting Started

1. Compile the RT-LAB model with the required communication interface.
2. Generate the EXata configuration files and target-side setup script.
3. Map the ports and validate data exchange.
4. Run a simple network-impact scenario and monitor end-to-end system behavior.

## Model Specifications

| Parameter | Value |
| --- | --- |
| Product | RT-LAB |
| Software version | RT-LAB 2024.4+ |
| Model file | Coming soon |

_Detailed specifications (time step, hardware, dependencies, license, known limitations, compatible hardware) to be confirmed._

## Downloads

_The downloadable model package is coming soon._

[Cyber\_Physical.zip](https://community.opal-rt.com/uploads/short-url/iTOuqC7ZKwpzjVhS5TJxRTvZZRw.zip) (3.9 MB)

 ![8. Exata Rt-lab](https://canada1.discourse-cdn.com/flex012/uploads/sps/original/1X/d4fe7dabe419c3a25a06a9596975996a2c4ccabe.png)

---

<div class="post-metadata">

**Author:** ![Parija](https://yyz2.discourse-cdn.com/flex012/user_avatar/community.opal-rt.com/parija/32/161_2.png) [@Parija](https://community.opal-rt.com/u/Parija)\
**Post date:** [July 15, 2026, 1:00pm UTC](https://community.opal-rt.com/t/rt-lab-and-exata-cps-co-simulation-starter-example/95/2 "2026-07-15T13:00:00Z")

</div>

Have you ever found a control or protection issue that only appeared once communication behavior was added to the test setup?