Pulse Sens’o

Pulse Sens’o sensor

 

Declaration of conformity


Download the declaration of conformity

Presentation


The Pulse Sens’o  sensor is LoRaWAN class A sensor, it uses a disposable A 3.6V battery as power supply.

The Pulse Sens’o sensor integrates 3 digital inputs. It  also includes an internal antenna.

It is possible to report the level or a counter on 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, it is designed to be used in an explosive atmosphere.

pulse-sens%27o

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

 

pulse_inputs

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

Installation and use


Installation

The housing is intended to be installed inside or outside a building but to the shelter of a vertical splash water 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.

cable-gland2

Then connect wires on Inputs  that will be used:

pulse_carte

For connectors, it is preferable to use several single wires with a gauge of 20-26 AWG. As the connectors pluck the wires plugged inside at about 4mm of the wire-end , strip the wires on about 5 to 6 mm of their extremity before plugging them into the connectors.

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

The housing is compatible with the following DIN rail adapter:

din

For more information about the casing, 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, and also the magnet to use with the reed switch.

The cables are connected following the table below:

Wire colorConnector
greenInput 1+
whiteInput 1-
brownInput 2+
pinkInput 2-
blue Input 3+
yellowInput 3-

The sensor is protected (IP68)  until the separation into three wires as shown below:

pulse_ip68_wiring

Casing

Combustion behaviour: UL94HB

Ingress protection: IP68 48hours@1m

Propagation radio

In order for the sensor to function correctly, it is better to limit the number of obstacles in order to avoid excessive attenuation of the radio wave, it is also important to put the sensor as high as possible. The cable gland should be positionned downward.

propagation-radio-pulse

Fludia sensor compatibility

fludia

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 depending on the polarity.

fludia_connection

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 use of the sensor throught LoRaWAN network (one uplink frame), and when  the spreading factor used is SF12.

The capacity of the disposable battery is 3.6Ah, 85% of it is used.

Transmission periodicityBattery lifeBattery life (Input closed contact)
3 frames / 24 hours+15 years+15 years

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

Human Machine Interface


There are three leds on the Pulse Sens’o device:

ASS:      blinking until the association to a network is done.

association

FNC:     blinking each minute while an input is activated.

CNF:     blinking in the configuration mode.

1- Pulse Sens’o/ Pulse Sens’o Atex

After installing the device, switch ON the power.

• A user button is available to enter in configuration mode, « void » frames are then sent every minute for 10 minutes.

Standard reports are not functioning during this mode.

Configuration mode
Way to trigger itOne 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 sensorThe 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.
Time durationThe configuration mode lasts 10 minutes when it is triggered by pressing the USER button

4

  • It is possible to ask a ReAssociation procedure if no down frame is received by the sensor during a given periodicity (4 days by default) or if a given number (100 by default) or failure (no acquittement is received) are reached by sending an applicative frame to the sensor or by the IHM of the sensor.

The sensor keeps the AppEUi and DevAddr configured, Confirmed/Unconfirmed     configuration and all applicative configurations. On the other hand, LoRaWAN configuration (channel, datarate …) are lost.

ReAssociation Mode
Way to trigger itThree short press on the USER button or ZCL command from LoRaWAN cluster.
Effects on the sensorThe ASSO led (green) blinks as the “no commissioned sensor” led lightning.
  • A factory reset is available on nke Watteco’s sensors. It deletes all the applicative settings saved in the flash memory (i.e.: the configured batches and reports will be deleted).

The sensor keeps the AppEUi and DevAddr configured. On the other hand, LoRaWAN configurations (channel, datarate …) and applicative configurations are lost.

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

5

2- Pulse Sens’o IP68/ Pulse Sens’o IP68 Atex

To Start-up the device, it is necessary to put a magnet on the  side of the sensor during one second (at the left side of the cable gland). The red Led blinks quickly during this step. After this second, the red led stops blinking and the green led blinks slowly until the association is done.

To switch off the device, use the same way by putting the magnet during 5 seconds. After this amount of time, the device blinks red 5 times slowly.

ip68_reed_switch

A reed switch is available under the sticker. It is possible to use a magnet to activate it and makes specific actions on the sensor (Switch off, switch on, Re-associtation…). When the reed switch is activated, the red led blinks quickly.

  • Configuration
