substationSBG

This is the release version of the substationSBG Version 1.0.126 - 03/06/2015 Updates and fixes since version 1.0.66 Improved alarm configuration and monitoring screens to provide better usability and feedback. New “CountOnlyMappedMeasurements” ... [More] configuration setting for synchrophasor inputs that will only count measurements that are enabled so that disabled measurements that are not received will not count against expected measurements and skew daily report numbers. An optional logging path for data gap recovery operations so that clustered implementations can use DFS replication to maintain runtime and outage log synchronization for subscriptions with automatic data recovery enabled. Support for GEP sessions using ZeroMQ. Message throttling in the 1.0 Historian for data with bad timestamps. Optimized AF-SDK based OSI-PI adapter to always insert given point IDs from the same thread (can make older PI instances happier) - this also includes a minor improvement in connection handling. Updated measurement metadata UI to do a full reload config to make sure changes are fully propagated to output adapters, e.g., flowing any updates to OSI-PI for metadata sync. New "TagNamePrefixRemoveCount" configuration setting to the OSI-PI adapter to remove desired levels of tag name prefixes (like those acquired from a subscription, e.g., "SOURCE!") from PI tag names when performing automated metadata synchronization. Issue where leaving openPDC Manager running on the home screen and connected to the openPDC service would keep allocated pinned buffers manifesting as a slow memory leak. Occurred due to use of the .NET FileSystemWatcher as a class member and parent class would not get a dispose call. In this case backup finalizer would not get called since watcher maintains a dangling reference to parent class via its internal pinned buffer. This can occur even with a properly implemented IDisposable pattern. Implemented and globally applied a SafeFileWatcher wrapper that uses weak references to correct. Removed reusable memory streams in GEP engine to allow system to properly reclaim memory resources after periods of stress. Issue where OSI-PI adapter would not properly rename existing points under some conditions. Was due to fallback tag lookup procedure not properly finding associated measurement by signal ID stored in the exdesc attribute. Issue where OSI-PI points keep updating after openPDC measurements have been removed. Exception while adding new phasors to input devices via the Manager. Updated phasor UI to check for duplicate source indexes when adding phasors manually. Confusing message in synchrophasor parser when receiving an exception related to data received on the command channel. Error messages in the DataPublisher’s UpdateCertificateChecker during reconfiguration due to null subscriber identities. Issue in GSF.StringExtensions.ParseKeyValuePairs where certain character encodings would be decoded automatically by the parser. Adding Macrodyne Controller config file to setup package to prevent error message at startup. Issue where the TLS remoting server never properly disconnected unauthenticated clients. Cleared the wait handle upon completion of any successful send operations in the TlsServer. Updated the status of the TlsServer to include client send queue sizes so resource utilization can be better monitored. Fixed the SubscriberStatusQuery, used on the external subscription monitoring UI screen, to properly query the TLS!DATAPUBLISHER rather than the EXTERNAL!DATAPUBLISHER. Version 1.0.66 - 03/06/2015 Use with the openPDC v2.1 for fully automated data gap recovery mode.Default substationSBG Network Port Usage Follows: substationSBG listens on TCP 6180 for the gateway data exchange protocol, the central openPDC will connect to each substationSBG on this port. substationSBG listens on TCP 8515 for the remote console utility, however, if the console is only used locally this will not need a firewall rule. Note that other firewall ports may need to be opened between substationSBG and other substation devices (e.g., local PMUs). Normally the substationSBG will be the source for these types of connections. Connections are typically TCP based. Windows environment elements (e.g., DFS Replication) may require additional firewall ports to be opened. [Less]

