Pulse Sens'O sensor

 

 

Declaration of conformity

---

Download the declaration of conformity

Presentation

---

The Pulse Sens'O sensor is a LoRaWAN class A sensor that uses a disposable 3.6V A-type battery as power supply.

The Pulse Sens'O sensor incorporates 3 digital inputs, and also includes an internal antenna.

The level or a counter can be transferred to the different inputs. It is also possible to get the voltage of the power supply.

There is an ATEX version of the Pulse Sens'O, which is designed to be used in an explosive atmospheres.

Family code

The family code of Pulse Sens'O devices is: 50-70-014-xxx

The family code of Pulse Sens'O ATEX devices is: 50-70-072-xxx

The family code of Pulse Sens'O IP68 devices is: 50-70-039-xxx

The family code of Pulse Sens'O IP68 ATEX devices is: 50-70-051-xxx

Electronic input

The schematic of the different inputs of the Pulse Sens'O sensor is illustrated below:

Electrical schematic example for inputs

→ Due to software limitation, the maximum frequency is 100 Hz on each input.

Installation and operation

---

Installation

The housing is intended to be installed inside or outside a building but it must be protected from vertical water spray and direct sunlight.

1- Pulse Sens'O / Pulse Sens'O ATEX

The product is delivered disassembled. This enables the connection to the screw terminals.

Before connecting your cable strands to the product’s screw terminals, you must insert the cable gland's nut and the seal.

Then connect the wires to the Inputs that will be used:

For the connectors, we recommend using several 20-26 AWG single wires. As the connectors pinch the wires plugged inside approximately 4mm from the wire end, strip the wires over a length of approximately 5 to 6mm before plugging them into the connectors.

Once the assembly is complete, the casing can be closed.

The housing is compatible with the following DIN rail adapter:

For more information about the casing, please visit: www.spelsberg.com

2- Pulse Sens'O IP68 / Pulse Sens'O IP68 ATEX

This product is delivered with the cables connected to its inputs, together with the magnet used with the reed switch.

The cables are connected according to the following table:

Wire colour	Connector
green	Input 1+
white	Input 1-
brown	Input 2+
pink	Input 2-
blue	Input 3+
yellow	Input 3-

The sensor is protected (IP68) up to the point where the cable splits into three wires, as shown below:

Casing

Flammability rating: UL94HB

Ingress protection: IP68, 48 hours @1m

Radio propagation

In order for the sensor to operate correctly, the number of obstacles should be limited in order to avoid excessive radio wave attenuation. It is also important to place the sensor as high as possible. The cable gland should be positioned downward.

Fludia sensor compatibility

The Fludia sensor "BelSenso FM230m" is compatible with the Pulse Sens'O.

Connect one of the inputs of the Pulse Sens'O to the output of FM230m according to the polarity.

Autonomy

---

The information in the table below represents how long the battery can last. It is  based on the default configuration at ambient temperature (+25°C) within the optimal operating range of the sensor via a LoRaWAN network (one uplink frame), when the spreading factor used is SF12.

The disposable battery has a 3.6Ah capacity, of which 85% is used.

Transmission periodicity	Repetition	Spreading Factor	Battery life
12h	0%	SF12	>10 years
4h	0%	SF12	>10 years
4h	200%	SF12	>10 years
2h	0%	SF12	>10 years
1h	0%	SF12	>8 years
1h	200%	SF12	>3 years
1h	200%	SF9	>10 years

A value of 3µA of consumption is added per input connected (contact closed).

Human Machine Interface

---

There are three LEDs on the Pulse Sens'O device:

ASSN:      blinking until the association with a network is done.

FNC:     blinking every minute while an input is activated.

CNF:     blinking in configuration mode.

1- Pulse Sens'O / Pulse Sens'O ATEX

Once the device is installed, switch ON the power.

• A user button is available to enter the configuration mode. "Void" frames are then sent every minute for 10 minutes.

Standard reports are disabled in this mode.

Configuration mode
Way to trigger it	One press on the USER button or specific ZCL command
Way to stop it	Another press on the USER button or specific ZCL command
Effects on the sensor	The CONF led (red) blinks (3 sec. OFF, 3 sec. ON) and the sensor sends an uplink frame every minute. The blinking is illustrated below this table.
Duration	The configuration mode lasts 10 minutes when it is triggered by pressing the USER button

