The Canary Historian integration refers to the embedded component, designed for the collection, storage, and analysis of time-series data from industrial operations. It addresses the need for reliable data historization, providing a solution for capturing and preserving volumes of operational data. The historian facilitates real-time data acquisition through direct integration with over 70 protocol devices, allowing for data aggregation and historization. Its functionality enables users to model data with asset tools, visualize trends, and develop custom applications through scripting, enhancing data usability and accessibility. Configuration of the Canary Historian involves the selection of data sources, mapping tags, and specifying storage parameters, all within the software platform. In use, the historian supports the creation of dynamic, data-driven user interfaces, including HMI/SCADA dashboards and analytical displays, making it indispensable for monitoring, controlling, and optimizing industrial processes.

On this page:

Introduction to Canary Labs

Watch the video tutorial


Built-in Integrated Canary Historian

  • Includes embedded and integrated Canary Historian, available with version 9.2 and newer
  • Includes free, 500 Canary Historian Tags with any license – Edge to Unlimited.
  • Add Tags to the 500 points (from 1500 to Unlimited!)
  • Unlimited Tag Option w/Framework Unlimited
  • Native Integration to Canary Historian and the Canary System via Tag Provider


Easily Connect to Any Canary Server

Find detailed docs at Tag Provider.

Canary and our company share a common tag definition and asset modeling

In addition to the embedded Canary Historian, we also have a new built-in integration with the Canary System that is easy to use, high speed and extremely secure, as it leverages Canary’s .NET API to connect at the core level, allowing you to publish and consume data and use Canary’s tags and models as well.

There is no need for extra configuration or even to create tags within our framework platform — simply define the server and browse the assets you need!

Node Configuration

The station parameters are:

  • ServerName: The name or IP address of the machine running the CanaryLabs Historian. (If the service is not running in the default port, the syntax should be: ComputerName:PortNumber or IpAddress:PortNumber)
  • ClientID: Indicates the client identification that is used to make calls in the Canary service
  • ConnectionType: Specifies the ConnectionType with the service

               The options are:

    • Anonymous: Connection using no credentials
    • UserName: Connection using a username/password that is defined in CanaryAdmin
    • Windows: Connection using Windows credentials
  • UserName: The user name used for verification (Valid for the Username and Windows connection types)
  • Password: The password used for verification (Valid for the Username and Windows connection types)
  • Views: A list of views found in the specified ServerName. If the view is virtual, the Node will be Read-Only
  • Dataset: The name of the dataset you will connect to. (Not available when the selected view is Virtual)
Always test your connection with a Test Button.


Setup

To setup canary to operate in your FrameworX solution, activate the number of tags for Canary on Solution → Settings menu.

How to Configure

To configure the CanaryLabs protocol as a ExternalTag, navigate to Unified Namespaces  >  ExternalTags Sources  and create a new connection for the CanaryLabs Communication Driver.

Configure the items under the PrimaryStation column the same way that was described in the Node Configuration. To see more details about setup a Canary ExternalTag please see the CanaryLabs TagProvider page.

In this section: