SLAAEF5 March   2024 MSPM0G1505 , MSPM0G1505 , MSPM0G1506 , MSPM0G1506 , MSPM0G1507 , MSPM0G1507 , MSPM0L1303 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306 , MSPM0L1306-Q1 , 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 Equations
      1. 2.2.1 NomAbsSoc Calculation
        1. 2.2.1.1 Coulometer With OCV Calibration
        2. 2.2.1.2 Battery Model Filter
      2. 2.2.2 CusRltSoc Calculation
      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 Step1: Hardware Preparation
    2. 4.2 Step2: Get Battery Model
      1. 4.2.1 Battery Test Pattern
      2. 4.2.2 Battery Model Generation
    3. 4.3 Step3: Input Customized Configuration
    4. 4.4 Step4: Evaluation
      1. 4.4.1 Detection Data Input Mode
      2. 4.4.2 Communication Data Input Mode
  8. 5MSPM0 Gauge Solutions
    1. 5.1 MSPM0L1306 + 1 LiCO2 Battery
      1. 5.1.1 Hardware Setup Introduction
      2. 5.1.2 Software and Evaluation Introduction
      3. 5.1.3 Battery Testcases
        1. 5.1.3.1 Performance Test
        2. 5.1.3.2 Current Consumption Test
    2. 5.2 MSPM0G3507 + BQ76952 + 4 LiFePO4 Batteries
      1. 5.2.1 Hardware Setup Introduction
      2. 5.2.2 Software and Evaluation Introduction
      3. 5.2.3 Battery Testcases
        1. 5.2.3.1 Performance Test1 (Pulse Discharge)
        2. 5.2.3.2 Performance Test2 (Load Change)
  9. 6References

4.4.2 Communication Data Input Mode

For this mode, the battery running data is input from the GUI. It enables you 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.

GUID-31E4766D-DC75-4061-8C82-1FD7A0389ACF-low.png Figure 4-12 Communication Data Input Mode Structure
  1. First, to realize this method, you 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, you 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. You need to input the Cell num at column B. And then input every battery's Vcell(mV), Icell(mA) and Tcell(­°C) into the same column like the same McuData file. For this, you can generate a McuData file first and refer to that one to do the transmit ion. At last, name the file with "-McuData.xlsx".
    GUID-1BE14725-1CA1-4B08-8FD6-8BB44D314A0E-low.png Figure 4-13 McuData Type
  4. Forth, 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, you need to wait until the port status changes to “Start transmit ion!”. The data load time and excel save time will be long if the file is very large. It would be 5~10 minutes.
    GUID-2FBB035F-895F-44D3-A287-50D643FAE4E8-low.png Figure 4-14 Communication Data Input Steps

You will receive the battery running data from MCU shown in MCU Test Data block. After it finishes transmission, the GUI automatically saves the received data under the GUI address.