Battery Level Monitoring - [Yabby3]
Table of Contents
The Yabby3 has in-built battery monitoring capabilities. It is critical to any application that:
- The batteries last long enough so that frequent changes are not necessary
- Low battery alerts are sent in a timely manner - so that battery changes can be made before batteries run flat.
The Yabby3 should be used with either of the below battery types
- Lithium Iron Disulphide (LiFeS2)
- Alkaline (can be used but not recommended)
See Battery Recommendations [Yabby3] for detail on selecting the right batteries.
The differences in battery chemistry mean the battery monitoring approach is slightly different for each type.
However, the firmware takes care of all of this for us, across all DM device types, and simply sets flags in the payload which we can alert on.
Setting up Low Battery Alerts
Information about editing parameters is available → OEM Server - Getting Started
The below are already configured by default - so we don't need to go make any changes, or configure anything unless we have special requirements.
Battery Good + Battery Critical Flags
The device keeps two battery 'flags':
Battery Good Digital Input
- Mapped to Digital Input 1 by default.
- Also appears as Bit 1 in the Device Status Flags
- Active '1' when the voltage is above the Battery Low Threshold - and inactive '0' when below this threshold.
Battery Low Threshold
If Battery Chemistry is set to AutoDetect and the Battery Low Threshold parameter set to 0, on startup, the device records the initial battery voltage, and works out if LiFeS2 or Alkaline batteries have been inserted.
Then, the battery low thresholds for each battery chemistry are as follows:
- LiFeS2 - 4.65V
- Alkaline - 3.6V
For LiFeS2 and Alkaline, the battery voltage (Analogue 1), and voltage used in the threshold is reported as the maximum voltage seen over a 3 day period. This is because battery voltages do bounce around somewhat and this provides some averaging. Additionally the different chemistries have different discharge profiles which require different measurement methods.
We can adjust the thresholds if desired by changing the Battery Chemistry dropdown and setting a value in mV for the Battery Low Threshold. This is typically not required, only change if you know what you are doing.
Battery Critical Digital Input
- Mapped to Digital Input 2 by default
- Also appears as Bit 5 in the Device Status Flags
- Active '1' if a brownout occurs.
- On the Yabby3 - this is if the voltage ever dips below 3V - which is too low to properly power the device. If this occurs - it is because the batteries are on their last legs, and need to be replaced immediately! The device needs at least 3V to operate.
The above flags mean we have 3 distinct states
|Battery Good (DI 1 + Status Bit 1)||Battery Critical (DI 2 + Status Bit 5)||Meaning|
|1 = On||0 = Off||Battery is OK, no action needs to be taken|
|0 = Off (cleared)||0 = Off||The battery is running low, and preparations should be made to replace batteries soon|
|0 = Off (cleared)||1 = On||The battery needs replacing ASAP|
Alerts in 3rd Party Platforms
We simply can configure the system to alert based on the status on Digital Inputs 1 and 2. Or the Status Flags.
It may be desirable to use the Status Flags as they are fixed across devices and cannot be remapped via parameter changes like the Digital Inputs Can.
- If Digital Input 1 / Status Bit 1 is cleared (1 -> 0) - send a Battery Low Alert
- If Digital Input 2 / Status Bit 5 is set (0 -> 1) - send a Battery CRITICAL Alert.
Alerts/Battery Level Report in Telematics Guru
Low Battery Alert
Create an Alert via Admin -> Alerts and use the Wizard.
Select the Low Battery alert and follow the prompts to set up this alert. This creates an alert on the Battery Good DI automatically.
Battery Critical Alert
Create an Alert via Admin -> Alerts and select New Alert (Advanced). When setting up the alert, set the following conditions on the Conditions tab (an alert when Digital Input is active)
Partner Battery Level Status Report
The Partner Battery Level Status report can be run to give an overview of the current battery status of all assets across a partner. It can be limited to an organization or device type additionally.
See the link Partner Battery Level Status Report for more information.
Battery Monitoring in OEM
OEM Battery Report
A battery low/critical report can be exported via OEM. This report details devices that have had the battery good flag unset and details if in a low or critical state. See OEM Battery Low/Critical CSV Export for more information.