Skip to main navigation Skip to search Skip to main content

H∞–Adaptive H∞ Algorithm-Based State of Charge Estimation Considering the Hysteresis Effect for Lithium Polymer Battery

  • Hailong Feng
  • , Zhifu Wang*
  • , Fujun Zhang
  • *Corresponding author for this work
  • Beijing Institute of Technology

Research output: Contribution to journalArticlepeer-review

Abstract

Accurate state of charge (SoC) estimation is crucial for the safe and reliable running of lithium-ion batteries in electrified transportation equipment. To enhance the estimation accuracy and robustness under different ambient temperatures, H∞ and the adaptive H∞ filterings were first combined to simultaneously forecast the parameters and SoC of the battery model considering the hysteresis effect in this paper. To drop the computational complexity to the most extent, the hysteresis unit was integrated into the first-order RC battery model and the aforementioned combined algorithm was developed under a dual-time frame. Then, the battery model with the hysteresis effect is evaluated against the model without that in terms of the estimation accuracy. Subsequently, the proposed algorithm is compared with the dual H∞ algorithm based on the employed battery model. The results demonstrate the excellent performance of the utilized battery model and the proposed algorithm in terms of both the estimation accuracy and the convergence speed.

Original languageEnglish
Article number717722
JournalFrontiers in Energy Research
Volume9
DOIs
Publication statusPublished - 20 Sept 2021

UN SDGs

This output contributes to the following UN Sustainable Development Goals (SDGs)

  1. SDG 7 - Affordable and Clean Energy
    SDG 7 Affordable and Clean Energy

Keywords

  • H∞ filter
  • adaptive H∞ filter
  • hysteresis
  • lithium-ion batteries
  • state of charge (SoC)

Fingerprint

Dive into the research topics of 'H∞–Adaptive H∞ Algorithm-Based State of Charge Estimation Considering the Hysteresis Effect for Lithium Polymer Battery'. Together they form a unique fingerprint.

Cite this