Readers

blf

Reads content from Vector BLF files containing CAN, CAN FD, FlexRay and Ethernet frames.

Properties

Name	Default Value	Type	Description
channel_definitions_file		string	This can be used to override the channel definitions within the metadata of the BLF file.
discard_incomplete_captures	true	bool	This will discard samples where we cannot map incomplete captures onto an ADTF data structure (CAN/CANFD/Flexray). If `false`, the length field values will be adjusted to cope with the smaller buffers within the samples.

Plugin Attributes

Attribute	Value
Plugin Name	blf_reader.adtffileplugin
License	ADTF Subscription
Support Mail	suppo.nosp@m.rt@d.nosp@m.igita.nosp@m.lwer.nosp@m.k.net
Homepage URL	https://adtf.dev/

Data Mapping

It supports the following bus logging types which will be mapped to the appropriate ADTF Device Toolbox SDK data structures and stream types:

CAN / CAN FD
FlexRay
Ethernet

Substreams

The reader provides a substream for each channel found within the file based on the stream type:

bus.CAN.CAN<channel_id>
bus.FR.FR<channel_id>
bus.ETH.ETH<channel_id>

Channel Handling

The reader requires either valid channel definitions within the meta data of the BLF file or an externel channels.xml file that you specify via the channel_definitions_file property (this can also be used to override invalid/incomplete meta data within the file).

Here is an example showcasing the format of the external file:

<?xml version="1.0" encoding="UTF-8"?>
<channels version="1">
  <channel number="1" type="CAN" network="CAN1" />
  <channel number="2" type="CAN" network="CAN2" />
  <channel number="1" type="FlexRay" network="FlexRay1">
  <channel number="2" type="FlexRay" network="FlexRay2">
  <channel number="1" type="Ethernet" network="Eth1">
  <channel number="2" type="Ethernet" network="Eth2">
</channels>

Note: <channel> may contain additional attributes/children (database definitions etc.), but these are not interpreted by the reader.