You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

For a generic explanation of the configurations for the Device Module, Channels, Nodes, and Points, please refer to the reference guide.

Summary Information

Communication Driver Name: CanaryLabs Historian

Current Version: 1.0.0.1

Implementation DLL: T.ProtocolDriver.CanaryLabs.dll

Manufacturer: CanaryLabs


System Requirements

The following requirements must be matched in order to use the CanaryLabs driver:

  • Product version 9.1.
  • .Net Framework 7.1 or higher. 

For more information on how to set up the CanaryLabs Environment, see the appendix.


Channel Configuration

Protocol Options

Not used in this driver. The remaining channel configurations are the same as in the reference guide.


Node Configuration 

Station Configuration

The station parameters are:

  • ServerName: 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 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 (defined in CanaryAdmin).
    • Windows: Connection using windows credentials.
  • UserName: User name used for verification (Valid for Username and Windows connection types).
  • Password: Password used for verification (Valid for Username and Windows connection types).
  • Views: List of Views found in the specified ServerName. If View is virtual, this Node will be Read-Only.
  • Dataset: Name of the dataset you will connect to. Not available when selected View is Virtual.


Use the Test Connection button to check the connection with the Server and Database. 

With a Success! status message, you enable 3 features for this Driver:

  1. Import Tool
  2. Unified Namespace
  3. Asset Modeling

The Import Tool is described in this section and the others are detailed in the appendix.


Import Tool

You can import the existing Canary Variables automatically into your Project by clicking on the Import Button.

This tool allows you to choose the variables, from the list, that will be imported into your project; automatically creating the Tags and Communication Points


Point Configuration

Address

You can use the Browse button to see all the data available in the CanaryHistorian database, or you can write the Tag address directly in the field.


For a simple Tag, fill the address with the syntax: ?DatabaseName?.?VariableName?. E.g.: 

TagName

Address

Motor1 Temperature

Motor1.Temperature

Motor1 RPM

Motor1.RPM

Motor2 Temperature

Motor2.Temperature

Motor2 RPM

Motor2.RPM

Or you can create a Template (Motor1 and Motor2), and input it into the Points list. Its members (Temperature and RPM) will be mapped automatically. E.g.:

Engineering Environment

TagName                               Address

Motor1

Motor1

Motor2

Motor2

Runtime

TagName                               Address

Motor1.Temperature

Motor1.Temperature1

Motor1.RPM

Motor1.RPM

Motor2.Temperature

Motor2.Temperature1

Motor2.RPM

Motor2.RPM


Array elements are also automatically expanded in runtime.


Use the Verify button to check if the name is valid and get the current value and quality.


TagProvider

This Communication Protocol supports the TagProvider feature, which is a tool that allows you to access your Communication Device Data Model without creating any Project Tags.

For more information, please refer to the TagProvider document.

How to Configure

To configure the CanaryLabs protocol as a TagProvider, navigate to Edit  >  Tags  > Providers, and create a new provider for the CanaryLabs protocol.

Configure the items under the PrimaryStation column the same way that was described in the Node Configuration.


Troubleshooting

The status of the driver execution can be observed through the diagnostic tools, which are:

  • Trace window
  • Property Watch
  • Module Information

A status value of 0 (zero) means the communication was successful. Negative values indicate an internal driver error, and positive values are the protocol's error codes.


Appendix

CanaryLabs Configuration Procedure

Once you have the CanaryLabs Historian software and the Canary Admin application installed, there are some permission configuration that are required in order 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.

  • Anonymous
  • System
  • Administrator
  • Interactive
  • Everyone
  • ?Your User?.


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.:

  • Anonymous
  • System
  • Administrator
  • Interactive
  • Everyone
  • ?Your User?.


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.:

  • Anonymous
  • System
  • Administrator
  • Interactive
  • Everyone
  • ?Your User?.


Under Security > Permissions, add the same users for the Root path with the ReadWrite AccessType.


Under Security > Settings, make sure the Security Enabled CheckBox is selected.

  • No labels