Pipe Surface Water TemperatureMeasurement

Description of Pipe Surface Water Temperature

This technique uses a 4-channel analog logger with a thermocouple sensor to take long-term measurements of water temperature (F) at one-hour intervals. This technique can be used to measure the fluid temperature from the surface of a pipe and not directly in the water stream. Data can be used to determine the cooling load and heat rejected to the outdoors by a cooling plant, the heat load delivered by a heating plant and heat recovered by an economizer. For more details on how collected data is used for calculations refer to the calculation methodology of the system being measured.

Measurements should be taken at one-hour intervals and not instantaneous values. When taking one-hour measurements, the logger will detect the temperature several times every hour and store the average value. Sometimes temperature can fluctuate over a one-hour period, but the instantaneous temperature value will not indicate that change.

The duration of the long-term measurement should be a minimum of six weeks. Measurements should be when the system of interest is operating under normal conditions.

Type of measurement

Proxy

Equipment

The measurement equipment needed for this procedure is a 4-channel analog logger that is compatible with thermocouple sensors. Thermocouple sensors are specially designed to measure very high temperatures such as the flue stack of a boiler and very low temperatures such as the surface of water pipes for a chiller system. Different thermocouple sensors are used to measure hot or cold pipes. Refer to the FELL catalog to identify the correct loggers and sensors for your project. The contents of this guide are largely based off the Onset HOBO UX120-14M logger and the TC6-T sensor, which can be found and borrowed through FELL.

For sensors installed at a pipe surface the sensor must be secured with thermal tape and the pipe surface should be cleaned prior to installation. Please note that loggers will require setup with a computer or phone using the manufacturer’s proprietary software prior to installation and measurement logging and that older loggers will require the use of a cable to connect to a computer. Refer to the measurement equipment’s user manual for a detailed description of setup requirements.

Measurement steps

1. Preparation for data acquisition

Use the manufacturer’s software to set up and launch the logger(s). Refer to the equipment’s user manual for detailed instructions on how to set up the logger.

  • Logging interval: 1-hour
  • Date and time to start logging
  • Date and time to stop logging
  • Value(s) to measure: Temperature (oF)
  • Activate input channels on the logger
  • Type of thermocouple sensor (K-type or T-type)
  • Sampling interval: 1-second
Figure 1: How to configure the 4-channel analog logger & Onset Current Transducer using HOBOware
Figure 1: How to configure the 4-channel analog logger & Onset Current Transducer using HOBOware

2. Installation of equipment

  • Connect the sensors to the data logger.
  • Place the data logger near the pipes. Avoid adhering the logger to the pipe itself.
  • Clean the surface of the pipe where the sensor will be placed and remove any dust on the pipe surface.
  • Place the sensor on the clean surface and apply thermal tape to fully cover the sensor.
Figure 2: Data logger placed on a chiller with two thermocouple sensors connected to it. Data logger in use is the Onset HOBO 4-Channel analog logger (UX120-14M).
Figure 2: Data logger placed on a chiller with two thermocouple sensors connected to it. Data logger in use is the Onset HOBO 4-Channel analog logger (UX120-14M).
Figure 3: Thermocouple sensor taped to the pipe surface of a chilled water return line. The sensor in use is the TC6-T.
Figure 3: Thermocouple sensor taped to the pipe surface of a chilled water return line. The sensor in use is the TC6-T.

3. Verify data is being collected

Wait 24-48 hours to verify data collection. Return to the location of the measured equipment and use a laptop or phone with the manufacturer’s proprietary software installed to do the following:

  • If necessary, connect the logger to the laptop or phone via USB cable. Otherwise, use the software to connect with the data logger via Bluetooth.
  • Analyze the data with a plot graph. This can be done with proprietary software or Microsoft Excel after exporting the dataset as a .csv file.
  • Determine if measured results align with the expected operation of the system or component.
Figure 4: Plot graph of data of a chiller system supply and return line. HOBOware Free is the software used to setup the logger and extract data. This logger had two sensors connected to it and results in two separate measurements as shown on the plot graph.
Figure 4: Plot graph of data of a chiller system supply and return line. HOBOware Free is the software used to setup the logger and extract data. This logger had two sensors connected to it and results in two separate measurements as shown on the plot graph.

4. Retrieve measurement equipment and download all final data

After verifying that the logger is collecting data, do the following:

  • Allow the logger to collect data for the remainder of the measurement period.
  • After the measurement period has concluded, remove the logger.
  • If necessary, connect the logger to the laptop or phone via USB cable. Otherwise, use the software to connect with the logger via Bluetooth.
  • Use the proprietary software to Stop the logger and end data collection.
  • Download all data from the logger and save the file in the.csv file format for analysis.
Figure 5: Final data table. Data was extracted from the logger using HOBOware free and exported for analysis. This data set contains two columns of temperature data, one for each sensor that was used.
Figure 5: Final data table. Data was extracted from the logger using HOBOware free and exported for analysis. This data set contains two columns of temperature data, one for each sensor that was used.

Troubleshooting

Problem: the logger is measuring unexpected values