Battery Percentage Confused?

Author

Comment

josh

Junior Member
Registered:1439547885
Posts: 21

Posted 1440673884	Reply with quote #1

Hi, I have noticed that on 3 occasions now leaving the device to "turn off" without an atomiser on the device has turned back on with 5-10% battery left, charging makes no difference as it counts up... However, plugging it into escribe and uploading settings brings it back to 50-70% where it should have been... This is quite concerning as this could cause issues with charging causing quite a bad overcharge... Has anyone else experienced this? I have had this 3 times, with 2 different batteries... Steps already taken: Charged to 100% (12.6V) after setting the 11.66wh (1050, 3s 11.1v) I have been unable to replicate this issue consistantly

VapingBad

Administrator
Registered:1435398945
Posts: 2,449

Posted 1440674160	Reply with quote #2

It may take a couple of charge/discharge cycles for the device to learn the battery and the batter bar takes the wattage setting onto account so you should see the batter bar rise as you lower the wattage. __________________ • I am not employed by nor do I represent Evolv Inc. All opinions are my own, they are just opinion not fact and can be wrong • Latest versions of EScribe: DNA 200/250 • DNA 75 Common problems

josh

Junior Member
Registered:1439547885
Posts: 21

Posted 1440674408	Reply with quote #3

I have had about 10 cycles through the first battery so far, this percentage was before it had been fired, when i had fired it and when i was charging it... I just worry that it might overcharge causing an issue... Or if I'm out and about I can't vape until I get back to my PC!

VapingBad

Administrator
Registered:1435398945
Posts: 2,449

Posted 1440675036	Reply with quote #4

I doubt it would overcharge, the battery bar is just info from the charging system and meta data, the charging circuit will limit the max voltage feed to the battery. I would check the battery and balance connections for dry joints first and then the battery on a volt metre vs what the device/escribe read and if they all match I would suspect the battery, but just generic guesses. __________________ • I am not employed by nor do I represent Evolv Inc. All opinions are my own, they are just opinion not fact and can be wrong • Latest versions of EScribe: DNA 200/250 • DNA 75 Common problems

James

Administrator
Registered:1435637569
Posts: 304

Posted 1440675598	Reply with quote #5

josh, the actual charging code does not use the battery meter, just the cell voltages. It isn't a worry for overcharging. What firmware version are you running, out of curiosity? And does it only happen if there is no atomizer attached?

josh

Junior Member
Registered:1439547885
Posts: 21

Posted 1440675756	Reply with quote #6

Hi James, I am using the latest version 07/01. So far I have only witnessed this issue repeating itself with the atomiser removed... I have been so far unable to get a consistent re-occurrence

blueridgedog

Moderator
Registered:1435400230
Posts: 573

Posted 1440688790	Reply with quote #7

James: Is the chip still calculating a "remaining" graphic based on load/ohms of the atomizer?

scoopy

Member
Registered:1435623729
Posts: 310

Posted 1440704613 · Edited	Reply with quote #8

Josh.....that is not the newest firmware... .try the 8-21 early firmware ....its under the software and firmware/early firmware thread. ...I agree with VapingBad to check your solder joints and all battery and balance connections....also have a look at all the resistors around the balance port....see if any are missing or loose __________________

Vape_Like_A_Boss

Member
Registered:1436582665
Posts: 65

Posted 1441308688	Reply with quote #9

Quote: Originally Posted by josh Hi James, I am using the latest version 07/01. So far I have only witnessed this issue repeating itself with the atomiser removed... I have been so far unable to get a consistent re-occurrence That firmware was I believe right before the change to allow users to customize battery capacity. It was first set up in the firmware for the beta units which all had the same size battery, and when chips started being sold in the early adopters program they updated the firmware to be compatible with whatever battery was used. I bet updating your firmware will resolve a lot of the issues you've mentioned.

Previous Topic | Next Topic