SLAAEF5B March   2024  – June 2025 MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G3506 , MSPM0G3507 , MSPM0H3216 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1Introduction
  5. 2Algorithm Introduction
    1. 2.1 Battery Basic Knowledge Introduction
    2. 2.2 Different SOCs and Used Technologies
      1. 2.2.1 NomAbsSoc Calculation
        1. 2.2.1.1 Coulometer With OCV Calibration
        2. 2.2.1.2 Data Fusion
        3. 2.2.1.3 Battery Model Filter
      2. 2.2.2 CusRltSoc Calculation
        1. 2.2.2.1 EmptySoc and FullSoc
        2. 2.2.2.2 Core Temperature Evaluation
      3. 2.2.3 SmoothRltSoc Calculation
    3. 2.3 Algorithm Overview
      1. 2.3.1 Voltage Gauge Introduction
      2. 2.3.2 Current Gauge Introduction
      3. 2.3.3 Capacity Learn Introduction
      4. 2.3.4 Mixing Introduction
  6. 3Gauge GUI Introduction
    1. 3.1 MCU COM Tool
    2. 3.2 SM COM Tool
    3. 3.3 Data Analysis Tool
  7. 4MSPM0 Gauge Evaluation Steps
    1. 4.1 Step 1: Hardware Preparation
    2. 4.2 Step 2: Get a Battery Model
      1. 4.2.1 Battery Test Pattern
      2. 4.2.2 Battery Model Generation
    3. 4.3 Step 3: Input Customized Configuration
    4. 4.4 Step 4: Evaluation
      1. 4.4.1 Detection Data Input Mode
      2. 4.4.2 Communication Data Input Mode
    5. 4.5 Step 5: Gauge Performance Check
      1. 4.5.1 Learning Cycles
      2. 4.5.2 SOC and SOH Accuracy Evaluation
  8. 5MSPM0 Gauge Solutions
    1. 5.1 MSPM0L1306 and 1 LiCO2 Battery
      1. 5.1.1 Hardware Setup Introduction
      2. 5.1.2 Software and Evaluation Introduction
      3. 5.1.3 Battery Test Cases
        1. 5.1.3.1 Performance Test
        2. 5.1.3.2 Current Consumption Test
    2. 5.2 MSPM0G3507, BQ76952 and 4 LiFePO4 Batteries
      1. 5.2.1 Hardware Setup Introduction
      2. 5.2.2 Software and Evaluation Introduction
      3. 5.2.3 Battery Test Cases
        1. 5.2.3.1 Performance Test 1 (Pulse Discharge)
        2. 5.2.3.2 Performance Test 2 (Load Change)
    3. 5.3 MSPM0L1306 and BQ76905
  9. 6Summary
  10. 7References
  11. 8Revision History

4.4.2 Communication Data Input Mode

For this mode, the battery running data is input from the GUI. This enables users to run the real test case or evaluate the MSPM0 Gauge with only a LaunchPad. This method can remove the need of hardware, increase algorithm running frequency and have no limit to the length of battery running data.

Communication Data Input Mode StructureFigure 4-12 Communication Data Input Mode Structure
  1. First, to realize this method, users only need a LaunchPad and do the right hardware setting.
  2. Second, download the gauge code to the LaunchPad after changing the detection mode to COMMUNICATION_DATA_INPUT in Gauge_UserConfig.h.
  3. Third, users need to have a MCUData file. An introduction is provided on how to transmit a test data into a recognized file by the GUI, especially for those who do not generate the test file from GUI. Users need to input the Cell num at column B. Then, input each Vcell(mV), Icell(mA) and Tcell(­°C) of the battery into the same column as the same in McuData file. For this, users can generate a McuData file first and refer to that one to do the transmit on. Finally, name the file with -McuData.csv.
    McuData Type Figure 4-13 McuData Type
  4. Fourth, connect the UART COM port following Figure 4-14 and load the MCUData runfile in MCU COM Tool by clicking the File Open button. After clicking the Data transmit button, wait until the port status changes to Start transmit!.
    Communication Data Input Steps Figure 4-14 Communication Data Input Steps

Users receive the battery running data from MCU shown in MCU Test Data block. After this finishes transmitting, the GUI automatically saves the received data under the GUI address.