• A reassociation procedure can be requested if no downlink frame is received by the sensor during a given periodicity (4 days by default) or if a given number (100 by default) is reached or in case of failure (no acknowledgement received) by sending an applicative frame to the sensor or via the sensor’s IHM.

The sensor keeps the AppEUi and DevAddr configured, Confirmed/Unconfirmed configuration and all applicative configurations. However, LoRaWAN configurations (channel, data rate…) are lost.

ReAssociation Mode
Way to trigger it	Three short presses on the USER button or ZCL command from LoRaWAN cluster.
Effects on the sensor	The ASSO LED (green) blinks as the “no commissioned sensor” LED is lit.

• A factory reset is available on Watteco’s sensors. It deletes all the applicative settings saved in the flash memory (i.e. configured batches and reports will be deleted).

The sensor keeps the AppEUi and DevAddr configured. However, LoRaWAN configurations (channel, data rate…) and applicative configurations are lost.

Factory reset
Way to trigger it	Two short presses and one long press for approximately 7 seconds on the USER button.
Effects on the sensor	The CONF LED (red) and ASSO LED (green) blink at the same time briefly. All the applicative settings (for batches and reports) are deleted. The blinking is illustrated below this table.

2- Pulse Sens'O IP68 / Pulse Sens'O IP68 ATEX

To start up the device, a magnet must be placed next to the sensor for one second (to the left of the cable gland). The red LED blinks quickly during this step. After one second, the red LED stops blinking and the green LED blinks slowly until the association is done.

To switch off the device, repeat the same operation by placing the magnet next to the sensor for 5 seconds. After those 5 seconds, the red LED blinks 5 times slowly.

A reed switch is available under the sticker. A magnet can be used to activate it and perform specific actions on the sensor (switch off, switch on, reassociation…). When the reed switch is activated, the red LED blinks quickly.

• Configuration

Configuration mode
Way to trigger it	One passage of the magnet near the reed switch or specific ZCL command
Way to stop it	Another passage of the magnet or specific ZCL command
Effects on the sensor	The CONF led (red) blinks (3 sec. OFF, 3 sec. ON) and the sensor sends an uplink frame every minute.
Duration	The configuration mode lasts 10 minutes

• A reassociation procedure can be requested if no downlink frame is received by the sensor during a given periodicity (4 days by default) or if a given number (100 by default) is reached or in case of failure (no acknowledgement received) by sending an applicative frame to the sensor or via the sensor’s IHM.

The sensor keeps the AppEUi and DevAddr configured, Confirmed/Unconfirmed configuration and all applicative configurations. However, LoRaWAN configurations (channel, data rate …) are lost.

ReAssociation Mode
Way to trigger it	Three passages of the magnet near the reed switch or ZCL command from LoRaWAN cluster.
Effects on the sensor	The ASSN led (green) blinks as the “no commissioned sensor” LED is lit.

• A factory reset is available on Watteco’s sensors. It deletes all the applicative settings saved in the flash memory (i.e. configured batches and reports will be deleted).

The sensor keeps the AppEUi and DevAddr configured. However, LoRaWAN configurations (channel, data rate…) and applicative configurations are lost.

Factory reset
Way to trigger it	Two quick passages and a long passage of the magnet near the reed switch
Effects on the sensor	The CONF LED (red) and ASSN LED (green) blink at the same time briefly. All the applicative settings (for batches and reports) are deleted. The blinking is illustrated below this table.

Applicative layer

---

Codecs are available to decode frames: Downloads

The Pulse Sens'O device implements “Binary Input” cluster associated to its Inputs. The link between the connectors and the EndPoint is given below:

Connector	End Point	Cluster	Fctrl
Input 1+/1-	0	Binary Input	11
Input 2+/2-	1	Binary Input	31
Input 3+/3-	2	Binary Input	51

Pulse Sens'O integrates the following clusters:

Cluster	Cluster name	Managed attributes
0x0000	Basic	All
0x0050	Configuration	All
0x000F	Binary Input	All
0x8004	LoRaWAN	All
0x8005	Multi Binary Inputs	All

Default configuration

A default configuration is set:

• The device reports each day the counter value associated with input 1+/1- (EndPoint 0 / Cluster Binary Input / Attribute Count), input 2+/2- (EndPoint 1 / Cluster Binary Input / Attribute Count), and input 3+/3- (EndPoint 2 / Cluster Binary Input / Attribute Count).

