Setting up data / trend logs using Tracer TU

Purpose

The purpose of this article is to walk through how to create and retrieve data / trend logs using Tracer TU.

Overview

Data Logging, also referred to as trending, records in real-time the value of a data point in the system and the time at which the value was recorded.

Trends can be captured on UC400, UC600, Symbio 700, and Symbio 800.

The steps for setting up trend data is the same for each controller type. Data storage is a continuous window where only the most recent data is stored. Data older is discarded to make room for the newest data. The more data collected/higher collection frequency will reduce the amount of data stored on a controller.

UC400/600: Data will be lost if power is cycled to the UC prior to someone downloading the data to a PC.

Symbio 700/800: Data is saved to on board memory and can be recovered after power is cycled.

Setup

1. Click on the “Graph” tab on the right side of the screen

2. Click the “Data Log Setup” tab3. Click on the “Add New” button

4. Fill out the following page as needed:

Here is a brief description of the fields.

1. 1. 1. 1. Datalog Name:
            • Choose a name that is not the same as the referenced selection. It will give you an error if you try to name it the same as the point you are referencing.
         2. Reference Selection:
            • Choose the point you are trying to log
         3. This can be “Triggered” or “Scheduled”

• • • • • Triggered is if you want to have this start logging if a point changes to a certain condition. This is typically used to catch a units operating condition when a binary value changes state or an analog value goes above or below a certain value.
        • Scheduled can track the unit's operation at all times or for specific times (see figure).

Figure. Scheduled Data Log Screen

4. This chooses how many samples to keep in memory. There is a limit on the memory, so it is important to get only as many samples as needed. Also, even more important is the “collection frequency.” In the example, we are looking at a compressor running status based on a freeze trip. Only one second is used, because it was noticed that compressors could still be running after a “Compressor Lockout” existed. Items such as setpoints don’t change often, so they can be set at a 1+ minute frequency. Water and air temperatures are more critical to most trends and a 5 second or less collection frequency may be desired to catch exactly what the state of the unit is in. If days of trends are required, the duration can be increased to capture a longer period of data.

5. This chooses the point to enable the logging. In this case I am waiting until Freeze Avoidance Lockout 1 is enabled and then collecting data.

6. Typically post trigger on delay time is set to 0, because it is most important to see what is going on as soon as a trigger is initiated. It’s okay in this instance with stopping the trend once the trigger is false here. The 2 minutes of trends will capture the necessary info, and it is important to allow restart, as to if this happens to the unit more than once before the trends are able to be pulled.

7. This goes along with BOX 5 as to what value will trigger the response. In the case of a binary value, true or false. In the case of an analog value > Greater than, or <Less than.

5. Complete setting up the rest of the trends desired.

6. Be sure that all data logs are enabled! They do not record data otherwise.

7. Select Send to Device when complete.

Retrieve Data Logs

Data log files can be retrieved after an event has occurred that requires review of the files.

1. Select Tools, Retrieve Data Logs

2. Select all the points using the check boxes

3. (Optional) change the file path that the files are saved (ie: desktop)

4. Select the retrieve button

5. The data files will now be saved in the specified folder.

WARNING:

Information in this article is intended for use by individuals possessing adequate backgrounds of electrical and mechanical experience and who comply with all federal, state, and local laws, rules, orders, or regulations related to the installation, service, or repair of a heating or central air conditioning product. Any attempt to install, service, or repair a heating or central air conditioning product may result in personal injury and/or property damage. The manufacturer or seller cannot be responsible for the interpretation of the information contained herein, nor can it assume any liability in connection with its use.