Batt'O

Presentation


Batt'O is adapted to battery monitoring, it periodically transmits on the LoRaWAN network the measurements of the battery charge voltage and the current entering or leaving the battery. The remote application can thus calculate the current state of charge of the battery.

Technically the sensor measures a charge voltage until 70V and a shunt voltage measure of 100mV. Each input is isolated from the other.

To measure the load current, the shunt must be adapted to the intensity of the electric current flowing in the conductor. (exemple of shunt : Shunts (rs-online.com))

Family code:

The family code of Press'o devices is: 50-70-141

Electronic specification

0 – 70 Volts Measure

  • voltage until 70V
  • precision +-70mV
  • resolution on 12bit : 17mV
  • available on a 1.5m wire [AWG 20-26]
  • spotting label

0-100 mVolts Measure

  • galvanic isolated input
  • precision +-1mV
  • resolution 12bit
  • available on a 1.5m wire [AWG 20-26]
  • spotting label
  • any voltage above 1V is destructive

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 housing is compatible with the following DIN rail adapter:

din

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 2 cable glands, which 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 periodicityBattery life
2 frames/ 24 hours10 years

Human Machine Interface


The Batt’O sensor has a buzzer that allows it to “communicate” with the user.

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 buzzer rings quickly.

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 buzzer rings quickly during this step. After this second, the buzzer stops and rings 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 rings 5 times slowly.

The table below describes the actions to be performed on the reed switch to disable or enable the storage mode.

Action
Magnet
Buzzer
Switch ON
(disable storage mode)
1 second
Switch OFF
(enable storage mode)
5 seconds

When the sensor is trying to associate with a network, it emits the following sound:

Once the association is completed, the buzzer makes the following sound:

A reed switch (or magnetic switch) is available. A magnet can be used to activate it and perform specific actions on the sensor (switch off, switch on, reassociation…).

  • Configuration: "void" frames are sent every minute for 10 minutes.

Standard reports are disabled in this mode.

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 sensor
DurationThe 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 itThree passages of the magnet near the reed switch or ZCL command from LoRaWAN cluster.
Effects on the sensor
  • 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.

Factory reset
Way to trigger itTwo quick passages and a very long passage (until the sensor rings for the reset) of the magnet near the reed switch
Effects on the sensor

Applicative layer


Codecs are available to decode frames: Downloads

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

End PointClusterUnit
0Analog Input [0-100mV] mV
1Analog Input [0-70V] mV

Batt'O integrates threshold and actions on threshold. It manages until 10 differents actions. (configuration action)

Batt'O  integrates the following clusters:

ClusterCluster name Managed attributes
0x0000 BasicAll
0x0050ConfigurationAll
Threshold is available with 3 slots
0x8004LoRaWANAll
0x000CAnalog InputAll
Threshold is available with 6 slots

Default configuration

A default configuration is set:

  • The device reports the 0-100 mV value (EndPoint 0 / Cluster Analog Input / Attribute PresentValue) and the 0-70V value (EndPoint 1 / Cluster Analog Input / Attribute PresentValue) every 24 hours.

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).

Measurement periodicity

The measurement periodicity depends on the minimum recording interval.

If the value of the minimum is 0, then the periodicity is 1 second.

If the value of the minimum is different than 0, then this value is the same as the periodicity.

Frame examples


All frames have to be sent on port 125

Standard report

Report

Report of the analog value of connector 4-20mA

→ Applicative payload is: 11 0a 00 0c 00 55 39  41 50 00 00

11: Fctrl (Endpoint=0)

41 50 00 00: present value ( single precision value =>13.0 mA)

 

Report of the analog value of connector 0-10V

→ Applicative payload is: 31 0a 00 0c 00 55 39  46 14 d0 00

31: Fctrl (Endpoint=1)

46 14 d0 00: present value ( single precision value =>9524.0 mV)

 

Configuration