This is the release version of the substationSBG Version 1.0.126 - 03/06/2015 Updates and fixes since version 1.0.66 Improved alarm configuration and monitoring screens to provide better usability and feedback. New “CountOnlyMappedMeasurements” ... [More] configuration setting for synchrophasor inputs that will only count measurements that are enabled so that disabled measurements that are not received will not count against expected measurements and skew daily report numbers. An optional logging path for data gap recovery operations so that clustered implementations can use DFS replication to maintain runtime and outage log synchronization for subscriptions with automatic data recovery enabled. Support for GEP sessions using ZeroMQ. Message throttling in the 1.0 Historian for data with bad timestamps. Optimized AF-SDK based OSI-PI adapter to always insert given point IDs from the same thread (can make older PI instances happier) - this also includes a minor improvement in connection handling. Updated measurement metadata UI to do a full reload config to make sure changes are fully propagated to output adapters, e.g., flowing any updates to OSI-PI for metadata sync. New "TagNamePrefixRemoveCount" configuration setting to the OSI-PI adapter to remove desired levels of tag name prefixes (like those acquired from a subscription, e.g., "SOURCE!") from PI tag names when performing automated metadata synchronization. Issue where leaving openPDC Manager running on the home screen and connected to the openPDC service would keep allocated pinned buffers manifesting as a slow memory leak. Occurred due to use of the .NET FileSystemWatcher as a class member and parent class would not get a dispose call. In this case backup finalizer would not get called since watcher maintains a dangling reference to parent class via its internal pinned buffer. This can occur even with a properly implemented IDisposable pattern. Implemented and globally applied a SafeFileWatcher wrapper that uses weak references to correct. Removed reusable memory streams in GEP engine to allow system to properly reclaim memory resources after periods of stress. Issue where OSI-PI adapter would not properly rename existing points under some conditions. Was due to fallback tag lookup procedure not properly finding associated measurement by signal ID stored in the exdesc attribute. Issue where OSI-PI points keep updating after openPDC measurements have been removed. Exception while adding new phasors to input devices via the Manager. Updated phasor UI to check for duplicate source indexes when adding phasors manually. Confusing message in synchrophasor parser when receiving an exception related to data received on the command channel. Error messages in the DataPublisher’s UpdateCertificateChecker during reconfiguration due to null subscriber identities. Issue in GSF.StringExtensions.ParseKeyValuePairs where certain character encodings would be decoded automatically by the parser. Adding Macrodyne Controller config file to setup package to prevent error message at startup. Issue where the TLS remoting server never properly disconnected unauthenticated clients. Cleared the wait handle upon completion of any successful send operations in the TlsServer. Updated the status of the TlsServer to include client send queue sizes so resource utilization can be better monitored. Fixed the SubscriberStatusQuery, used on the external subscription monitoring UI screen, to properly query the TLS!DATAPUBLISHER rather than the EXTERNAL!DATAPUBLISHER. Version 1.0.66 - 03/06/2015 Use with the openPDC v2.1 for fully automated data gap recovery mode. Default substationSBG Network Port Usage Follows: substationSBG listens on TCP 6180 for the gateway data exchange protocol, the central openPDC will connect to each substationSBG on this port. substationSBG listens on TCP 8515 for the remote console utility, however, if the console is only used locally this will not need a firewall rule. Note that other firewall ports may need to be opened between substationSBG and other substation devices (e.g., local PMUs). Normally the substationSBG will be the source for these types of connections. Connections are typically TCP based. Windows environment elements (e.g., DFS Replication) may require additional firewall ports to be opened. [Less]

Important Note Source code for this project has been migrated to GitHub: https://github.com/GridProtectionAlliance/substationSBG All new source code and product releases will be posted there.   Project Description The substationSBG ... [More] administered by the Grid Protection Alliance (GPA) couples the high-performance phasor data processing features of the openPDC and the security features of SIEGate into a purpose-built system that is both a substation PDC and a gateway for the secure, reliable communication of synchrophasor data from a substation to the control center. It acts as a synchrophasor data gateway in that it can securely and efficiently gather and redistribute high-resolution (e.g., 60 sample-per-second) time-series data from multiple devices and move real-time data in a consolidated stream to a central location, e.g., as upstream openPDC, and also keep a central data repository complete by providing automated data recovery capabilities using its short-term rolling local archive. Be sure to check out our new video on Data Gap Recovery. The Gateway Exchange Protocol The substationSBG uses the highly efficient Gateway Exchange Protocol (GEP) to move data among interested parties (all standard synchrophasor protocols are also supported as needed). This protocol has been optimized to minimize bandwidth as the gateway flexibly implements publish-subscribe with individual phasor measurement point granularity. See: The GEP Protocol.pdf [Less]

Important Note Source code for this project has been migrated to GitHub: https://github.com/GridProtectionAlliance/substationSBG All new source code and product releases will be posted there.   Project Description The substationSBG administered by ... [More] the Grid Protection Alliance (GPA) couples the high-performance phasor data processing features of the openPDC and the security features of SIEGate into a purpose-built system that is both a substation PDC and a gateway for the secure, reliable communication of synchrophasor data from a substation to the control center. It acts as a synchrophasor data gateway in that it can securely and efficiently gather and redistribute high-resolution (e.g., 60 sample-per-second) time-series data from multiple devices and move real-time data in a consolidated stream to a central location, e.g., as upstream openPDC, and also keep a central data repository complete by providing automated data recovery capabilities using its short-term rolling local archive. Be sure to check out our new video on Data Gap Recovery. The Gateway Exchange Protocol The substationSBG uses the highly efficient Gateway Exchange Protocol (GEP) to move data among interested parties (all standard synchrophasor protocols are also supported as needed). This protocol has been optimized to minimize bandwidth as the gateway flexibly implements publish-subscribe with individual phasor measurement point granularity. See: The GEP Protocol.pdf [Less]

substationSBG: Version change for build substationSBG_v1.0.132.0.

substationSBG: Version change for build substationSBG_v1.0.132.0.

Synchrophasor-VS2012: Updated grid solutions framework tool: DNP3ConfigGenerator.

Synchrophasor-VS2012: Updated grid solutions framework tool: DNP3ConfigGenerator.

Updated grid solutions framework tool: NoInetFixUtil.

Updated grid solutions framework tool: NoInetFixUtil.