Flash'O sensor
Declaration of conformity
Download the declaration of conformity
Presentation
Flash'O is a LoRaWAN class A sensor. It is a meter radio interface that transmits the cumulated flash LED values from any pulse meters: water, gas, electricity, energy. The sensor is connected to an optical probe that recovers light pulses.
The Flash'O sensor is powered by a disposable 3.6V A-type battery. It incorporates one digital input, and also includes an internal antenna.
The level or a counter can be transferred to the input. It is also possible to get the voltage of the power supply.
Compatibility notice between ENEDIS meters and TIC or Flash’'O sensors (in French)
Family code
The family code of Flash'O devices is: 50-70-071-xxx
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.
The optical probe is easily attached using either magnets or velcro strips. The cable length is approximately 0.5m.
The housing is compatible with the following DIN rail adapter:
For more information about the casing, please visit: www.spelsberg.com
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.
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 | Battery life |
|---|---|
| 1 frame/ 24 hours | +15 years |
Human Machine Interface
There are three LEDs on the Flash'O device:
ASSO: blinking until the association with a network is done.
FNC: blinking every minute while an input is activated.
CONF: blinking in configuration mode.
Once the device is installed, switch the power ON.
- 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.
| 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.
| 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 nke 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.
| 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. |
.
Applicative layer
Codecs are available to decode frames: Downloads
Flash'O incorporates the following clusters:
| Cluster | Cluster name | Managed attributes |
|---|---|---|
| 0x0000 | Basic | All |
| 0x0050 | Configuration | All |
| 0x8004 | LoRaWAN | All |
| 0x000F | Binary Input | 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).
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 present value of connector input 1+/1-
Configuration
Configure a standard report on connector input 1+/1-
Batch report
Configuration
• Configure a batch report on binary input counter of 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.
| 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 |
| ... | ... | ... |
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 the 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
Known Issues
- Binary Input batch:
- Version: V3.5.2.5358.5408, V3.5.2.5466.0, V3.5.2.5466.5514
- Issue: Counting Indexes are always to 0 in batch report.
- Workaround: Set a standard report on each input on which a counting is necessary:
- Input 1: 1106000f000402230000fffe00000000 => send a standard report all the 22 days
- Input 2: 3106000f000402230000fffe00000000 => send a standard report all the 22 days
- Input 3: 5106000f000402230000fffe00000000 => send a standard report all the 22 days
