Skip to content

Releases: GridProtectionAlliance/pdqtracker

PDQTracker v1.5

15 May 16:47
8b90458
Compare
Choose a tag to compare

This is the official release for PDQTracker v1.5

This is version 1.5.2 of the PDQTracker, released on May 15, 2021

NOTE: If you are upgrading from a prior version of the PDQTracker, you must migrate your existing configuration to use the latest database schema when the Configuration Setup Utility is run after the installation completes - this version includes schema updates.

PMU Connection Tester is installed separately, if needed:
https://github.com/GridProtectionAlliance/PMUConnectionTester/releases

Major Updates:

  • Added full support for IEEE C37.118 Std2011 optional Configuration Frame 3
  • Added tag removal options for OSIsoft PI adapter metadata synchronizations
  • Improved phase guess operations for synchrophasor device wizard
  • Updated DNP3 adapters to latest OpenDNP3 code base with SSL support
  • Added "SystemName" for system level deployment level identification provided at install time
  • Added SNMP reporting for system statistics
  • Improved operation with PostgeSQL schema
  • New system level statistics

Notable Updates to PDQTracker for version 1.5

  • Added auto-sync ability for service / manager database configuration mismatch.
  • Added code to correct any non-unique SQL Server Device unique IDs before database migration
  • Added new dependent DLLs to installer for updated PostgreSQL database assembly
  • Fixed installer deployment names for Npgsql dependencies
  • Fixed PostgreSQL operation for assigning existing database
  • Updated all database connection tests and failure messages to be consistent
  • Updated installer to add Utilities folder with CLI shortcuts / also now remembers last install path.
  • Updated installer to retrieve last service account during installation.
  • Updated Postgres assembly version to use 4.0.11

See full release notes since last release.

PDQTracker v1.4

08 May 02:11
80443e2
Compare
Choose a tag to compare

Official stable release of version 1.4 of the PDQTracker (v1.4.4).

NOTE: if you are upgrading from a prior version of the PDQTracker, you must migrate your existing configuration to use the latest database schema when the Configuration Setup Utility is run after the installation completes - this version includes schema updates.

See full release notes since last release.

Note: PMU Connection Tester is installed separately:
https://github.com/GridProtectionAlliance/PMUConnectionTester/releases

New Updates and Improvements

  • This version includes the BETA version of STTP: https://github.com/sttp
  • Added Modbus Protocol to SQL scripts.
  • Fixed up protocols in initial data set scripts.
  • Fixed race condition between HandleConnectOnDemandAdapters and adapter initialization.
  • Fix DataPublisher subscribe requests to propagate input measurement changes to the routing tables.
  • Fixed event wiring in AllAdaptersCollection.
  • Fixed casing on protocol definition for DNP3.
  • Fixed protocol ID of the test device in the sample data set.
  • Fixed NULL comparisons in SQL trigger for tracking changes to Device records.
  • Updated the schema version of the databases to reflect the change to the device update trigger.
  • Modified order of operations in DataPublisher.HandleSubscribeRequest to fix the issue of subscribers not receiving cached measurements upon subscription.
  • Added ManageCertificate command to ServiceHostBase.
  • Updated SerializedSchema.bin using refactored Schema class.
  • Added code to detach from the StatisticsEngine.Calculated event in DataSubscriber.cs.
  • Fixed parameter parsing for PublishInterval in unsynchronized data subscriber
  • Added ping console command to servicehostbase.
  • Updated ping command to split server setting to remove the port.
  • Added code to handle connect on demand scenarios for DataSubscriber.
  • Fixed temporal support in DataSubscriber.
  • Updated gateway style statistics to fall-back on reflection in source object in case properties are available.
  • Modified the sentinel value of objects derived from the AnalogValueBase and DigitalValueBase classes.
  • Added validation to the routine that updates the connection string after the user updates a connection string parameter.
  • Fixed design-time errors in PagedViewModelBase.
  • Updated the status flag reference in the RealTimeMeasurementUserControl to match the status flag reference in InputStatusMonitorUserControl.
  • Added IEEE C37.118.2 tab to the status flag reference.
  • Fixed input wizard to apply the selected PDC vendor device ID to the concentrator on save.
  • Added validation for the chart refresh interval to ensure that the Manger doesn't crash when the value is misconfigured.
  • Fixed Latitude and Longitude fields so that trailing zeros don't cause validation errors on the Device page.
  • Added line-to-line option under Phase to the Manage Phasor page of the Manager.
  • Fixed up startup operation that fills in missing protocols.
  • Removed stats from device outputs - although statistics may be associated with device, it will not be the adapter producing them...
  • Added more messaging around ToogleBadData testing function and restricted command to admins and editors.
  • Updated automated output measurement creation for power calculations to use HistorianID from associated voltage.
  • Updated default lag-time of PowerMultiCalculatorAdapter to 5 seconds.
  • Fixed the metadata import adapter to use the parent acronym when using source prefix to name child devices.