Every change made to the default configuration must comply with the legal duty cycle (for example, the most restrictive in the EU is 0.1%, which corresponds to approximately 1 frame per hour with SF12)

Frame examples

---

All frames have to be sent on port 125

Standard report

Report

Report of the state of connector input 1+/1-

 

Report the counter associated to connector input 2+/2-

 

Configuration

Configure a standard report on the state of connector input 3+/3-

 

Configure a standard report on the counter associated to connector input 1+/1-

 

Configure the polarity on connector Input 1+/1-

 

Configure the edge selection on connector Input 1+/1-

 

Configure the debounce period on the connector 3+/3-

 

Batch report

Configuration

• Configure a batch report on connector input 2+/2- and connector input 3+/3-:

Timestamp and record Input 2+/2- every 200 pulses; and timestamp and record the level of Input 3+/3-. A report has to be sent at least every 24 hours:

→A counter on Input 2+/2- is the End Point 1, Cluster “Binary Input” is 0x000F, and Attribute “Count” is 0x0402.

A level on Input 3+/3- is End Point 2, Cluster “Binary Input” is 0x000F, and Attribute “Present Value” is 0x0055.

There are two different measurements to be recorded in the batch, so the tag size has to be 1. Label 0 can be used for counter and Label 1 for level.

For counter, the delta is 200 and resolution 1. For level, the delta is 1 and resolution 1. The maximum has to be configured for all to 0x850a.

Two frames must be sent to configure this batch.

Label number	Tag label	Tag size
1 or 2	0/1	1
3 or 4	00/01/11/10	2
5 or 6 or 7 or 8	000/001/010/011/100/101/110/111	3
...	...	...

Applicative payload of the count on input 2+/2-

 

Applicative payload of the present value of input 3+/3-

 

To decode the batch reception, use br_uncompress. Type for binary input attribute counter is U32 (10), Type for binary input attribute PresentValue is Boolean (1), so the following command must be used:

echo “ 26100040405e7692050000004006 ” | br_uncompress -a 1   0,1,10   1,1 ,1

Result

DECOMPRESSION SERIES

cnt: 7   #  Batch counter (from 0 to 7)

5778    # Timestamp in seconds of sending of the frame

#Format of data is: Timestamp of Measurement | Label | Value

5689 0 0     # Timestamp: 5689 s                                Label 0                  Value: 0

5777 1 1     # Timestamp: 5777 s                                Label 1                  Value: 1

• Configure a batch report on binary input counter on connector 1+/1- and voltage battery:

Timestamp and record the pulses counter with a resolution of 1, a value has to be saved at least every 30 minutes or on a rise of 50 pulses. Timestamp and record the battery voltage with a resolution  of 0.1V, a value has to be saved at least every 24 hours. All data have to be concatenated and sent every 24 hours at the most.

→The solution to concatenate several different physical values in the same frame is to use batch reporting.

For the batch, the number of physical measurements that will be sent must be known in order to choose a label for each of them and the size of these labels.

As mentioned in the previous paragraph, we will have only two kinds of measurements to manage, thus two different labels. The tag size to be used for two labels is 1. Label 0 can be used for binary input counter and label 1 for the disposable battery level.

Two frames must be sent to configure this batch.

A counter on Input 1+/1- is the End Point 0, Cluster “Binary Input” is 0x000F, and Attribute “Count” is 0x0402.

The battery voltage: Cluster "Configuration" is 0x0050, and attribute "Node power descriptor" is 0x0006.

Applicative payload of the count on input 1+/1-

 

Applicative payload of battery voltage

 

To decode the batch reception, use br_uncompress. Type for binary input counter is U32 (10) and U16 (6) for the disposable battery power, so the following command must be used:

echo "26150020e06001d71e0000a0650f" | ./br_uncompress -a 1 0,1,10 1,100,6

Result:
DECOMPRESSION SERIES

cnt: 5   #  Batch counter (from 0 to 7)

263    # Timestamp in seconds of sending of the frame

#Format of data is: Timestamp of Measurement | Label | Value

263 0 45     # Timestamp: 841 s                                   Label 0: counter pulse                          Value: 45

263 1 3000     # Timestamp: 811 s                                Label 1: Disposable battery                 Value: 3.0V