How to Log Data Using the OPC DA Collector

Learn how to log data from an OPC DA Server and take advantage of all the useful features the OPC DA Collector has to offer. The OPC DA Collector user interface is not accessible as a tile from the Canary Admin. Instead, access the OPC DA Collector by running the application, Canary Logger Administrator.

Create a DataSet in the Historian

1. Create a DataSet. Without first creating a DataSet, data cannot be logged. Instead of writing data to the historian, all logged tags will buffer in the Sender service.

Learn How to Create a DataSet by reading the linked article.

Start a New Log Session

2. Launch the application 'Logger Administrator'

Typically, different computers in various locations are used to log data. The opening page, under the General Tab, allows the admin to see every device in the network that has the Logger Administrator installed on it. The administrator can remotely monitor/administrate those sessions. All the computers listed under the 'General' tab can be connected remotely so their respective logging sessions or Logging Configuration Files (LCF) can be edited. Right-click on a machine name and select 'Connect' to access that machine's Logger Administrator.

3. Select File | New Log Session from the menu bar.

4. Name the logging session

5. In the field 'Historian Computer', enter the machine name where the Canary Historian is installed. If the install is local, leave this field blank.

   2. Data can be sent to multiple historians in real-time. For example, a company may have a primary historian and redundant historians or a local (level 1) and corporate historian (level 2). Learn How to Set Up Dual Logging by checking out the article.

6. Click Save. Store the file in the appropriate directory.

Groups vs. Logging Sessions

The OPC DA Collector can organize tags in two ways, by groups and by logging sessions. Groups are sub categories within logging sessions. A recommended best practice is to use multiple logging sessions to organize tags based on the future maintenance needs of the LCF. Out of use tags may need to be dropped, or certain meta data properties may need to be changed. To make any changes, the active logger must be stopped momentarily and then restarted. When this occurs, for a brief second, tags do not log data creating a tiny hole of data loss (usually less than 5 seconds) in the archive. Additionally, a new HDB file will also be created. For these reasons, a logging session should never log to more than a single DataSet. Tag groups can be created within a logging session. Groups can be used to organize tags that have common deadbands, update rates, logging triggers, or time normalization.

A LCF logging session should never send data to more than a single DataSet.

6. In the 'Computer' field, enter the machine name or IP address of the OPC DA server. If the OPC DA Server is local, leave this field blank.

7. Select the desired OPC Server and click OK. Use the ellipses to browse.

Browse for Tags in the OPC Server

1. Use the hotkey Ctrl+B or right click in the dark gray space to open the context menu for the Trends grid.

2. Select 'Browse OPC Server'. A window with the OPC Server Nodes appears.

3. At the top of the window, use the drop down menu in the 'Name Prefix' to select a historian DataSet.

4. Browse the OPC Server Nodes and expand them to make tags visible in the window on the right.

5. Select the desired tags. Use 'Apply' to add them to the logging session and continue to browse other nodes without closing the window. Select 'OK' to add all selected tags and close the window.

6. Click 'Apply'.

7. Click 'Save'. Store the LCF in a shared network so it can be run on start-up by other computers on the network.

8. Click 'Start' to begin the logging session.

Configure Additional Settings

A series of fields can be adjusted within the logger, each outlined further in other articles.

Deadbanding - Ignore or omit values unless they change beyond a pre-configured percentage or value.

Trigger Item ID and Trigger Expression - Start and stop logging data only in certain situations or according to another tag's value.

Redundant Logging from Multiple OPC Servers - Prevent data loss in the event of a machine failure by logging data with multiple logging sessions into one historian or from multiple redundant OPC servers to one historian.

Dual Logging to Multiple Historians - Log data to multiple historians, primary/redundant or local/corporate.

AutoStart the DA Logger - Configure the Logger as an automatic service.

Data Transformations - Apply calculations to tags prior to logging values.

Update Rate - Change how often the logger pulls values from the OPC Server.

Normalization Time - Round values up to the nearest millisecond, second, minute, or hour to reduce the data footprint.

Repurpose an LCF - Open and edit an existing logging session using an LCF from another logging instance.

Metadata Properties - Learn why meta properties such as high/low limits, scales, and descriptions are important.

Exporting and Importing Logging Configurations as Excel Spreadsheets - Learn how to edit tags in Microsoft Excel and then import them back into the Logger Administrator.