Distributed Battery Management System Daisy Chain Architecture

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing distributed battery management systems require separate slave controllers for each battery module and a block controller for data communication, leading to increased manufacturing costs and vulnerability to noise interference, particularly in hybrid and electric vehicles.

Innovation Solution

Implementing a daisy chain structure for slave controller connections, where only the top-level slave controller includes a microcontroller and sensing ICs, reducing hardware components and using asynchronous differential signaling for robust communication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a separate slave controller with microcontroller and memory functions is used for each battery module, then monitoring capability is improved, but manufacturing cost increases

Engineering Contradiction:

Improvemonitoring capabilityVSAvoidmanufacturing cost

Core Design Contradiction:

ReliabilityVSEase of manufacture

Solution Approach 1:

Multiple slave controllers are merged into a single controller unit that can monitor multiple battery modules. The slave controller is configured to receive control information and sense information from multiple battery modules, eliminating the need for separate microcontrollers and memory units in each module while maintaining comprehensive monitoring capability.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The slave controller is designed with multi-functional capability to handle control information and sensing data from multiple battery modules simultaneously. A single slave controller can interface with multiple battery modules through a unified communication interface, making the system more cost-effective while preserving monitoring reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Ease of operation

If wire harnesses are used to connect slave controllers, then communication is established, but noise vulnerability increases

Engineering Contradiction:

Improvecommunication capabilityVSAvoidnoise vulnerability

Core Design Contradiction:

Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The mechanical wire harness connection system is replaced with an inductive communication system. The master controller and slave controller communicate through magnetic coupling between coils, eliminating physical wire connections that are susceptible to noise. This allows control information and sensing data to be transmitted wirelessly between controllers, significantly reducing noise vulnerability while maintaining communication capability.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Ease of operation

If block controller is added for data communication between slave controllers, then communication function is improved, but device complexity increases

Engineering Contradiction:

Improvecommunication functionVSAvoiddevice complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The block controller component is extracted and eliminated from the system. Instead of adding an intermediate communication controller, the slave controller is directly configured to communicate with the master controller through inductive coupling. This removes the unnecessary communication layer, reducing device complexity while maintaining effective data communication between controllers.

Inventive Principle:

Principle #2Taking out (Extraction)

4Reliability

If multiple slave controllers with full microcontroller functionality are deployed, then monitoring coverage is improved, but hardware resource consumption increases

Engineering Contradiction:

Improvemonitoring coverageVSAvoidhardware resource consumption

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

Multiple slave controller functions are combined into a single slave controller unit. The consolidated slave controller can interface with multiple battery modules through a unified architecture, reducing the total number of microcontrollers, memory units, and other hardware resources while maintaining comprehensive monitoring coverage across all battery modules.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The slave controller is designed with universal multi-functional capabilities to handle monitoring tasks for multiple battery modules. A single slave controller can process control information and sensing data from various battery modules, eliminating the need for dedicated hardware resources in each module while preserving complete monitoring coverage.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9236735B2Distributed battery management system and method for distributed battery management

Publication Date: 2016.01.12 HYUNDAI MOBIS CO LTD

AI summary

Disclosed is a distributed battery management system of managing a plurality of battery modules, including: slave controllers have a daisy chain structure in which the slave controllers are connected from a bottom-level slave controller up to a top-level slave controller in series, sequentially transfer control information received from the outside from the top-level slave controller up to the bottom-level slave controller, sense information on the battery modules in response to the transferred control information, sequentially transfer the sensed sensing information from the bottom-level slave controller up to the top-level slave controller, and transmit the sensing information transferred to the top-level slave controller to the outside; and a master controller which transmits the control information to the top-level slave controller among the slave controllers and manages the battery modules by using the sensing information received from the top-level slave controller.