| Table of Contents |
|---|
...
Ideally, the timestamp input should come from an accurate synchronization source. Otherwise, there is no guarantee on the data sampling, reported data rate and fraction of second information.
| Connection point | Direction | Description |
|---|---|---|
| Sync | From model to driver | It is a binary value (0 or 1) that represents the synchronization state of the timestamp. If the timestamp is synchronized with an accurate external source such as a GPS, the value applied to this signal should be 1 and otherwise it should be 0. For GOOSE: This value will appear in each time qualify byte of the data frames to indicate the validity of the timestamp. |
| Epoch | For GOOSE: Represents the number of seconds elapsed since January 1st 1970, commonly known as Unix epoch time. It means that it has to increment at each second. This signal is used to timestamp the outgoing packets. | |
| Microseconds | For GOOSE: Represents the microsecond count within the current second. For SV: This input is not necessary. |
...
Publishers
Connection point | Direction | Description |
|---|---|---|
| Settings / Pause | From model to driver | Controls the transmission of the GOOSE message. An input of 1 suspends transmission and a value of 0 enables it. |
| Settings / stNum | From driver to model | Starting from 0, this value is incremented every time a change occurred to a data set member of the GOOSE message. |
| Settings / sqNum | From driver to model | Starting from 0, this value is incremented for each GOOSE message sent without any modifications to its data set members. |
| Settings / simulation | From model to driver | This input controls the GOOSE header field "test". If the input value is 1 (TRUE), the GOOSE message will be transmitted with the test flag equal to TRUE, informing all subscribers that the Object Input Data is the result of a test. |
| Settings / ndsCom | From model to driver | This input controls the GOOSE header field "needs commissioning". |
| Data | From model to driver | Each attribute found in the data set used by the GOOSE message provides a connection point. Its format represents its full path within the IED: IED / Access point / Logical device / Logical node / Data object / Data attribute |
...
This information applies to both Sampled Values 9-2LE and IEC 61869-9 publishers and subscribers.
Bit | Attribute Name | Meaning of value | Value | Default value |
|---|---|---|---|---|
0-1 | Validity | Good | 0 0 | 0 0 |
| Invalid | 0 1 | |||
| Reserved | 1 0 | |||
| Questionable | 1 1 | |||
| 2 | Overflow | TRUE | FALSE | |
| 3 | Out of range | TRUE | FALSE | |
| 4 | Bad reference | TRUE | FALSE | |
| 5 | Oscillatory | TRUE | FALSE | |
| 6 | Failure | TRUE | FALSE | |
| 7 | Old data | TRUE | FALSE | |
| 8 | Inconsistent | TRUE | FALSE | |
| 9 | Inaccurate | TRUE | FALSE | |
10 | Source | Process | 0 | 0 |
| Substituted | 1 | |||
| 11 | Test | TRUE | FALSE | |
| 12 | Operator blocked | TRUE | FALSE | |
| 13 | Derived | TRUE | FALSE |
...