The Canary logger is what collects the data from the OPC server. This is where the Canary services start. One of the things to take note of, is that the logger simply collects from the OPC server. This means that the boundaries that the OPC server specifies are passed to the logger administrator. In most cases users can expect to see the tags collected as tags with R4 data types. Below is a table of the different types of data and their min/max range:
The logger can be configured to override the data type passed if the OPC server has incorrectly identified the type. This can be accomplished by opening the log session and clicking the down arrow to display the different types. A click of the mouse will then change the specified type to the manual entry selection. The log session will then show the change after being applied. The log session will also need to be stopped and started to pick up this change.
It is also possible to change enter engineering units, high/low scales, high/low limits, dead band, and data transformations. Engineering units, high/low scales, and high/low limits will only affect how the data is displayed using visualization tools. It can, however, affect the data exported from the historian as these properties will be stored with the data. When the data is viewed in Axiom, it may be helpful to know that the scale may not reflect the stored range. This is because Axiom overrides the stored scale with a scale range written by the lowest/highest values. Axiom does give the option to change the scale range through a manual input.