Edit Panel Data Log
- Equipment Name and Data Point are fixed values that cannot be changed.
- Start Date cannot be changed from the edit page. You can change it by deleting and recreating the data log.
- Change the End Date and End Time to reflect how long you would like to log the data. There is no restriction on how long you can run a data log. If you leave it blank, the data log will never stop without additional intervention.
- If the original data log was set up with a Fixed Number of Samples, you can see and edit the field. The data log collects and stores data until the number of samples reaches the fixed number. Thereafter, each new sample replaces the oldest sample in the database. This is known as a "rolling window."
- Click Select Attributes if you want to assign attributes or edit the attribute assignments for the data log.
- Select Optimized by Server for the Collection Interval to use the standard interval for equipment of that type (shown at the top of the screen).
- Select Custom Interval for the Collection Interval to specify a regular interval other than the standard interval (for example, every 24 minutes).
- Select Scheduled Day and Time for the Collection Interval to specify a specific time of day on one or more days per week.
- Set the Offset time. The offset of a data log determines how many minutes past the top of the hour the data log will initiate collection. For example, a data log with a fifteen minute collection interval and an offset of zero would collect data at 9:00, 9:15, 9:30, etc. If the same data log had an offset of three, it would collect data at 9:03, 9:18, 9:33, etc.
- The offset of a data log defaults to the minutes associated with the time that the data log was created in Tracer Ensemble. For example, if a user creates a data log at 9:23 AM, the data log's offset will be set to 23.
- Offset does not mean that the data log will not start collecting until that time has been reached. In the previous example of the data log created at 9:23, if the collection interval is five minutes, the data log will collect at 10:03, 10:08, 10:13, 10:18, 10:23, etc.
- Offset is utilized to spread data collection loads for data logs. If a user creates many data logs that are all collecting at fifteen minute intervals, the actual data collection will be spread across the fifteen minute blocks. As a result, Tracer Ensemble will not be forced to try to collect all of the data in a single minute and then sit idle for fourteen minutes.
- In the event that it is determined that Tracer Ensemble is not able to collect data at specified times due to extensive data collection at peak times, it is useful to edit the offset of critical data logs to a time that is off of the peak collection times.
Note: The offset for data logs in Tracer Ensemble applies only to when Tracer Ensemble will collect data. In the case of trend logs in BACnet devices that are being collected into Tracer Ensemble, this applies to the time that Tracer Ensemble will read the buffer data from the trend object, not the time that the trend object itself collects data. Consequently, if the user's desire is for collected trend data for multiple logs to show data collected at the same time, the trend log definitions in the BACnet device would need to be modified with the appropriate service tool.
Possible Error Messages
Related topics