Configuration mode
Way to trigger itOne 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 sensorThe CONF led (red) blinks (3 sec. OFF, 3 sec. ON) and the sensor sends an uplink frame every minute.
Time durationThe configuration mode lasts 10 minutes
  • It is possible to ask a ReAssociation procedure if no down frame is received by the sensor during a given periodicity (4 days by default) or if a given number (100 by default) or failure (no acquittement is received) are reached by sending an applicative frame to the sensor or by the IHM of the sensor.

The sensor keeps the AppEUi and DevAddr configured, Confirmed/Unconfirmed  configuration and all applicative configurations. On the other hand, LoRaWAN configuration (channel, datarate …) are lost

ReAssociation Mode
Way to trigger itThree passages of the magnet near the reed switch or ZCL command from LoRaWAN cluster.
Effects on the sensorThe ASSO led (green) blinks as the “no commissioned sensor” led lightning.
  • A factory reset is available on nke Watteco’s sensors. It deletes all the applicative settings saved in the flash memory (i.e.: the configured batches and reports will be deleted).

The sensor keeps the AppEUi and DevAddr configured. On the other hand, LoRaWAN configurations (channel, datarate …) and applicative configurations are lost.

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

 

Applicative layer


Codec are available to decode frame: Downloads

The Pulse Sens’o device implements “Binary Input” cluster, associated to its Inputs. The corresponding between the connectors and the EndPoint is done below:

ConnectorEnd PointClusterFctrl
Input 1+/1-0Binary Input11
Input 2+/2-1Binary Input31
Input 3+/3-2Binary Input51

Pulse Sens’o  integrates the following clusters:

ClusterCluster nameManaged attributes
0x0000BasicAll
0x0050ConfigurationAll
0x000FBinary InputAll
0x8004LoRaWANAll
0x8005Multi Binary InputsAll

Default configuration

A default configuration is set:

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

Every change on the default configuration must respect the legal duty cycle. (For example the most restrictive in EU is 0.1%, so in SF12 it is around 1 frame each hour)

Frame examples


Standard report

Report

 

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

→ Applicative payload is: 11 0a 00 0f 00 55 10 01

11: Fctrl (Endpoint=0)

 01: current binary value

 

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

→Applicative payload is: 31 0a 00 0f 04 02 23 00 00 00 01

31: Fctrl (Endpoint=1)

 00 00 00 01: current value of the counter

 

Configuration

 

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

Report the state of the connector Input 3+/3- at each variation. The value has to be reported at less each 15 minutes, and a minimal timing of 20 seconds between 2 reports has to be settled to optimize the consumption:

→The value on Input 3+/3- is the End Point 2, Cluster “Binary Input” is 0x000F, and Attribute “present value” is 0x0055. The maximum field has to be 0x800F to have a report all 15 minutes and the minimum  field has to be 0x0014 to have a minimal timing between two reports. The delta has to be configured to 0x01 for a report at each variation.

 Applicative payload is: 51 06 00 0f 00 00 55 10 00 14 80 0f 01

51: Fctrl (Endpoint=2)

00 14: minimum reporting interval (20 seconds)

80 0f: maximum reporting interval (15 minutes)

01: reportable change (at each variation)

→Response: 51 07 00 0f 00 00 00 55

To disable the previous configuration, change the value of the minimum and maximum sending interval and the delta to 0: 51 06 00 0f 00 00 55 10 00 00 00 00 00

 

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

Report the counter all the 5 pulses on the connector Input 1+/1-. The counter has to be reported at least each 2 hours:

→A counter on Input 1+/1 is the End Point 0, Cluster “Binary Input” is 0x000F, and Attribute “Count” is 0x0402. The maximum field has to be 0x1c20 to have a report every  2 hours and the minimum field has to be  0x0000 to have a report immediately after the right incrementation. The delta has to be configured to 0x05 for a report all the 5 pulses.

Applicative payload is: 11 06 00 0f 00 04 02 23 00 00 1c 20 00 00 00 05

11: Fctrl (Endpoint=0)

00 00: minimum reporting interval (0 seconds)

1c 20: maximum reporting interval (2 hours)

00 00 00 05: reportable change (5 pulses)

→Response:11 07 00 0f 00 00 04 02

To disable the previous configuration, change the value of the minimum and maximum sending interval and the delta to 0: 11 06 00 0f 00 04 02 23 00 00 00 00 00 00 00 00

 

Configure the polarity on the connector Input 1+/1-

→Write attribute no response: 11 05 00 0f 00 54 10 nn

11: Fctrl (Endpoint=0)

nn: current polarity of the sensor (normal : 00, reversed: 01)

 

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

→Write attribute no response: 11 05 00 0f 04 00 18 nn

