can_message dict | trace_summary string | signal_mappings list | source_artifact dict | processing_functions list |
|---|---|---|---|---|
{
"message_name": "BMS_STATUS_ID",
"can_id": 419385573,
"frame_type": "Extended frame",
"dlc": 8,
"cycle_time_ms": 100
} | BmsStatus_OnCanRx accepts the extended BMS status frame with identifier 0x18FF50E5 and an 8-byte payload. It decodes bytes 0–1 as an unsigned little-endian pack-voltage value and bytes 2–3 as a signed little-endian pack-current value, applies a factor of 0.1 to each, and stores the results in the corresponding g_bms_st... | [
{
"signal_name": "PackVoltage",
"start_bit": 0,
"bit_length": 16,
"byte_order": "Little-endian (least-significant byte first)",
"is_signed": false,
"factor": 0.1,
"offset": 0,
"unit": "V",
"internal_variable": "g_bms_status.pack_voltage_v",
"decode_expression": "(float)voltag... | {
"source_text": "#define BMS_STATUS_ID 0x18FF50E5UL\n#define BMS_STATUS_DLC 8U\n#define BMS_STATUS_CYCLE_MS 100U\n#define BMS_STATUS_EXTENDED_FRAME 1U\n\ntypedef struct {\n float pack_voltage_v;\n float pack_current_a;\n} BmsStatus;\n\nstatic BmsStatus g_bms_status;\n\nvoid BmsStatus_OnCanRx(const CanFrame *fr... | [
"BmsStatus_OnCanRx"
] |
{
"message_name": "THERMAL_STATUS_ID",
"can_id": 419390113,
"frame_type": "Extended frame",
"dlc": 8,
"cycle_time_ms": 250
} | ThermalStatus_OnCanRx filters for the extended thermal-status frame with identifier 0x18FF62A1 and an 8-byte payload. It reads bytes 0–1 as a signed little-endian temperature value, scales it by 0.01, and stores it in g_thermal.max_cell_temp_c. Byte 2 is read as an unsigned pump-duty value, scaled by 0.5, and stored in... | [
{
"signal_name": "MaxCellTemperature",
"start_bit": 0,
"bit_length": 16,
"byte_order": "Little-endian (least-significant byte first)",
"is_signed": true,
"factor": 0.01,
"offset": 0,
"unit": "degC",
"internal_variable": "g_thermal.max_cell_temp_c",
"decode_expression": "(floa... | {
"source_text": "#define THERMAL_STATUS_ID 0x18FF62A1UL\n#define THERMAL_STATUS_DLC 8U\n#define THERMAL_STATUS_CYCLE_MS 250U\n#define THERMAL_STATUS_EXTENDED_FRAME 1U\n\ntypedef struct {\n float max_cell_temp_c;\n float pump_duty_pct;\n} ThermalStatus;\n\nstatic ThermalStatus g_thermal;\n\nvoid ThermalStatus_O... | [
"ThermalStatus_OnCanRx"
] |
{
"message_name": "CHARGE_LIMITS_ID",
"can_id": 1313,
"frame_type": "Standard data frame",
"dlc": 8,
"cycle_time_ms": 20
} | ChargeLimits_Transmit constructs the standard 8-byte frame with identifier 0x521. It converts the charge and discharge current limits to unsigned raw values by dividing by 0.1, then writes them in little-endian order to bytes 0–1 and 2–3, respectively. Bytes 4–7 are set to zero before Can_Send transmits the frame. | [
{
"signal_name": "ChargeCurrentLimit",
"start_bit": 0,
"bit_length": 16,
"byte_order": "Little-endian (least-significant byte first)",
"is_signed": false,
"factor": 0.1,
"offset": 0,
"unit": "A",
"internal_variable": "g_limits.charge_current_limit_a",
"decode_expression": "No... | {
"source_text": "#define CHARGE_LIMITS_ID 0x521U\n#define CHARGE_LIMITS_DLC 8U\n#define CHARGE_LIMITS_CYCLE_MS 20U\n#define CHARGE_LIMITS_EXTENDED_FRAME 0U\n\ntypedef struct {\n float charge_current_limit_a;\n float discharge_current_limit_a;\n} ChargeLimits;\n\nstatic ChargeLimits g_limits;\n\nvoid ChargeLimi... | [
"ChargeLimits_Transmit",
"Can_Send"
] |
Battery Management CAN Signal and Source Code Traceability Dataset
This dataset contains supervised examples tracing CAN signal definitions, encoding and decoding logic, internal variables, and related processing functions in battery management firmware source code. It connects message definitions to implementation details and code locations, providing examples of how signals are handled across firmware. The data supports code fine-tuning, repository understanding, and analysis of CAN signal implementations in battery management control units.
Technical Specifications
| Field | Type | Description |
|---|---|---|
| can_message | object | CAN message definition details identified in or associated with the source code. |
| trace_summary | string | A concise Chinese-language summary of the relationships between message definitions, signal fields, internal variables, and processing functions in the source code. |
| signal_mappings | array | Mappings between CAN signal definitions and firmware variables, encoding or decoding logic, and relevant code locations. |
| source_artifact | object | Firmware source code snippets used for trace analysis, together with their source information. |
| processing_functions | array | A list of firmware function names related to CAN message or signal processing. |
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
- 21