...
I/O interfaces allow defining datapoints that are handled outside the models themselves. In order to bring the data going through those datapoints inside the models, we need to use two specific blocs called https://opal-rt.atlassian.net/l/cp/2wqY1pig and https://opal-rt.atlassian.net/l/cp/1VJbdYhR. OpInput and OpOutput .
...
OpInput
The https://opal-rt.atlassian.net/l/cp/2wqY1pig OpInput block gives the ability to create an input connection within the model. Thus, it may be connected to any output signal coming from any associated I/O interface.
In the case of the OrchestraFramework I/O interface, output signals correspond to any item of the subscribe part of the DDF or the 'status' signal.
OpOutput
The https://opal-rt.atlassian.net/l/cp/1VJbdYhR OpOutput block gives the ability to create an output connection within the model. Thus, it may be connected to any input signal coming out of any associated I/O interface.
...
Performing the connections between the model datapoints delivered by the OpInputs/OpOutputs and the datapoints from the I/O interfaces is explained in the following page https://opal-rt.atlassian.net/l/cp/5muqM3S7 Connections management .