Count Logging Settings : Fluke Process Instruments

Introduction

This quick guide discusses the count logging settings available on the Irisys Vector units that you must configure in order to ensure data is stored at the correct time interval.

The Count Logging setting is how often count data is stored internally, including histogram data. It also determines the HTTP Post of count data, if configured.

In order to access these settings, you must first make an initial connection to the Vector unit; see separate guide: Irisys Vector 4D - Making a Setup Connection.

Count Logging Settings

Once you are connected to your Vector, the count logging settings are accessed via the ‘Settings’ tab, then ‘Count Logging’:

If connected to a Vector via an Estate Manager connection, make sure you select the ‘Live View’ option to make changes

Count Logging

The Count Logging setting relates to storage of data within the counters internal flash memory for retrieval later. If logging is set to 60 seconds, then every minute – on the minute – the register values will be stored internally.

Default logging is 900 seconds (15 minutes). Some common values are shown below:

Interval (Seconds)	Interval (Minutes)	Notes
60	1 minute	60 logs an hour on the minute
300	5 minutes	12 logs an hour
360	6 minutes	10 logs an hour
600	10 minutes	6 logs an hour
720	12 minutes	5 logs an hour
900	15 minutes	4 logs an hour (default)
1200	20 minutes	3 logs an hour
1800	30 minutes	2 logs an hour
3600	60 minutes	1 log an hour on the hour

As people walk through the field of view and cross count lines and/or enter and leave any configured zones, the corresponding register values will change. Most of the register count values will keep incrementing as more people are counted and will never reset to zero unless the counter is powered off, or the ‘Reset System Counts’ option is selected – see separate ‘Counting setup’ document. This means that the logged counts will also be a constantly increasing number, and in order to calculate the incremental number of people that have been counted in an hour (for example), you must use the count total from an hour and subtract the count total from the previous hour.

Some register types, such as the Zone Occupancy register, lend themselves to a lower logging interval setting due to the live nature of that particular register type.

The logging interval is a single global value which all registers observe.

Histogram Data

The Count Logging setting value determines the logging frequency for storage of the histogram data too.

A Vector can also store various histogram data, such as the heights of everyone crossing a count line, for example. This data can be pulled back via the Vectors REST API (or via the REST API in Estate Manager) and can be displayed directly from within the Vectors Counting setup – see separate document.

The histogram data may be useful when determining a height threshold for differentiating between adults and children. It is also possible to pull additional adult/child data from the histograms when comparing a weekday to a weekend day for example.

HTTP Post

Sending of count data via HTTP Post is also governed by this setting. Essentially whenever new data is available, it will trigger an HTTP Post. E.g. if the logging period is 900 seconds, data will be logged internally when the timer reaches 15 minutes, and will then be immediately sent via HTTP Post.

For real-time data the alternative method data retrieval via MQTT should be used, see documentation available.

Saving

Before navigating away from the device, click the ‘Save’ button to complete any changes.

Notes on API Usage

Count and Histogram data can be pulled using the REST API, but use of this API is beyond the scope of this document and programmers are directed to the built in REST API documentation which is accessed via the web interface:

The REST API used to communicate directly with the Vector is the same REST API that is built into Estate Manager. It is therefore possible to produce software which can work with or without Estate Manager, with very few changes required between each method.

We have some code examples on how to integrate with both the REST API and the HTTP Push functionality stored online at the GitHub repository. Go to: https://github.com/IrisysUK

No part of this publication may be reproduced without prior permission in writing from InfraRed Integrated Systems Limited. This document gives only a general description of the products and except where expressly provided otherwise shall form no part of any contract. From time to time changes may be made in the products.

Count Logging Settings Print