← Back to topic list

Range 420 but the display shows 380 when fully charged

Working_Presence8606 | 2026-01-31 07:54 | 28 views

I have a byd atto 3, driving from 3 months couple of questions Is it safe to fully charge twice or thrice in a week, an over night charging Also the charging when fully shows around 380 which is 40km down the original Is this normal? How does this work?

Comments (15)
LuxePassenger 2026-01-31 08:05

U can Switch the display of Ur Range between ur calculated Range based of ur drving and just the charge in the settings I think.

deed02392 2026-01-31 08:06

Safe yes. Range is based on all factors such as external temperature, AC and your driving style.

PitchPleasant338 2026-01-31 08:50

It's winter.  Read your manual.

Ruber-Chicken 2026-01-31 09:06

Coughs in Australian....

DarkAngel5666 2026-01-31 09:10

You have two range modes in the settings app. One that just does a calculation based on your charge level vs the advertised range, and the second, a tiny bit more useful (because it is still very optimistic) that does the same but factors in your real consumption.

net_fish 2026-01-31 10:42

Given it's winter in the EU you're probably getting wacked a bunch of range thanks to the cold weather. As for charging, it's an LFP battery, go for it. I've been charging my Atto 3 to 100% every 24 hours for the past couple of months in order to try and fix a voltage delta. It's improved from around 400mV to 200mV so yay! Normally I'd do a charge to full 2-3 times a week purely because of the km's that I do. But yeah, in comparison to NMC packs an LFP pack is a lot more tolerant to 100% charges and infact needs them at least weekly to ensure accuracy in the SoC readout.

PitchPleasant338 2026-01-31 12:00

Exactly, it's so cold that even you're sick and coughing!

santz007 2026-01-31 14:26

All LFP batteries should always be charged to 100%. The tricky part is to keep it as little amount of time as possible at 100%, but yes definitely charge to 100% every time without worrying

CptnSpandex 2026-02-01 01:15

I love my atto3 but they range guess-o-metre is dog shit. Best advice is to put a small piece of masking tape over that part of the display and just write “lies” on the tape. I use the battery % and trip computer.

alkonz 2026-02-01 02:13

Could you elaborate more on fixing voltage deltas. Thanks.

net_fish 2026-02-01 02:31

I managed to do something stupid, I think mainly too much time between charges to 100% and not enough 10-100 calibration charges given my km's/yr which managed to push the delta between highest and lowest cell voltage to around 400mV. that managed to knock 2% off the packs state of health. I've got it back to a shade under 200mV which has recovered almost all of that 2%. I do something like 35-40k km a year and id suggest that the manual is written with the average 10-15k km/yr driver in mind. as such I probably need to be doing calibration charges quarterly not 6 monthly :) I only even noticed it because Im a data nerd and was poking around with CarScanner Pro and an OBD reader

Maximum-Canary1598 2026-02-01 09:51

This is not true. I can recommend the following video: https://youtu.be/w1zKfIQUQ-s?si=eBsv7KOmnaf7Veup

alkonz 2026-02-01 16:49

Thanks for the info. I should take a look at the voltages with my own odb scanner. Did you wait some time before taking the reading?

Working_Presence8606 2026-02-01 20:38

Still need the estimate how far can it go but yeah let’s see how it goes in summer

net_fish 2026-02-01 23:59

The delta has to be read just as charging completes. If you're using CarScanner Pro then you leave it running with one of the dashboards open that shows the delta and then once completed open up the data log and read the peak value from the graph for the HV pack delta. The most accurate way is to use ThinkDiag Mini + the DollarFix app on an Android device to read the "top differential pressure" out of the BASU (BMS). this is the figure that the car itself records thus the most accurate. you can get the ThinkDiag off Ali Express and it comes with the software

Add comment

Login is required to comment.

Login with Google