Hi, For a solar-powered, deep sleep application on my Boron LTE device, I am pushing Li battery state up to the cloud read from FuelGauge::getVCell() and FuelGauge::getSoC(). I noticed that in the connection handshake, one of the items pushed is a battery status (that gets reported in the console).…

The 81% reading is the “raw” value where aprox. 86-89% is the maximum that can be reached even with a “fully” charged LiPo (due to the way how the SoC is calculated by the fuel gauge) and the cloud then applies some “normalisation” to map the raw 0…90% onto a 0…100% scale.

Here's a previous post that coincides with @ScruffR 's explanation above : [image] State of Charge Values Troubleshooting I believe the Device Vitals assume that the default Li-Po termination voltage of 4.112 V is used. The Fuel Gauge reports the actual SOC depending on th…

Battery level mismatch?

Troubleshooting

Rftop August 7, 2019, 4:54pm 3

Here's a previous post that coincides with @ScruffR's explanation above :

Topic		Replies	Views
State of Charge Values Troubleshooting	6	1252	April 2, 2019
Particle console Battery Charge vs. getSOC() Cloud	2	580	September 2, 2020
fuel.getSoC() return 22% of car battery fully charged Hardware	5	350	September 14, 2022
State of charge (SoC) decreases dramatically around the half way through? General	17	2648	September 2, 2016
SoC returns 0.00 at times (bsom eval board) Hardware boron	12	1027	November 19, 2021

Battery level mismatch?

Related topics