Case study

AUTOSAR - Compliant Software Development For Battery Management System

Design and Development of Embedded Software Solutions based on AUTOSAR Architecture
Client: BMS Supplier Industry: Automotive Location: Korea

AUTOSAR (Automotive Open System Architecture) is a standardized open software architecture for the automotive industry that aims to simplify the development, integration, and maintenance of software components in modern vehicles. AUTOSAR supports the development of complex software systems by providing a standardized framework for software components, communication protocols, and interfaces. This case study will explore the use of AUTOSAR-compliant ECU ssoftware components in electric vehicle charging systems..

The development of BMS software requires a high level of expertise in battery chemistry, electronics, and software engineering. BMS software must be able to perform complex calculations, communicate with other vehicle systems, and ensure the safe operation of the battery. Additionally, BMS software must comply with safety standards and regulations to ensure the safety of users and the vehicle

01

Customer background

Our client is a leading Korean Tier 1 supplier of electronic charging solutions for automotive companies.

02

Challenges

The complexity of BMS software presents several challenges , the software must be able to monitor the state of the battery in real-time, calculate the battery's state of charge and state of health, and control the charging and discharging process. Additionally, the software must communicate with other vehicle systems, such as the powertrain and the charging system, to ensure the safe operation of the vehicle.

The customer looked for a standalone team of technical experts who could take full responsibility for a part of software development and integration of AUTOSAR-compliant solution.

03

Product and Solution

To enable seamless communication between software components and systems, We proposed AUTOSAR-compliant standardized communication protocol which reduced the time and effort required to develop, integrate, and maintain software systems for BMS.

04

Tools & Technologies

05

Delivered Services

We are involved in design and development of software components, including battery monitoring, control, and management. The battery monitoring component includes cell voltage monitoring, temperature monitoring, and current monitoring. The battery control component includes state estimation, state prediction, and charge control.

1. Battery Monitoring Component: The battery monitoring component is responsible for monitoring the state of the battery, like cell voltage, current, and temperature. This component ensures that the battery is operating within safe limits and provides data to other components for state estimation and prediction.

2. State Estimation Component: The state estimation component is responsible for estimating the state of charge (SoC), state of health (SoH), and state of function (SoF) of the battery. This component uses data from the battery monitoring component to calculate the battery's SoC, SoH, and SoF, which are used by other components to control the charging and discharging process.

3. Charging Control Component: The charging control component is responsible for controlling the charging process of the battery. This component uses data from the state estimation component to determine the optimal charging strategy for the battery, such as the charging current and voltage. Our architecture enables to communicate with the charging system to ensure the safe and efficient charging of the battery.

4. Discharging Control Component: The discharging control component is responsible for controlling the discharging process of the battery. This component uses data from the state estimation component to determine the optimal discharging strategy for the battery, such as the discharging current and voltage.

5. Communication Component: The communication component is responsible for communicating with other vehicle systems, such as the powertrain and the charging system. The CAN communication is used for communication between the battery monitoring component, state estimation component, charging control component, and other BMS software components. The battery monitoring component reads the voltage, current, and temperature data from the battery and sends it to the state estimation component over CAN. The state estimation component then estimates the battery's state of charge (SoC), state of health (SoH), and state of function (SoF) and sends it to the charging control component over CAN. The charging control component then determines the optimal charging strategy based on the battery's state and sends the charging command to the charging system over CAN.

05

Business Value

1. We reduced the time and effort required to develop, integrate, and maintain software systems for BMS.
2. We enabled faster time-to-market, reduced costs, and improved interoperability between different BMS software components and systems.
3. We build modular and flexible software systems that can adapt to different battery chemistries and capacities.

Whether you are a OEM or Tier'1 supplier, we are committed to helping you achieve your goals and bring innovative products to market. Contact us today to learn more about how we can help your business succeed.