PDQTracker v1.3

01 Jun 17:15
Compare
Choose a tag to compare

Official stable release of version 1.3 of the PDQTracker (v1.3.5).

NOTE: if you are upgrading from a prior version of the PDQTracker, you must migrate your existing configuration to use the latest database schema when the Configuration Setup Utility is run after the installation completes - this version includes schema updates.

See full release notes since last release.

Note: the PMU Connection Tester is no longer automatically included with the installer package and will need to be installed separately:

https://github.com/GridProtectionAlliance/PMUConnectionTester/releases

New Features and Improvements

  • Added CSV source data export and e-mail options to daily quality reporting
  • Fully overhauled system security
  • Added eDNA historian adapters
  • Added ability to control TCP Nagle algorithm through configuration and applied better defaults when applicable
  • Added quiet / resume console commands, with q and r alias shortcuts, to reduce noise during interaction
  • Improved sub-second time handling
  • Improved startup time of applications without Internet access by allowing disabling of generate publisher evidence in the NoInetFixUtil
  • Improved sub-second time handling
  • Added new GSF time-series Filter Adapters and management screen
  • Added new Grafana functions and capabilities (see full list)
  • Better pre-compilation options of Razor web pages at service start
  • Added "useSourcePrefixNames" boolean connection string parameter to DataSubscriber to allow override ability on subscription prefixes applied to devices names
  • Included new GSF adapter to allow selection of a "best" value based on configuration options
  • Modified the latest values cache in DynamicCalculator to be fed by the concentration engine to resolve usability issues
  • Fixed memory leak in MultiProtocolFrameParser when replay start time and stop time is specified
  • Fixed logic error in AverageFrequency calculator when reporting unreasonable results as NaN
  • Fixed SQL syntax for updated Phasor synchronization in DataSubscriber
  • Updated LDAP security provider to allow UserData.IsDefined to be assumed to be true if no cached user can be found to allow authentication to be attempted
  • Added a safety check around target cache acquisition for cases where cache may have been disposed
  • Handled edge case in SIDToAccountName to resolve errors with null input
  • Removed references and dependencies on to Thread.CurrentPrincipal throughout system as part of security overhaul

PDQTracker v1.2.111

11 Oct 19:43
Compare
Choose a tag to compare

Official stable release of version 1.2 of the PDQTracker (v1.2.111).

GSF changes

See full change log since last release.

Important Fixes

  • Fixed issue with adding / updating IEEE C37.118 frame
  • Upgraded the way security works

PDQTracker v1.2.95

08 Sep 15:17
Compare
Choose a tag to compare

Official stable release of version 1.2 of the PDQTracker (v1.2.95).

See full change log since last release.

Important Fixes

  • Fixed long delay in CSU when attempting to fix the node table format.
  • Fixed errors in CSU when reading encrypted configuration file settings.
  • Fixed database setup screens in the CSU to retain the value of the Encrypted option on the connection string when using an existing database as-is.
  • Add error handling to SqlServerDatabaseSetupScreen in the CSU.
  • Fix WPF styles in the manager.

PDQTracker v1.2

17 Mar 19:54
Compare
Choose a tag to compare

Official stable release of version 1.2 of the PDQTracker (v1.2.2).

See full change log since last release.

