This document has only the specific information about the device connection settings and its address syntax.
Refer to the User Guide for more information on the Device Module.
On this page:
Communication Driver Information | |
---|---|
Driver name | CanaryLabs Historian |
Assembly Name | T.ProtocolDriver.CanaryLabs.dll |
Assembly Version | 1.0.0.8 |
Manufacturer | CanaryLabs |
The following requirements must be matched in order to use the CanaryLabs driver:
For more information on how to set up the CanaryLabs Environment, see the Appendix.
Protocol options are not used in this driver. The remaining channel configurations are the same as in the reference guide.
The station parameters are:
Use the Test Connection button to check the connection with the Server and Database. |
With an OK! status message, 3 features are enabled for this Driver:
The Import Tool is described in this section, and the other two are detailed in the Appendix.
You can automatically import the existing Canary Variables into your Project by clicking the Import button.
This tool allows you to choose variables, from the list, that will be imported into your project; automatically creating the Tags and Communication Points.
You can use the Browse button to see the available data in the CanaryHistorian database, or you can write a Tag address directly in the Item field.
For a simple Tag, use 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 (ex. Motor1 and Motor2), and input it into the Points list. Its members (e.g.: 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 a name is valid and get the current value and quality.
This Communication Protocol supports the TagProvider feature, which is a tool that allows you to access your Communication Device Data Model without creating project Tags.
For more information, please refer to the TagProvider document.
To configure the CanaryLabs protocol as a TagProvider, go 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.
The status of the driver execution can be observed through the diagnostic tools, which are:
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.
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.
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.
Open the Receiver Tab.
Under Endpoints, select every checkbox, but do not change the port numbers.
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.:
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.