The platform includes enhancements specifically designed to leverage Canary Historian, a time-series database that provides high speed performance and friendly configuration tools. This integration includes:
Native Solution Historian: Canary Historian embeds in the platform easily as if it were a native tool. Solutions can use it in conjunction with the existing built-in SQL Historian.
Free 100 Canary Points: The first 100 Canary Historian points are included free of charge. Upgrade options are available for larger systems.
Create Canary Points directly at Designer: No need to use or learn additional tools other than FrameworX Solution Designer.
Simplified License Management: Request license upgrades directly from FrameworX.
Out of Box TrendChart Monitor: Zero configuration is required; an out-of-the-box TrendChart monitor for Canary Historian tags.
Edge Data Collector: Any of the 70+ communication protocols is now a Data Collector for Canary Historian, with Store and Forward support.
Canary Driver and TagProvider: Connection with other Canary Historian instances, either mapping to Local Tags or using dynamic referencing, with tunneling features included.
On this page:
Canary Historian is a time series database built for industrial automation. It is a high-performance historian designed for large-scale applications that handle substantial 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.
Solutions can use both systems concurrently. Performance on SQL storage has increased over the years, but it cannot reach the speed and storage capabilities that a database specifically designed for time-series data, like Canary, can deliver. Use Canary for the tags that require high speed and/or long time retention. Keep those in SQL where the retrieval and storage requirements can be managed with SQL storage.
Trend Charts on Displays, Scripts, and all other modules use data abstraction layers, so there are no changes to 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, when 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.
This integration includes support specifically for Windows, as Canary Labs is a Windows-only integration. |
Canary Historian can be used in different ways by the various modules.
Historian: Uses Canary as a Storage Location for archiving or retrieving HistorianTags.
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.
Configuring Devices using Canary.
→ Read about the Devices Module, or Read about the specific Canary Labs Communication driver.
Configuring TagProvider using Canary.
→ Read about Unified Namespaces
→ Read about the specific Canary Labs TagProvider
Displays and Scripts, with no additional configuration, will query Canary Historian when using tags that were previously connected with Canary using the Historian Module.
Examples of the automated usage:
In Displays TendCharts. See TrendChart Control.
In Scripts, using the Historian Tables method to query data. See Historian Runtime Attributes.
Once you have the CanaryLabs Historian software and the Canary Admin application installed, you will need to configure some permissions for the connection to work.
Admin Configuration
Open the Admin Tab.
Under Endpoints, select every checkbox, but do not change the port numbers.
Under Access, add the users that will be allowed to access the CanaryAdmin programs.
Under Settings, make sure the checkbox for the Persist Last Connection is selected.
Receiver Configuration
Open the Receiver Tab.
Under Endpoints, select every checkbox, but do not change the port numbers.
Sender Configuration
Open the Sender Tab.
Under Configuration > Endpoints, select every checkbox, but do not change the port numbers.
Under Configuration > Access, add all the users that will be allowed to write in the Canary Historian. E.g.:
Views Configuration
Open the Views Tab.
Under Configuration > Endpoints, select every checkbox, but do not change the port numbers.
Under Configuration > Access, add all the users that will be allowed to write in Canary Historian. E.g.:
Under Security > Permissions, add the users for the Root path with the ReadWrite AccessType.
Under Security > Settings, make sure the Security Enabled checkbox is selected.
In this section: