DataLogger
產品概覽
DataLogger 是一個易于配置的應用程序，可將 OPC 服務器的數據記錄到任何兼容 ODBC 的數據庫。DataLogger 與 KEPServerEX 緊密集成，帶來大量獨特的好處，例如安裝簡單、性能高效而且容易瀏覽 OPC 瀏覽空間中的標簽。
資源
- 性能
- 協議
- 文檔
- 應用案例
- 可用語言
- 發行說明
性能
- 支持任何兼容 ODBC 的數據庫管理系統
- 用戶友好的安裝和配置
- 支持拖放式添加 OPC 數據項（標簽）
- 支持動態創建的標簽
- 提供靈活的觸發方式
- 包括 Simulator Driver
- 支持已記錄項的死區
- 支持已記錄項的可選 NumericID 字段
- 能夠在不要求啟用 Log on Static Interval 或 Log on Data Change Trigger 行為的情況下使用啟動/停止快照
- 提供一個 _LogDataBit 系統標簽，允許客戶端應用程序觸發 DataLogger
- 支持已記錄項的 CSV 導入/導出
協議
- ODBC API
文檔
可用語言
- 英語
發行說明
6.10.623.0
2021/2/23
- Added code to prevent store and forward files from being corrupted.
6.8.796.0
2019/12/17
- 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
2019/6/18
- 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
2018/6/19
- 修復了在啟用“存儲并轉發”(SAF) 時，DataLogger 無法記錄的問題。
- 修復了在啟動或將日志組狀態從“已禁用”更改為“已啟用”時，DataLogger 記錄錯誤的問題。
6.4.405.0
2018/6/11
- 實施并回滾了“失敗且存在空插入錯誤”的“跳過 SAF 記錄”。
- 更新為將表驗證錯誤視為可恢復錯誤。
- 修復了“始終觸發”屬性的意外行為的問題。
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.
訂貨號：KWP-DLOGR0-PRD
請聯系銷售人員獲取臨時授權
- 電話：400 613 9938
- 電子郵件：
