this post was submitted on 13 Oct 2023
82 points (96.6% liked)
Asklemmy
44152 readers
995 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Title says plugged in and body says plugged in at 100%; these can be separate concepts if one has fine control over the charging voltage.
Plenty of academic research out there showing that pegging Li to 100% SoC reduces cycle counts to EOL (by electrolyte degradation and other processes), especially at higher voltages/temps. You didn't mention capacity reduction associated with charging at freezing temps so I assume that is a non-issue in your use case.
It seems to me that if leaving it plugged in is an option you have shore/mains/grid power. So I'd
Am I missing something here?
offgrid with LiFePO4
I live offgrid with Li on a very limited budget, so performance and maximal cycle life is a practical matter for me. Based on my own reading and experimentation I charge my 4S LiFePO4 to 13.8v (3.45Vpc) until Absorption falls to 0.10C then quasi-float at 13.31v (3.3275Vpc). I warm them to 50F and charge at โค0.4C.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn't work well for people on different instances. Try fixing it like this: [email protected]