Skip to main content

OPAL-RT Integration OPAL-RT logo

There are three options to exchange simulation signals with an OPAL-RT real-time simulator:

  1. Orchestra: VILLASnode can act as an Orchestra client. Orchestra is OPAL-RT's co-simulation framework for integrating custom code and external models.

    The functionality is implemented by the opal.orchestra node-type.

    tip

    This node-type is recommended for new setups.

  2. UDP Sockets: Use OPAL-RT's UDP/TCP I/O interfaces. In this mode, OPAL-RT targets will send signals via a UDP socket to VILLASnode. More information about our adapted AsyncIP example can be found here: AsyncIP client.

    This functionality is implemented by the socket node-type.

    caution

    This node-type is not recommended due to limited synchronizations, and limitations in I/O signal management.

  3. Asynchronous Process: VILLASnode can act as an RT-LAB Asynchronous Process. Data exchange is then handled using OPAL-RT's libOpalAsyncApi.

    The functionality is implemented by the opal.async node-type.

    Deprecation

    This node-type is deprecated and not recommended for new setups.