> 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/configure-ios/time-synchronization-driver/oregano-time-synchronization-example.md).

# Oregano Time Synchronization Example

## Description <a href="#description" id="description"></a>

The **Oregano** example can be created by starting a new RT‑LAB project. From the menu bar, select **File > New > RT‑LAB Project**. Enter a name and location for your project, then click **Next**. From the available templates list, navigate to **IO > Oregano** and select **Oregano\_syn1588**, then click **Finish**. This example project demonstrates how to use the OPAL‑RT **synchronization** driver to retrieve timing information (such as epoch time) from the synchronization hardware and display it in the RT‑LAB console.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-a2a17ec67f33584d4a29a726717c967e3558626f%2FDR-rtlab-oregano-ex.png?alt=media" alt="" width="383"><figcaption></figcaption></figure>

## Requirements <a href="#requirements" id="requirements"></a>

The general requirements stated in the Time synchronization driver **Requirements, Features & Limitations** section apply.

The example can be executed **with or without an external time source**, depending on the application needs. If an external time source is used, ensure that the hardware is connected as described in the **Connect the Hardware** section.

## Detailed explanation <a href="#detailedexplanation" id="detailedexplanation"></a>

This example illustrates the setup, configuration, and operation steps required to relay time information to the model. This example can be run **with or without an external time source**, depending on the application requirements.

### Model preparation and configuration <a href="#modelpreparationandconfiguration" id="modelpreparationandconfiguration"></a>

1. Review and adjust the Synchronization interface parameters as required.
2. Build the Oregano\_syn1588 model.
3. Load and execute the model.

## Simulation and results <a href="#simulationandresults" id="simulationandresults"></a>

Once the Synchronization interface is configured and the model is compiled, loaded, and running on the simulator, the received timing values can be observed in the **Console subsystem**. These values confirm that the Synchronization interface is correctly configured and that timing data is being successfully delivered to the model.

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


---

# 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/configure-ios/time-synchronization-driver/oregano-time-synchronization-example.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.
