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 Point | Direction | Description |
|---|---|---|
| Phasors | From driver to model | For a given stream, each configured phasor will provide two connection points that will return data to the model. |
| Analogs | From driver to model | For a given stream, each configured analog value will provide two connection point that will return data to the model. |
| Digitals | From 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. |
| Normal state status word | From driver to model | For 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 ROC | From driver to model | Rate of change of frequency sent by the PMU as per IEEE Std C37.118.2-2011 Section 4.3 |
| Frequency | From driver to model | Frequency sent by the PMU as per IEEE Std C37.118.2-2011 Section 6.2.2. |
| Epoch time (sec) | From driver to model | Epoch time sent by the PMU as per IEEE Std C37.118.2-2011 Section 6.2.2. |
| Fraction of second (ns) | From driver to model | Fraction of second sent by the PMU as per IEEE Std C37.118.2-2011 Section 6.2.2. |
| Clock locked | From driver to model | Time quality as per IEEE Std C37.118.2-2011 Section 6.2.2. |
| Timebase | From model to driver | Resolution 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 Point | Direction | Description |
|---|---|---|
| Status | From driver to model | 0 = Connected |
| Error | From driver to model | 0 = No error |
| Mismatch | From driver to mode | 0 = 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 Point | Direction | Description |
|---|---|---|
| Data error | From driver to model | 00 = good measurement data, no errors |
| In sync | From driver to model | PMU sync, 0 when in sync with a UTC traceable time source. |
| Data sorting | From driver to model | 0 by time stamp, 1 by arrival. |
| Configuration change | From driver to model | Set to 1 for 1 min to advise configuration will change, and clear to 0 when change effected. |
| Data modified | From driver to model | 1 if data modified by post processing, 0 otherwise |
| Time quality | From driver to model | See Table 7, section 6.3.1 of IEEE Std C37.118.2-2011. |
| Unlocked time | From driver to model | 00 = sync locked or unlocked < 10 s (best quality) |
| Trigger reason | From driver to model | 1111–1000: Available for user definition |
Finally, there is only one connection point that can be used to send data from the model to the driver:
| Connection Point | Direction | Description |
|---|---|---|
| Enable reception of data | From 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. |
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.