Canary Historian is a time series database built for industrial automation. A high-performance historian designed for large-scale applications that handle large volumes of data writing.. It provides scalability and enables efficient management of high-volume write operations. Its design supports extensive dataset analysis within time contexts for effective trend identification, avoiding the constraints of relational schemas. Canary's architecture balances speed, accuracy, and volume, making it an ideal choice for specialized time series data management needs.
Solution can use both system concurrently. Performance on SQL storage increase over years, but can't reach the speed and storage that a database specifically designed for time-series data, like Canary, can deliver. Use Canary for the tags that requires high speed and/or long time retention. Keep in SQL the ones that the retrieval and storage requirements can be delivered with the SQL storage.
Trend Charts on Displays, Scripts, all FrameworX modules uses data abstraction layers, so there is no changes on the remaining configuration of the Solution, when you decide to modify the configuration of Tags from using one Historian to another. |
The software platform should be installed and, where necessary, licensed.
Set up the Sender's EndPoints and access the Receiver's EndPoints in the Canary Admin Tool.
Done! The initial configuration is finished!
Canary Historian can be used in different ways by various Framework Modules
Historian: Uses Canary as a Storage Location for archiving or retrieving Tags historian.
Devices: Read and Write to external Canary Historian Server with the Device Module.
TagProvider: Map external Canary Historian Server to dynamic integration of its data and structures.
Displays and Scripts: No custom configuration is required, TrendCharts will use Canary Historian Data Automatically if available..
Configuring Historian using Canary
→ Read about the Historian Module, or Read about the specific Canary Communication driver.
Configuring Devices using Canary.
→ Read about the Devices Module, or Read about the specific Canary Communication driver.
Configuring TagProvider using Canary.
→ Read about Unified Namespaces, or Read about the specific Canary TagProvider
Displays and Scripts, with not addition configuration, will query Canary Historian, in using Tags that were previously connected with Canary using the Historian Module.
Examples of automted usage:
In Displays TendCharts. See TrendCharts.
In Displays, using the PlayBack feature .See PlayBack example.
In Scripts, using the Historian.Historian Tables method to query data. See Historian Runtime Attributes
In this section: