> 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/hypersim/examples/how-to/cigre-integrator.md).

# CIGRÉ integrator

## Description

The **CIGRÉ Integrator** example, located in **File > Open an Example File > How To**, demonstrates a user-defined block implemented with the IEEE/CIGRÉ DLL Modeling Method V1.1 (February 29, 2024).

The objective is to validate a DLL-based user-defined block against an equivalent transfer function implementation of a forward Euler integrator and to illustrate input synchronization using a point-on-wave feature.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-70f81c140ad3d4230875a7817a393005a2e629cc%2Fimage%20(1015).png?alt=media" alt=""><figcaption></figcaption></figure>

## Requirements

This example model does not require any additional hardware or licenses.

## Detailed explanation

The model contains two blocks that compute a numerical integration using the forward Euler method.

The transfer function used is in the Z-domain:

$$
H(z) = \frac{1}{z - 1}
$$

Given an input signal to the block $$H(t - 1)$$, the output evolves according to the recursive relation:

$$
y\_{t} = y\_{t-1} + \Delta t \times H(t-1)
$$

A CIGRÉ user-defined block implemented as a shared library (.dll), and a second block replicates the same integrator using a transfer function. Both blocks are non-direct feedthrough, as each contains a state.

* **CIGRE\_1.input** signal entering and **CIGRE\_1.output** signal generated by the [CIGRÉ Interface block](https://github.com/Opal-RT-Technologies/product-docs-hypersim/tree/release-2026.4/library-blocks-reference/control-interfaces/cigre-interface_mis_en-attente-doc-2026.md)
* **Hz1.u** signal entering and **Hz1.y** signal generated by the transfer function

A point-on-wave feature is included to synchronize input signals during ScopeView acquisitions.

## Simulation and results

Use the ScopeView template *CIGRE\_Integrator.svt* to review recorded signals. Inputs to both blocks are identical. This enables quick comparisons of all block output values against each other.

All output values (integrated signals) match, confirming that the CIGRÉ user-defined block performs integration consistent with the transfer function implementation.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-70e77c5c165001439c0b16e752c853c45579b7dc%2Fimage%20(1016).png?alt=media" alt=""><figcaption><p>Input values entering each block are identical, and all output values (integrated signals) match</p></figcaption></figure>

## References

The CIGRÉ Integrator source files are available in the demo folder a *CIGRE\_Integrator\references\src.*

{% file src="/files/J0qA2QXvblgXizbJHp7e" %}

<https://www.cigre.org/>


---

# 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/hypersim/examples/how-to/cigre-integrator.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.
