{
  "node": {
    "id": "term:blf",
    "type": "Term",
    "label": "BLF file",
    "properties": {
      "id": "blf",
      "name": "BLF file",
      "abbr": ".blf",
      "aka": [
        "Binary Logging Format",
        "Vector BLF"
      ],
      "section": "topic-data",
      "definition": "Vector’s compressed binary format for bus logs: every CAN, CAN FD, LIN or Ethernet frame with its timestamp and channel. It is the usual format of field logs from vehicles and test benches, decoded with the matching DBC file.",
      "related": [
        "dbc",
        "asc-log",
        "mdf4",
        "data-logger",
        "can-bus"
      ],
      "url": "https://lemonergy.com/learn/glossary/blf/",
      "mentions": [
        "can-fd"
      ]
    }
  },
  "edges": [
    {
      "id": "edge:4204",
      "source": "term:blf",
      "target": "topic:topic-data",
      "type": "belongsTo",
      "properties": {
        "sourceFile": "terms.json"
      }
    },
    {
      "id": "edge:4205",
      "source": "term:blf",
      "target": "term:dbc",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4206",
      "source": "term:blf",
      "target": "term:asc-log",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4207",
      "source": "term:blf",
      "target": "term:mdf4",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4208",
      "source": "term:blf",
      "target": "term:data-logger",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:4209",
      "source": "term:blf",
      "target": "term:can-bus",
      "type": "relatedTo",
      "properties": {
        "sourceFile": "terms.json",
        "meaning": "Related context; not a causal claim"
      }
    },
    {
      "id": "edge:mentions/blf/can-fd",
      "source": "term:blf",
      "target": "term:can-fd",
      "type": "mentions",
      "properties": {
        "sourceFile": "terms.json",
        "method": "build_glossary.mention_index + mentions",
        "field": "definition",
        "meaning": "Text mention; 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:dbc",
      "type": "Term",
      "label": "DBC file",
      "properties": {
        "id": "dbc",
        "name": "DBC file",
        "abbr": ".dbc",
        "aka": [
          "CAN database"
        ],
        "section": "topic-data",
        "definition": "The de-facto text format, from Vector, that describes a CAN network: which messages exist, their identifiers and timing, and how each signal is packed, scaled and named. Without the BMS’s DBC a CAN log is just numbers.",
        "related": [
          "can-bus",
          "blf",
          "asc-log",
          "arxml",
          "j1939"
        ],
        "url": "https://lemonergy.com/learn/glossary/dbc/",
        "mentions": [
          "bms"
        ]
      }
    },
    {
      "id": "term:asc-log",
      "type": "Term",
      "label": "ASC file",
      "properties": {
        "id": "asc-log",
        "name": "ASC file",
        "abbr": ".asc",
        "aka": [
          "Vector ASCII log",
          "TRC",
          "PEAK trace"
        ],
        "section": "topic-data",
        "definition": "The plain-text form of a bus log, one frame per line with time, channel, identifier and data bytes. It is larger than BLF but readable in any editor; PEAK’s .trc files are a similar text trace from their interfaces.",
        "related": [
          "blf",
          "dbc",
          "can-bus"
        ],
        "url": "https://lemonergy.com/learn/glossary/asc-log/",
        "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:data-logger",
      "type": "Term",
      "label": "Data logger",
      "properties": {
        "id": "data-logger",
        "name": "Data logger",
        "aka": [
          "CAN logger",
          "telematics logger"
        ],
        "section": "topic-data",
        "definition": "A device on the vehicle or bench that records bus traffic and sensor data to BLF or MDF4 files, often with triggers and remote upload. For field failures it is the black box from which the sequence of events is rebuilt.",
        "related": [
          "blf",
          "mdf4",
          "fleet-telematics",
          "freeze-frame"
        ],
        "url": "https://lemonergy.com/learn/glossary/data-logger/",
        "mentions": []
      }
    },
    {
      "id": "term:can-bus",
      "type": "Term",
      "label": "CAN bus",
      "properties": {
        "id": "can-bus",
        "name": "CAN bus",
        "aka": [
          "Controller Area Network",
          "ISO 11898"
        ],
        "section": "topic-pack",
        "definition": "The serial network over which a BMS talks to the vehicle or inverter: a two-wire differential bus, defined in ISO 11898, carrying short prioritised messages at up to 1 Mbit/s, or faster with CAN FD. Every node hears every message, and a dominant bit wins arbitration without any collision.",
        "related": [
          "can-high-low",
          "can-fd",
          "termination-resistor",
          "bms",
          "lin-bus",
          "fms-interface"
        ],
        "url": "https://lemonergy.com/learn/glossary/can-bus/",
        "mentions": [
          "inverter"
        ]
      }
    },
    {
      "id": "term:can-fd",
      "type": "Term",
      "label": "CAN FD",
      "properties": {
        "id": "can-fd",
        "name": "CAN FD",
        "aka": [
          "CAN with flexible data rate"
        ],
        "section": "topic-pack",
        "definition": "An extension of classical CAN that switches to a higher bit rate, up to 5–8 Mbit/s, for the data part of each frame and allows 64 data bytes instead of 8. BMS data-logging and over-the-air updates are its usual battery uses.",
        "related": [
          "can-bus",
          "can-high-low",
          "bms"
        ],
        "url": "https://lemonergy.com/learn/glossary/can-fd/",
        "mentions": []
      }
    }
  ]
}