DataLogger插件 - Kepware OPC Server 中国区总代理、合作伙伴 - 上海泗博自动化技术有限公司

返回上一页

DataLogger

产品概览

下载试用

DataLogger 是一个易于配置的应用程序，可将 OPC 服务器的数据记录到任何兼容 ODBC 的数据库。DataLogger 与 KEPServerEX 紧密集成，带来大量独特的好处，例如安装简单、性能高效而且容易浏览 OPC 浏览空间中的标签。

搜索 KEPServerEX 产品

联系销售人员

询价或售前咨询

  • 电话：4006 139 938 / 021-5102 8348
  • 电子邮件：

资源

  • 性能
  • 协议
  • 可用语言
  • 文档
  • 发行说明
  • 更多技术信息

性能

  • 支持任何兼容 ODBC 的数据库管理系统
  • 用户友好的安装和配置
  • 支持拖放式添加 OPC 数据项（标签）
  • 支持动态创建的标签
  • 提供灵活的触发方式
  • 包括 Simulator Driver
  • 支持已记录项的死区
  • 支持已记录项的可选 NumericID 字段
  • 能够在不要求启用 Log on Static Interval 或 Log on Data Change Trigger 行为的情况下使用启动/停止快照
  • 提供一个 _LogDataBit 系统标签，允许客户端应用程序触发 DataLogger
  • 支持已记录项的 CSV 导入/导出

协议

  • ODBC API

可用语言

  • 英语

文档

发行说明

6.4.321.0

2017/12/13

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

6.3.273.0

2017/9/27

  • 修复了以下问题：在未设置触发器条件的情况下将进行初始日志记录。
  • 修复了以下问题：使用 DataChange 触发器记录项目导致使用服务器时间戳。
  • 增强了存储和转发存储目录验证。

6.2

2017/6/8

  • 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.601.0

2017/4/4

  • 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.2107.0

2016/11/15

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

5.21.114.0

2017/3/20

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

5.21.112.0

2016/8/16

  • 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

2016/5/3

  • 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

2015/10/20

  • 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

2015/6/23

  • 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

2014/7/22

  • 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

2014/2/18

  • 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

2013/8/5

  • 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

2012/6/26

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

运行环境性能特征

  • 作为 Windows 服务和交互用户运行
  • 可通过支持多个并发的日志记录进程（线程）扩展
  • 支持自动创建表格并能够将数据附加到现有表格
  • 直接记录本地项列表中的数据，而不依赖外部 OPC 服务器
  • 支持错误恢复，让用户能够在 DSN 连接断开时自动重新连接
  • 支持可选的自动配置备份（保存最新的配置文件副本）

什么是高级插件？

KEPServerEX 不仅是 OPC 服务器，它还是一种适用于工业自动化和 IoT 的连接平台。只需下载 KEPServerEX，然后从包含 150 多种设备驱动、客户端驱动和高级插件的 Kepware 库中选择，以便适合您工业控制系统的独特通信要求。

高级插件可扩展 KEPServerEX 连接平台的功能。通过将设备中的原始数据转换为其他形式，来提高数据实用性，并增强 KEPServerEX 的功能。

高级插件可以单独进行许可或作为套件的组成部分进行许可，还可以随着连接需求的发展按需进行许可。

上海泗博自动化技术有限公司  Copyright(c) 2005-2021   SiboTech.net All Rights Reserved 
foot
公司总机： 021-6482 6558    |   沪ICP备15057390号