question stringclasses 3
values | demonstration_answer dict | firmware_source_code stringclasses 3
values |
|---|---|---|
How does this code confirm discharge overcurrent, and which flags or outputs change when the condition is confirmed? | {
"fault_type": "Discharge overcurrent",
"trigger_conditions": "pack_current_ma must be strictly greater than 18000 mA for four consecutive calls. Any reading at or below 18000 mA resets discharge_oc_samples to zero.",
"detection_path": "bms_fast_protection_task calls bms_check_discharge_overcurrent, which compar... | #include <stdbool.h>
#include <stdint.h>
#define DISCHARGE_OC_LIMIT_MA 18000
#define DISCHARGE_OC_CONFIRM_SAMPLES 4u
typedef struct {
int32_t pack_current_ma;
uint8_t discharge_oc_samples;
bool discharge_oc_fault;
bool discharge_fet_cmd;
bool fault_event_pending;
} Bms;
static void bms_check_disc... |
How is charge overtemperature detected, and how does the code handle the fault and its clear condition? | {
"fault_type": "Charge overtemperature",
"trigger_conditions": "The maximum of the four temp_c readings must be at least 55 °C for two consecutive checks. A maximum at or below 50 °C resets the counter and satisfies the clear condition. Between 50 °C and 55 °C, the counter is not reset by the shown logic.",
"det... | #include <stdbool.h>
#include <stdint.h>
#define TEMP_SENSOR_COUNT 4u
#define CHARGE_OT_TRIP_C 55
#define CHARGE_OT_CLEAR_C 50
#define CHARGE_OT_CONFIRM_SAMPLES 2u
typedef struct {
int16_t temp_c[TEMP_SENSOR_COUNT];
uint8_t charge_ot_samples;
bool charge_ot_fault;
bool other_charge_inhibit;
bool c... |
What cell-voltage condition confirms overvoltage, and what state changes does the code make when it is confirmed or cleared? | {
"fault_type": "Cell overvoltage",
"trigger_conditions": "The maximum of the 12 cell_mv readings must be at least 4200 mV for three consecutive checks. The counter is reset when the maximum is at most 4100 mV; readings between 4100 mV and 4200 mV do not reset it.",
"detection_path": "bms_10ms_task calls bms_chec... | #include <stdbool.h>
#include <stdint.h>
#define CELL_COUNT 12u
#define CELL_OV_TRIP_MV 4200u
#define CELL_OV_CLEAR_MV 4100u
#define CELL_OV_CONFIRM_SAMPLES 3u
typedef struct {
uint16_t cell_mv[CELL_COUNT];
uint8_t ov_samples;
bool cell_ov_fault;
bool charge_enable_request;
} Bms;
static void bms_che... |
Battery Management Fault Detection and Protection Logic Code Dataset
This dataset focuses on fault detection and protection logic in battery management control unit firmware. It provides source code snippets, code understanding questions, and structured example answers covering scenarios such as overvoltage, undervoltage, overcurrent, and temperature anomalies. The content explains fault conditions, detection paths, status or flag updates, protection responses, and their supporting code. It is suitable for code SFT, firmware repository understanding, and analysis of battery management protection logic.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| question | string | A question about the source code, such as how it detects or handles overvoltage, undervoltage, overcurrent, or temperature anomalies. |
| demonstration_answer | object | An answer based on the source code and question that explains fault conditions, detection steps, state changes, protection actions, and supporting code. |
| firmware_source_code | string | A battery management firmware code snippet for analysis, containing implementations of fault conditions, detection paths, status updates, or protection responses. |
Compliance Statement
| Authorization Type | CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |
Source & Contact
- Downloads last month
- 29