In the PULSE sensor (APP version 2.0.0 and later) redundancy can be set.
Redundancy is a mechanism to repeat data from one frame to another. Thus, in case of frame loss (e.g. network coverage limit), some information is recovered in the next frame. This mechanism reduces the risk of data loss and increases the overall reliability of the solution.
Based on the same principle as the historisation operation, redundancy allows this time to add in the frame samples which have already been transmitted previously and which are not part of the observation period of the frame in question.
This is why we will find in the frame the new indexes which have been observed over the period defined by the historisation and the previous indexes defined by the redundancy.
Example of the PULSE V3 operating parameters in history + redundancy:
I wish to read the index value of my meter every hour, transmit this information every 6 hours and have 6 redundant readings in case of loss of frame (i.e. the samples of the previous frame).
From the IoT Configurator (downloadable from https://www.adeunis.com/en/device-management-2/sensor-setup/):
- go to the "Application Configuration" menu,
- then "Global Configuration",
- the parameters to be applied are:
- "Acquisition period" = 1800 ; the transmitter will make an index reading every hour (1800(*2s) = 3600s = 1h),
- "Transmission frequency" = 6; the transmitter will send the frame every 6 hours (6x3600s = 6h, i.e. 4 frames per day),
- "Redundancy" = 6; the transmitter will add the previous 6 samples to the frame (so the frame will cover the last 12 hours).
The PULSE will therefore transmit one frame every 6 hours with 6 new index values and 6 redundant values (i.e. the frame will cover the last 12 hours).
- in LoRaWAN, the maximum number of index histories is 23 per channel,
- in sigfox, it is 4 per channel.
If you set up redundancy, then the number of historized samples (S301) + the number of redundant samples (S340) must be strictly less than 23 for a LoRaWAN product and strictly less than 4 for a Sigfox product. The configuration inconsistency bit will be lit in the PULSE frame status byte if the selected configuration exceeds the total number of samples supported by the product and therefore samples are lost.