New Features and Improvements

  • StatHistorianReportGenerator: Added system up-time to each of the daily reports.
  • StatHistorianReportGenerator: Modified correctness report to properly count measurements received while the device was reporting an error to produce a more accurate report.
  • StatHistorianReportGenerator: Modified the completeness report to use the term 'Availability' instead of 'Quality' for clarity.
  • StatHistorianReportGenerator: Fixed an error that occurred when duplicate system up-time statistics were created in the STAT historian as a result of changing point IDs over time.
  • StatHistorianReportGenerator: Set run-time culture to invariant to reduce risk of culture specific failures when generating a long date for a report that may include high-order Unicode characters that are outside the range of what can be produced by Report.NET library since it is only capable of using the standard AFM fonts that are expected to be supported by all PDF readers.
  • LogFileViewer: Added new enhanced general logging capabilities along with a new application, Log File Viewer, that is used to analyze logs.
  • GrafanaAdapters: Added full set of aggregation and operational functions that operate on a per-series or per-set for all data sources that implement Grafana interfaces. See documentation.
  • GSF.TimeSeries: Added up-time statistics for system, subscriber, publisher, input streams and output streams.
  • GSF.TimeSeries: Added a new enhanced version of the time-series special compression algorithm, automatically enabled for new connections, used with the Gateway Exchange Protocol that uses much less bandwidth. Add ; compression=true to connection string of existing GEP subscriptions to enable.
  • GSF.TimeSeries: Created a lookup cache for the main adapter meta-data using dictionary based lookups. This improved load times for input adapters on large systems (e.g., from 160 seconds to less than 1 second in some cases).
  • GSF.TimeSeries: Updated measurement definitions to carry meta-data as part of measurement key with an internal reference inside measurement implementations to reduce total memory footprint requirements for new measurements.
  • GSF.Core: Added a static timer class to allow many hundreds of scheduled events that run at the same interval to be associated with a single wait event instead of creating a new timer for each event (e.g., as hundreds of devices needing to check statistics every second) - this alleviates thread pool exhaustion that can occur when hundreds of timer events get executed at the same time.

Important Fixes

  • DataSubscriber: Updated measurements received with GEP to apply any linear adjustments defined in the local configuration.
  • GSF.Core: Added code to ensure that log files won't become deadlocked if an error occurs during rollover.
  • GSF.TimeSeries: Updated DataSubscriber meta-data synchronization to exclude calculation and alarm signals from the device measurement removal processing such that if a local subscription creates new calculations associated with a subscribed device, the locally created measurements will not get automatically removed at the next synchronization.

PDQTracker v1.1

16 Oct 15:41
Compare
Choose a tag to compare

Note: This is not the latest version.

Official stable release of version 1.1 of the PDQTracker (v1.1.1).

See full change log since last release.

New Features and Improvements

  • New web interfaces to support Grafana dashboards
  • Support for PostgreSQL configuration databases
  • Bulk power calculation adapter improvements including a more functional AdjustmentStrategy parameter for line-to-line and line-to-neutral adjustments
  • New dynamic e-mail responder adapter that will send an e-mail based on a custom expression
  • Simplified installation deployments signed with extended validation certificate

Important Fixes

  • Improved performance of secure implementations of Gateway Exchange Protocol for access control list lookups in service and manager implementations
  • Better phasor reduction management in manager, output streams and GEP meta-data synchronization (e.g., reducing output stream to only include positive sequence phasors)
  • Fixed issues in openHistorian 1.0 data and statistic archive deployments with potential race conditions between rollovers and reading data to prevent data access issues
  • Outage logs now properly serialize stop timestamps in UTC ensuring proper data gap recovery operations
  • NT SERVICE accounts are now assigned needed rights in installer to restart associated host service allowing restart buttons to properly function
  • Fixed issues related to creating and using a custom abstract synchrophasor configurations

Remote Console Access for Users with Viewer Roles

A new command has been added to the remote console to allow messages to be filtered down to desired results, see Filter command syntax below. In order for users with view role access to access the remote console, the filter command will need to be added to the included security resources in the main configuration file.

The simplest way to add this command is to run the XML Configuration Editor application that can be found on the start menu and add the Filter command before the Settings command in the IncludedResources configuration key in the securityProvider section of the configuration settings:

<securityProvider>
    <add name="IncludedResources" value="UpdateSettings,UpdateConfigFile=Special; Filter,Settings,Schedules,Help,Status,Version,Time,User,Health,List,Invoke,ListCommands=*; Processes,Start,ReloadCryptoCache,ReloadSettings,ResetHealthMonitor,Connect,Disconnect,Initialize,ReloadConfig,Authenticate,RefreshRoutes,TemporalSupport,LogEvent=Administrator,Editor; *=Administrator"
        description="Semicolon delimited list of resources to be secured along with role names." encrypted="false" />
</securityProvider>

Filter Command Syntax

Filters status messages coming from the service.

   Usage:
       Filter [ { -List |
                  -Include <FilterDefinition> |
                  -Exclude <FilterDefinition> |
                  -Remove <ID> } ... ]

       Filter -?

       FilterDefinition ::= Type { Alarm | Warning | Information } |
                            Message <FilterSpec> |
                            Regex <FilterSpec>

   Options:
       -List        Displays a list of the client's active filters
       -Include     Defines a filter matching messages to be displayed
       -Exclude     Defines a filter matching messages to be suppressed
       -Remove      Removes a filter

PDQTracker v1.0

13 Sep 14:48
Compare
Choose a tag to compare

Note: This is not the latest version.

Official stable release of version 1.0 of PDQ Tracker (v1.0.161).