> 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/simulation-control-monitoring-and-logging/log-simulation-data-with-datalogger.md).

# Log Simulation Data with DataLogger

## **Introduction** <a href="#introductiontothedatalogger" id="introductiontothedatalogger"></a>

The **DataLogger** is a powerful tool for simulation data acquisition, allowing users to capture signals during or after simulation for design validation, record multiple signals across one or more models, and export data in MAT (MATLAB), CSV (Excel), or OPREC formats.

It supports both triggered and non-triggered acquisition modes while maintaining minimal impact on real-time simulation performance. Signals can be captured at any point during the simulation, including from the very first calculation steps, ensuring that no important events are missed.

The system allows multiple signals to be logged within a single model as well as across multi-model simulation setups. It also supports multiple signal groups, each of which can operate at different acquisition rates based on ratios of the simulation step, providing flexibility in data collection.

Log file configuration is fully customizable. Users can define parameters such as file size, naming conventions, and logging duration (for example, in seconds, minutes, or hours). The naming structure is designed to be clear and informative, incorporating model tags, subsystem identifiers, and timestamps to simplify data management.

In addition, the recorded data is enriched with detailed metadata, including signal names, units, scaling, aliases, and trigger settings. This improves traceability and makes the data easier to interpret and reuse.

Finally, configurable trigger mechanisms make it possible to detect and capture transient events and anomalies. This enables more thorough analysis and helps ensure that critical behaviors are accurately recorded.

{% hint style="danger" %}
**Known Limitations:**

* Occasional freezes may occur with **large signal sets**.
* **Partial vectors cannot be logged**.
* **MAT export is limited**; use **CSV** or **OPREC** formats for MATLAB processing.
  {% endhint %}

## **Requirements**

To use the DataLogger, the model must be **built and loadable**. This ensures that all signals can be detected, grouped, and logged according to the configured acquisition settings.

{% hint style="info" %}
The DataLogger is the engine that powers the **Recorders** section in RT-LAB. When you build a model, DataLogger automatically creates a recorder for that model, allowing you to configure signal groups, triggers, and logging parameters. While the UI shows **Recorders**, all data acquisition and logging functionality is managed by the **DataLogger**.
{% 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/simulation-control-monitoring-and-logging/log-simulation-data-with-datalogger.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.
