Skip to content

Latest commit

 

History

History
64 lines (48 loc) · 3.85 KB

Developers_About_the_Signal_Reference.md

File metadata and controls

64 lines (48 loc) · 3.85 KB

The Open Source Phasor Data Concentrator

Grid Protection Alliance openPDC Project openPDC Wiki Documentation Latest Release

Signal Reference Notes

For synchrophasor measurements the signal reference field is critical - it is used to map device elements in a protocol frame (e.g., IEEE C37.118) to and from measurements. The format of this field is very regular:

The text based signal reference field must contain the Acroynm of the associated Device, followed by a dash (-), followed by the two character SignalType Suffix then optionally followed by an index. Note that the mapping is by order, not by index or name. Thus, it is critical that the indexed measurements be modeled in the order that they are returned from the source device. For example SHELBY-PM4 represents the fourth phasor magnitude for the SHELBY Device and SHELBY-SF represents its status flags.

The information below describes the original specification:


In order to rebroadcast data from the sub-second sources, a field is required to be able to associate each point with its associated "field" in a synchrophasor protocol data frame. This document defines these relations.

This field is normally for internal use only and is stored in a field associated with each defined measurement point:

Type of Point Description Abbreviation Indexed?
Phasor Magnitude Voltage (Volts) or Current (Amps) PM Yes
Phasor Angle Angle (Degrees) PA Yes
Frequency Frequency (Hz) FQ No
dF/dt Frequency rate of change DF No
Digital Value DV Yes
Analog Value AV Yes
Status Flags SF No
Quality Flags QF No

Examples below follow the prescribed format of: the PMU/device acronym, a dash and one of the above abbreviations. Also, if the type of point is indexed, adding the associated entry index, for example:

SHELBY-PM1 Magnitude associated with Phasor1 entry
SHELBY-PA1 Angle associated with Phasor1 entry
SHELBY-PM2 Magnitude associated with Phasor2 entry
SHELBY-PA2 Angle associated with Phasor2 entry
SHELBY-PM3 Magnitude associated with Phasor3 entry
SHELBY-PA3 Angle associated with Phasor3 entry
SHELBY-PM4 Magnitude associated with Phasor4 entry
SHELBY-PA4 Angle associated with Phasor4 entry
SHELBY-PM5 Magnitude associated with Phasor5 entry
SHELBY-PA5 Angle associated with Phasor5 entry
SHELBY-FQ Frequency value associated with Frequency entry
SHELBY-DF Rate of frequency change associated with Frequency entry
SHELBY-DV1 Digital Word Value 1 (16-bits)
SHELBY-DV2 Digital Word Value 2 (16-bits)
SHELBY-AV1 Analog Value 1
SHELBY-AV2 Analog Value 2
SHELBY-SF Status Flags
SHELBY-QF Quality Flags

Using this information you can map individual measurements to and from most any synchrophasor protocol data frame.


Apr 12, 2013 at 5:55:03 PM - Last edited by ritchiecarroll, version 7
Oct 5, 2015 - Migrated from CodePlex by aj


Copyright 2015 Grid Protection Alliance