11: Fctrl (Endpoint=0)

nn: the current edge selection ( 01: falling edge, 02: rising edge, 03: rising and falling edge, 04: polling) 

 

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

→Write attribute no response: 51 05 00 0f 04 01 21 00 7D

51: Fctrl (Endpoint=2)

00 7D: debounce period (125 ms)

 

Batch report

Configuration

 

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

Timestamp and record the Input 2+/2- all the 200 pulses; and timestamp and record the level of the 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 measures to record 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 the resolution 1. The maximum has to be configured for all to 0x850a.

It is necessary to send two frames to configure this batch.

Number of labelTag labelTag size
1 or 20/11
3 or 400/01/11/102
5 or 6 or 7 or 8000/001/010/011/100/101/110/1113
.........

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

31 06 00 0f 1d 04 02 00 00 00 85 0a 00 00 00 c8 00 00 00 01 01 

31: Fctrl (Endpoint=1)

1d:  0b00011101 => 0001110: size of configuration string after attribute ID (14 bytes)

00 00: minimum recording interval (0 seconds)

85 0a: maximum recording interval (24 hours)

00 00 00 c8:  required delta value (size: 4 bytes for attribute Count => attribute type = 23, 200 pulses)

00 00 00 01: required resolution

01: tag value (ob00000001 => 00000: tag label, 001: tag size)

→Response: 31 07 00 0f 00 01 04 02

 

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

51 06 00 0f 11 00 55 00 00 00 85 0a  01  01 09 

51: Fctrl (Endpoint=2)

11: 0b00010001 => 0001000: size of configuration string after attribute ID (8 bytes)

00 00: minimum recording interval (0 seconds)

85 0a: maximum recording interval (24 hours)

01: required delta value (size: 1 byte for attribute PresentValue => attribute type = 10, 1 pulse)

01: required resolution

09: tag value (ob00001001=> 00001: tag label, 001: tag size)

→Response: 51 07 00 0f 00 01 00 55

 

To decode the batch reception, use the br_uncompress. Type for binary input attribute counter is U32 (10), Type for binary input attribute PresentValue is Boolean (1), so it is necessary to use this command:

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

Result

UNCOMPRESS SERIE

cnt: 7   #  Counter of the batch (from 0 to 7)

5778    # Timestamp in second of sending of the frame

#Format of data is: TimeStamp of Measure | 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 the 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 all the 24 hours. All data have to be concatenated and sent at  maximum all the 24 hours.

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

For the batch it is necessary to know the number of physical measures that will be sent in  order to choose a label for each of them and the size of these labels.

According to the previous paragraph, we will have only two kinds of measure to manage, thus two different  labels. The tag Size to use for two labels is 1. Label 0 can be used for binary input Counter and label 1 for the level of disposable Battery.

It is necessary to send two frames 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-

11 06 00 0f 1d 04 02 00 00 00 80 1e 00 00 00 32 00 00 00 01 01 

11: Fctrl (Endpoint=0)

1d:  0b00011101 => 0001110: size of configuration string after attribute ID (14 bytes)

00 00: minimum reporting interval (0 seconds)

80 1e: maximum reporting interval (30 minutes)

00 00 00 32:required delta value  (size: 4 bytes for attribute Count => attribute type = 23, 50 pulses)

00 00 00 01: required resolution

01: tag value (ob00000001 => 00000: tag label, 001: tag size)

→Response:11 07 00 0f 00 01 04 02

 

Applicative payload of voltage battery

11 06 00 50 15 00 06 04 80 0a 85 a0 00 64 00 64 09 

11: Fctrl (Endpoint=0)

15:  0b00010101 => 0001010: size of configuration string after attribute ID (10 bytes)

80 0a: minimum reporting interval (10 minutes)

85 a0: maximum reporting interval (24 hours)

00 64: required delta value (size: 2 bytes for attribute Node power descriptor => attribute type = 41, 100 pulses)

00 64: required resolution (0.1V)

09: tag value (ob00001001=> 00001: tag label, 001: tag size)

→Response:11 07 00 50 00 01 00 06

 

To decode the batch reception, use the br_uncompress. Type for binary input counter is U32 (10) and is U16 (6)  for the disposable battery power. So, it is necessary to use this command:

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

Result:
UNCOMPRESS SERIE

cnt: 5   #  Counter of the batch (from 0 to 7)

263    # Timestamp in second of sending of the frame

#Format of data is: TimeStamp of Measure | 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

Print Friendly