Configure a standard report on the 0-100 mV input

Report immediately the measurement of the 0-100 mV input on a 1mV variation. The measurement has to be reported at least every hour, and the measurement has to be made every 10 minutes.

→The 0-100mV is the End Point 0, Cluster “Analog Input” is 0x000c, Attribute “PresentValue” is 0x0055. The maximum field has to be 0x803c to have a report every one hour and the minimum field has to be 0x800a to have a measurement every 10 minutes. The delta has to be configured to 0x3f800000 for a report every 1 mV variation.

Applicative payload is: 11 06 00 0c 00 00 55 39 80 0a 80 3c 3f 80 00 00

11: Fctrl (Endpoint=0)

80 0a: minimum reporting interval (10 minutes)

80 3c: maximum reporting interval (1 hour)

3f 80 00 00: reportable change ( 1mV in single precision)

→Response:11 07 00 0c 00 00 00 55

To disable the previous configuration, change the value of the minimum and maximum sending intervals and the delta to 0: 11 06 00 0c 00 00 55 39 00 00 00 00 00 00 00 00

or you can use remove report command.

 

Configure a standard report on the 0-70V input

Report immediately the measurement of the 0-70V input on a 5V variation. The measurement has to be reported at least every hour, and the measurement has to be made every 10 minutes.

→The 0-70V is the End Point 1, Cluster “Analog Input” is 0x000c, Attribute “PresentValue” is 0x0055. The maximum field has to be 0x803C to have a report every one hour and the minimum field has to be 0x800a to have a measurement every 10 minutes. The delta has to be configured to 0x459c4000 for a report every 5000 mV variation.

Applicative payload is: 31 06 00 0c 00 00 55 39 80 0a 80 3c 45 9c 40 00

31: Fctrl (Endpoint=0)

80 0a: minimum reporting interval (10 minutes)

80 3c: maximum reporting interval (1 hour)

45 9c 40 00: reportable change ( 5000mV in single precision)

→Response:31 07 00 0c 00 00 00 55

To disable the previous configuration, change the value of the minimum and maximum sending intervals and the delta to 0: 31 06 00 0c 00 00 55 39 00 00 00 00 00 00 00 00

or you can use remove report command.

 

Configure a threshold on the 0-100mV input

Report immediately the measurement of the 0-100mV  Input when measure exceeds or falls a threshold of 10 mV with an hysteresis of +-1mV. The measurement has to be reported at least every hour, and the measurement has to be made every 10 minutes.

→The 0-100mV is the End Point 0, Cluster “Analog Input” is 0x000c, Attribute “PresentValue” is 0x0055. The maximum field has to be 0x803C to have a report every one hour and the minimum field has to be 0x800a to have a measurement every 10 minutes.

Applicative payload is: 11 06 000c 80 0055 39 800A 803C 70 41200000 3f800000 01

11: Fctrl (Endpoint=0)

80: new format frame

80 0a: minimum reporting interval (10 minutes)

80 3c: maximum reporting interval (1 hour)

70: criteria slot 0, Threshold, No Alarm, OnExceed, OnFall

41200000: threshold of 10 mV

3f800000: hysteresis of 1 mV

01: number of occurences over the threshold before a report will be sent

→Response:11 07 00 0c 00 00 00 55

To disable the previous configuration, change the value of the minimum and maximum sending interval and the delta to 0: 11 06 00 0c 00 00 55 39 00 01 02 03

or you can use remove report command.

 

Batch report

Below the preconised configuration for batch:

Label (size = 3) resolution
0-100 mV 0 0.02 [mV]
0-70V 1 17 [mV]
Battery Level 2 100 [mV]
External Power Level 3 100 [mV]
  • Use codec online to configure a batch:

Under construction

  • Uncompress the batch with codec inline or with codec sources with the following argument:

Under construction -a 3 0,0.02,12 1,17,12 2,100,6 3,100,6

Print Friendly