KEPServerEX DataLogger

Release Notes

• 6.10.623.0

  2/23/2021

  • Added code to prevent store and forward files from being corrupted.

  6.8.796.0

  12/17/2019

  • Fixed an issue introduced in 6.7 where string Numeric Item IDs were no longer supported. Customers using previous versions with existing projects that used string IDs are not able to upgrade to V6.7 but can upgrade to 6.8.

  6.7.1046.0

  6/27/2019

  • Configuration settings can now be set through the Configuration API service.
  • Feature translation for all languages currently supported by the server.
  • Removed CSV Import and Export feature. Added help information on importing via JSON and the Configuration API.
  • Added full configuration of DataLogger through JSON files.
  • Updated the user interface to conform to Version 6 styling.
  • Enhanced the plug-in to be able to log Complex tags from the Advanced Tags plugin.

  6.5.829.0

  6/19/2018

  • Fixed an issue where DataLogger failed to log when Store and Forward (SAF) was enabled.
  • Fixed an issue where DataLogger could incorrectly log records at startup or when changing log group state from disabled to enabled.

  6.4.405.0

  6/11/2018

  • Implemented and rolled back Skip SAF Records that Failed with NULL Insert Error.
  • Updated to treat table validation errors as recoverable.
  • Fixed issues with unexpected behavior around the “Always Triggered” property.

  6.4.321.0

  12/13/2017

  • Enhanced to treat table validation errors as recoverable and continue table validation attempts until successful.

  6.3.305.0

  6/11/2018

  • Updated to treat table validation errors as recoverable.
  • Fixed issues with unexpected behavior around the “Always Triggered” property.

  6.3.273.0

  9/27/2017

  • Fixed an issue where initial logging would occur when no trigger conditions were set.
  • Fixed an issue where logging an item using a DataChange trigger resulted in using the server timestamp.
  • Enhanced store and forward storage directory validation.

  6.2.429.0

  6/8/2017

  • Fixed an issue where DataLogger used the Dynaset open method in some cases rather than Snapshot when a MySQL DSN was used. MySQL does not support Dynasets.

  6.1.655.0

  6/11/2018

  • Added a flag to INewRowProducer::_AddEntries that specifies whether to use the server timestamp or the item timestamp.

  6.1.601.0

  4/4/2017

  • The timestamp logged to the database will now reflect the time of the last data change.
  • Resolved validation errors that caused the runtime to fail to load JSON and XML project files, which resulted in an ‘Invalid Name’ event log message.
  • Fixed an issue where fields other than TIMESTAMP would give a SQL “Datetime field overflow” message when their data type is set to DATETIME.
  • Fixed an issue where a read-only user could modify log groups.

  6.0.2206.0

  6/11/2018

  • Added conversion of fraction part of SQL TIMESTAMP_STRUCT from ms to ns for variant types in UpdateField().

  6.0.2107.0

  11/15/2016

  • Log item timestamp now reflects the item log time rather than the last data change time.

  5.21.235.0

  6/11/2018

  • Fixed a bug where a timestamp other than the item log time could be used.
  • Updated to treat table validation errors as recoverable.

  5.21.114.0

  3/20/2017

  • Updated log item timestamps to always reflect the item log time rather than the last data change.

  5.21.112.0

  8/16/2016

  • Fixed a situation where initial values were not logged.
  • Fixed an issue where all log groups shared the same VARCHAR mapping checkbox state.
  • Changed behavior of the “Log on Static Interval” trigger option to log the current timestamp rather than the timestamp of the last data change. This change restored the behavior that existed prior to the 5.20 release.

  5.20.396.0

  5/3/2016

  • Added support for mapping Numeric ID to VARCHAR instead of NUMERIC.
  • Updated the timestamp logged to the database to reflect the time of the last data change when using “Log on Data Change.”

  5.19.467.0

  10/20/2015

  • Added an error string for “Too many tags to log in wide column format” to message log and documentation.
  • Corrected an issue where NULL quality could be written.
  • Resolved an issue where a trigger interval of greater than 24 days could cause the trigger to appear to be constantly on, causing excessive writes to the database.
  • Resolved an issue that could cause data corruption when writing large strings or arrays.

  5.18.662.0

  6/23/2015

  • Removed the ability to pick a data type for log items. The type was not used.
  • Fixed an issue where enabling a DataLogger log group after reinitializing the server did not correctly start the log group.

  5.15.585.0

  7/22/2014

  • Reorganized the Triggers dialog to be more intuitive. The start/stop logging options were moved to the Absolute and Expression trigger type pages. The Log on Static Interval and Log on Data Change logging options were moved to a new Logging Conditions page.

  • Added a new trigger condition that allows a snapshot to be taken of a log group’s current tag values when a monitored item changes. A deadband can be applied to the monitored item to control how often a snapshot occurs.

  • Fixed an issue where enabling a log group could cause false triggers in some trigger expressions that included server tag data. In these cases, the tags failed to get an update before the trigger expression was checked, which caused the check to return true incorrectly.

  • Fixed an issue where a negative value was shown for the log group’s Update Rate (located on the Data Map tab) if the Update Rate was greater than 24 days.

  5.14.491.0

  2/18/2014

  • Added support for store and forward. Log groups can now store data locally to disk when connectivity to the SQL server is lost, and then forward the data when connectivity returns.

  • Fixed an issue where performing a CSV export would disable the Apply Changes button without applying the changes to the Runtime. Now, performing a CSV export causes the changes to be applied and disables the Apply Changes button.

  • Fixed deadlock that could occur if Link Tags were linked to DataLogger System Tags. The deadlock occurred when starting a log group.

  5.12.142.0

  8/5/2013

  • Resolved a DataLogger issue introduced in KEPServerEX version 5.12.140.0 where values for columns associated with the first log item in the Server Item List were incorrectly logged as NULL. This issue affects customers who upgraded to version 5.12.140.0 from an earlier server/plug-in version and use the Wide Table Format to log data.

  5.9.170

  6/26/2012

  • Added the new “Item data set to good quality” Event Expression trigger to the Start and Stop condition pick lists.