Temperature Averaging Strategy in HyperStat

| Overview

Multiple sensors can be connected to the HyperStat, to sense different parts of the zone, so that the overall zone parameters are better sensed. When multiple sensors are so connected to the HyperStat, the resultant temperature is usually the average of the temperature from all the sensors. This averaged temperature value is the one that influences the algorithm to provide the necessary conditioning.

The averaging was just easy, but with the interpolated values, and the update frequency types in place. Understanding the strategy used for the resultant temperature value to the HyperStat is highly recommended. For the FMs to understand the building spaces, and the support folks to mitigate the queries and concerns raised.

| Temperature Averaging Strategy

Based on the different modes and different update frequency types there could be three possible scenarios, which require an understanding of the temperature value averaging strategy.

Case 1: When the average enabled UI is absent for the HyperStat:

In this case, the resultant temperature value in the Home Screen is just a straightforward Average of the Temperatures from different sensors in the bus.

Case 2: When HyperStat is average enabled:

Also, in this case, the resultant temperature value on the Home Screen is just a straightforward Average of the Temperatures from different sensors in the bus.

Note: Average off values are considered only after 60 sec after the HyperStat is powered ON.

Case 3: When HyperStat is average enabled, and the Transmitted value for the widgets and visualizations (based on the interpolated values, for the regular update sent at 40 seconds) are as below.

In this case, the resultant temperature value in the Home Screen is just a straightforward Average of the Temperatures from different sensors, and the average for the interpolated values for the widgets and visualizations is, as per the Transmitted Values column as shown above.

Note: For transmitted values, the average of the previous values is considered (limited to 5 numbers) for every 5 seconds before it is transmitted during the 40-second Regular update.