Fluke Process Instruments

Introduction

This quick guide discusses the optional Wireless fine motion room sensor and its corresponding installation and configuration. This optional hardware component provides a corresponding register value that will increase whenever motion is detected. Although this register on its own may be useful in some situations, its primary use case is as a feed into the (Analytic only) Occupancy type register in order to reset the occupancy value to zero after a period of inactivity. In this way, any over-count bias (no matter how small) can be removed automatically. See the ‘Data Access and Usage’ section below for more details.

Its intended use is for applications such as meeting room utilization reporting.

When occupancy reporting on rooms with multiple doors is required, multiple Vectors should be used – covering each way in and out of the area of interest – with all the IN and OUT lines feeding into the Occupancy register via either the Wide Tracker or remote registers functionality.

Pre-Requisites

In all cases it is strongly recommended that Vectors are updated to very latest firmware version currently available. But in any case, a minimum firmware version of 2.0.135 is required for full compatibility with the USB receiver and fine motion detector.

Firmware updates and update instructions are available from the Irisys partner portal as usual - here.

Hardware Installation

To add a wireless PIR you need both the PIR itself and a corresponding USB receiver:

The motion sensor should be positioned in the middle of the room where it is most likely to be able to detect people movement. Pull the battery tab and secure the motion sensor with appropriate fixings. For larger areas up to four Motion Sensors can be utilized with a single USB Receiver.

The USB Bluetooth Receiver should be connected to the Vectors free USB port, before power up, so that it is correctly recognized and usable. If the receiver is connected when the Vector is already powered on, perform a reboot of the Vector for the internal drivers to be correctly configured. When correctly identified there will be a log entry in the diagnostics:

Configuration

Before the Fine Motion Room Sensor can be used in any applications, it must first be assigned to a register.

To do this, go to ‘Settings’ then the ‘Counting’ tab to access the main counting functionality.

By default, a Vector will have two counting lines configured, as shown in the Register dialog list below. If the registers dialog is not shown, click the ‘Registers’ button in the top right:

On the register dialog, click the plus symbol (+), then scroll down through the list of available register and choose the ‘Wireless PIR’ register type, and click ‘Next’:

Enter a suitable (unused) name for the new register, and click ‘Next’:

Now click the Devices dropdown and any in range Room sensors will be listed.

Select the correct Room Sensor and then click ‘Next’:

Lastly click the ‘Add Register’ button to finish.

The new wireless PIR register will then be shown on the registers dialog.

Note that if the Room sensor has been powered up for some time, it will most likely already have some activity counts recorded.

Data Access and Usage

The main use case of the room sensor is as a feed into an Occupancy register. An Occupancy register performs a simple IN minus OUT calculation to derive an occupancy count value, and a configurable period of no activity received from the Room Sensor can be used as a signal that the area is definitely empty, and the occupancy value can be reset to zero – if required. This will correct any IN-count bias and prevents a cumulative error from building up, which could be possible in some cases, even when the IN and OUT accuracies are very similar.

If you want to use the Fine Motion Room Sensor data directly in your own software, the data is logged and available in exactly the same way as any of the other register types. The following data access methods are available:

• REST API. Software written using the REST API will allow you to pull the periodically logged count data. Shortest log period is one-minute intervals, default is 15 minutes. The REST API can be used to pull data directly from device or from Estate Manager if available.
• HTTP Post. This is where the Vector actively sends the logged data without software having to request it.
• MQTT. This is also where the Vector actively sends data, but MQTT is designed for real-time data and instead of sending the logged count data it will send the values as they change. This means you get data within 1-2 seconds of the change occurring. Note that because the PIR register can increase rapidly and consistently as and when people are detected, this can cause a lot of MQTT messages to be generated. An MQTT ‘broker’ is required.
• BACnet. For pulling the data into a BACnet controller.
• For completeness, there are also relay outputs when the optional USB-IO module is connected. If you want to output the PIR count increments via relay pulses, a USB hub will be required so that both USB devices can be connected to the Vector at the same time. Using relays to output the PIR increments is not recommended due to the number of counts increments that could be generated during periods of activity in the room.