惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

V
Visual Studio Blog
I
InfoQ
H
Help Net Security
GbyAI
GbyAI
博客园 - 叶小钗
Recent Announcements
Recent Announcements
Engineering at Meta
Engineering at Meta
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
爱范儿
爱范儿
Y
Y Combinator Blog
L
LangChain Blog
腾讯CDC
酷 壳 – CoolShell
酷 壳 – CoolShell
WordPress大学
WordPress大学
Stack Overflow Blog
Stack Overflow Blog
F
Fortinet All Blogs
G
Google Developers Blog
Apple Machine Learning Research
Apple Machine Learning Research
The GitHub Blog
The GitHub Blog
T
The Blog of Author Tim Ferriss
博客园 - Franky
D
Docker
Jina AI
Jina AI
罗磊的独立博客

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Why your lithium forklift's fuel gauge lies in the middle...
997 997 · 2026-06-19 · via DEV Community

997 997

The habit every lead-acid driver picks up, glance at the resting voltage to judge how full the pack is, quietly stops working on lithium iron phosphate. It stops working across the broad middle of the range, right where a straight answer would help.
An iron phosphate cell holds its voltage almost level for a long stretch of its discharge. From the high end down to nearly empty, the terminal voltage barely drifts, tracing a plateau rather than a slope. The energy is leaving the pack steadily, but the one number a simple gauge reads is sitting nearly still.
A few hundredths of a volt can cover a wide band of remaining charge.
Lead-acid behaves the opposite way, which is exactly why the voltage trick grew up around it in the first place. Its voltage falls in a fairly steady slope as it empties, so reading the terminal gives a rough but usable sense of fuel left.
On lithium the same gauge tells a comforting lie, reading near full through the bulk of the shift and then dropping through the floor in the last stretch with little warning.
Counting electrons instead of reading volts
The honest way to track an iron phosphate pack is to count what goes in and what comes out, current multiplied by time, added up. Coulomb counting, in the jargon.
The idea is clean and the practice drifts. A current sensor carries a small offset, charging never returns every last electron it took, and tiny errors each cycle accumulate into a gauge that slowly wanders away from the truth. Count long enough without a reference and your careful tally is off by more than the plateau ever hid.
So counting alone is not enough. The tally needs something solid to check itself against, now and then, to stay honest.
The fix in one breath
Count the current, and recalibrate at the ends where voltage moves.
Where the curve cooperates
The plateau is flat in the middle but not at the edges. Near full and near empty the voltage finally bends sharply, and those bends are where the pack will tell you a real number.
This is the quiet cleverness inside a good lithium management system, and it is why two packs with identical cells can give wildly different gauges. The controller counts coulombs through the flat middle, trusting the running tally because voltage there is useless, and then waits for the pack to reach one of the steep ends of the curve to reset that tally against a voltage it can read. Top the pack right off and the voltage climbs hard near the ceiling, giving a clean fix on full. Run it down toward empty and the voltage drops away just as hard, giving a fix on the bottom. Between those calibration points the system is dead-reckoning, like a ship tracking its position by speed and heading until it can sight a landmark. The better controllers go further, folding the current count and the voltage reading into a running estimate that also accounts for how the pack's apparent capacity shifts with temperature and age, often with a filter that weighs each clue by how trustworthy it is at that moment. A pack that never gets topped fully, that lives its life in the plateau on opportunity charges, gives the system fewer landmarks to sight, which is one reason a periodic full charge is good hygiene even when the duty cycle never seems to need it. The number on the display is not a measurement. It is an estimate the controller defends with arithmetic and the occasional glimpse of solid ground.
Topping fully now and then is not about capacity. It hands the gauge a landmark to fix itself against.
Two packs built on the same cells can read wildly differently because the cells were never the hard part of the job. The estimation is, and a sloppy estimator riding on excellent cells still hands a driver a gauge they quietly learn to stop trusting by mid-afternoon.
Why this is a buying question
A fleet runs on whether drivers believe the gauge. If the number sags to half and the truck keeps working fine, or reads comfortable and dies at the dock, people stop planning around it and start guessing, which wastes the run time the battery was supposed to give back.
The cells are a commodity. The estimation logic that turns a flat curve into a number you can schedule a shift by is the engineering that separates packs, and it is where a serious builder like Shinko Power earns the difference.