{
  "node": {
    "id": "term:a2l",
    "type": "Term",
    "label": "A2L file",
    "properties": {
      "id": "a2l",
      "name": "A2L file",
      "abbr": ".a2l",
      "aka": [
        "ASAM MCD-2 MC"
      ],
      "section": "topic-data",
      "definition": "The ASAM description of a controller’s internal measurement and calibration variables — names, memory addresses, data types and conversions — that tools need to read or tune them over XCP. It is generated with each firmware build and must match it exactly.",
      "related": [
        "xcp",
        "hex-file",
        "mdf4",
        "firmware"
      ],
      "url": "https://lemonergy.com/learn/glossary/a2l/",
      "mentions": []
    }
  },
  "edges": [
    {
      "id": "edge:4191",
      "source": "term:a2l",
      "target": "topic:topic-data",
      "type": "belongsTo",
      "properties": {
        "sourceFile": "terms.json"
      }
    },
    {
      "id": "edge:4192",
      "source": "term:a2l",
      "target": "term:xcp",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4193",
      "source": "term:a2l",
      "target": "term:hex-file",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4194",
      "source": "term:a2l",
      "target": "term:mdf4",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4195",
      "source": "term:a2l",
      "target": "term:firmware",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    }
  ],
  "neighbors": [
    {
      "id": "topic:topic-data",
      "type": "Topic",
      "label": "Data, communication and electronics",
      "properties": {
        "id": "topic-data",
        "name": "Data, communication and electronics",
        "lede": "The control units, chips, protocols and file formats through which a battery is measured, controlled and logged.",
        "context": "Separate quantities from encoding and transport.",
        "example": "2500 in a log might mean 25.00 °C, 2.5 V or raw counts. Units and scale must accompany the value.",
        "lesson_url": "https://lemonergy.com/learn/fundamentals/battery-basics/",
        "lesson_label": "Open battery basics"
      }
    },
    {
      "id": "term:xcp",
      "type": "Term",
      "label": "XCP",
      "properties": {
        "id": "xcp",
        "name": "XCP",
        "aka": [
          "Universal Measurement and Calibration Protocol",
          "CCP"
        ],
        "section": "topic-data",
        "definition": "The ASAM protocol for reading internal variables of a running controller and changing its calibration parameters, over CAN, Ethernet or other buses; CCP is its CAN-only predecessor. Engineers use it to watch BMS state estimators in real time and tune thresholds.",
        "related": [
          "a2l",
          "mdf4",
          "can-bus",
          "ecu"
        ],
        "url": "https://lemonergy.com/learn/glossary/xcp/",
        "mentions": [
          "bms"
        ]
      }
    },
    {
      "id": "term:hex-file",
      "type": "Term",
      "label": "HEX and S-record files",
      "properties": {
        "id": "hex-file",
        "name": "HEX and S-record files",
        "abbr": ".hex, .s19",
        "aka": [
          "Intel HEX",
          "Motorola S-record",
          "SREC"
        ],
        "section": "topic-data",
        "definition": "Text formats that carry a firmware or calibration image with its memory addresses and checksums, used to flash controllers: Intel HEX and Motorola S-record (.s19, .srec, .mot). Their content must match the A2L that describes it.",
        "related": [
          "flashing",
          "firmware",
          "a2l"
        ],
        "url": "https://lemonergy.com/learn/glossary/hex-file/",
        "mentions": []
      }
    },
    {
      "id": "term:mdf4",
      "type": "Term",
      "label": "MDF4",
      "properties": {
        "id": "mdf4",
        "name": "MDF4",
        "abbr": ".mf4",
        "aka": [
          "ASAM MDF",
          "Measurement Data Format",
          "MDF"
        ],
        "section": "topic-data",
        "definition": "The ASAM standard binary format for measurement data, version 4 with the .mf4 extension: it stores decoded signals and raw bus frames side by side with their units, conversions and timestamps, compressed and indexed so large logs open quickly. It is the common exchange format for vehicle and battery test data.",
        "related": [
          "blf",
          "dbc",
          "a2l",
          "xcp",
          "data-logger",
          "hdf5"
        ],
        "url": "https://lemonergy.com/learn/glossary/mdf4/",
        "mentions": []
      }
    },
    {
      "id": "term:firmware",
      "type": "Term",
      "label": "Firmware",
      "properties": {
        "id": "firmware",
        "name": "Firmware",
        "aka": [
          "embedded software",
          "BMS software"
        ],
        "section": "topic-data",
        "definition": "The software that runs on a BMS or charger controller. Its version decides how SOC, limits and faults behave, so it is tracked like a part number, updated by flashing over CAN or over the air, and recorded in the battery passport.",
        "related": [
          "mcu",
          "flashing",
          "bmu",
          "battery-passport",
          "functional-safety"
        ],
        "url": "https://lemonergy.com/learn/glossary/firmware/",
        "mentions": [
          "charger",
          "state-of-charge",
          "bms",
          "over-the-air-update"
        ]
      }
    }
  ]
}