Documentation Home Page HYPERSIM Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.

C37.118 Master | Connections

Once configured, the C37.118 master I/O interface offers different data points to be connected with the model.

The following data points can be connected to the model to provide the timestamp and additional information about the state of the synchronization:

Connection PointDirectionDescription
PhasorsFrom driver to model

For a given stream, each configured phasor will provide two connection points that will return data to the model.

  • If the stream is configured in polar mode, connections points will be provided for the magnitude and the angle (in radians).
  • If the stream is configured in rectangular mode, the connection points will be provided for the real and imaginary parts.

The name of the connection point will contain the device name, and the configured phasor name.

AnalogsFrom driver to model

For a given stream, each configured analog value will provide two connection point that will return data to the model.
The first one is the analog value itself, and the second one is the factor to be applied to this value. Since the standard does not specify how to handle factors for analog values, it is the user responsibility to either multiply or divide the analog value by the factor value returned to the model.
The name of the connection point will contain the device name, and the configured analog point name.

DigitalsFrom driver to model

For a given stream, each configured digital value will provide 16 connection points that will return each bit of the 16-bit digital value to the model.
The name of the connection point will contain the device name, the configured digital point name and the specific bit name.

Normal state status wordFrom driver to modelFor a given digital value, normal status word of the current digital signal. The name of the connection point will contain the digital point name. Only available when ‘Enable reception of normal bit states’.
Frequency ROCFrom driver to modelRate of change of frequency sent by the PMU as per IEEE Std C37.118.2-2011 Section 4.3
FrequencyFrom driver to modelFrequency sent by the PMU as per IEEE Std C37.118.2-2011 Section 6.2.2.
Epoch time (sec)From driver to modelEpoch time sent by the PMU as per IEEE Std C37.118.2-2011 Section 6.2.2.
Fraction of second (ns)From driver to modelFraction of second sent by the PMU as per IEEE Std C37.118.2-2011 Section 6.2.2.
Clock lockedFrom driver to modelTime quality as per IEEE Std C37.118.2-2011 Section 6.2.2.
TimebaseFrom model to driverResolution of fraction of second timestamp as per IEEE Std C37.118.2-2011 Section 6.4.


Some connection points can be used to monitor the status of the C37.118 master driver.

Connection PointDirectionDescription
StatusFrom driver to model

0 = Connected
1 = Disconnected
2 = Receiving
3 = Error

ErrorFrom driver to model

0 = No error
1 = PMU unreachable
2 = Communication timeout
3 = Received PMU ID different than expected

MismatchFrom driver to mode0 = No mismatch between the remote PMU and the PMU configured in the master
1 = There is a data mismatch between the remote PMU and the PMU configured in the master



Some connection points can be used to monitor the statistic word sent by the PMU. See Table 6, section 6.3 of IEEE Std C37.118.2-2011:

Connection PointDirectionDescription
Data errorFrom driver to model

00 = good measurement data, no errors
01 = PMU error. No information about data
10 = PMU in test mode (do not use values) or absent data tags have been inserted (do not use values)
11 = PMU error (do not use values)

In syncFrom driver to modelPMU sync, 0 when in sync with a UTC traceable time source.
Data sortingFrom driver to model0 by time stamp, 1 by arrival.
Configuration changeFrom driver to modelSet to 1 for 1 min to advise configuration will change, and clear to 0 when change effected.
Data modifiedFrom driver to model1 if data modified by post processing, 0 otherwise
Time qualityFrom driver to modelSee Table 7, section 6.3.1 of IEEE Std C37.118.2-2011.
Unlocked timeFrom driver to model

00 = sync locked or unlocked < 10 s (best quality)
01 = 10 s ≤ unlocked time < 100 s
10 = 100 s < unlock time ≤ 1000 s
11 = unlocked time > 1000 s

Trigger reasonFrom driver to model

1111–1000: Available for user definition
0111: Digital
0110: Reserved
0101: df/dt High
0100: Frequency high or low
0011: Phase angle diff
0010: Magnitude high
0001: Magnitude low
0000: Manual


Finally, there is only one connection point that can be used to send data from the model to the driver:

Connection PointDirectionDescription
Enable reception of dataFrom model to driver

This connection point is only available when the ‘Enable automatic data request’ is disabled. At the beginning of the simulation, the C37.118 master driver will ask and receive the PMU configuration, but will not ask to begin the data transfer.
From the model, when the value associated to this connection point will change from 0 to 1, the C37.118 master will send a command to the PMU to start transmitting data. If this value change from 1 to 0, the C37.118 master will send a command to the PMU to stop data transmission.


Here is an example of how sensors can be configured to return C37.118 master information to the model.


Please note that unused columns have been collapsed.

OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | opal-rt.com | +1 514-935-2323
Follow OPAL-RT: LinkedIn | Facebook | YouTube | X/Twitter