MF4 and MDF parsing
Read MF4/MDF measurements, inspect their signal content and metadata, and prepare the data for analysis or conversion.
Vehicle Data & Measurement
MF4 conversion for usable measurement workflows
Export selected MF4/MDF channels into agreed data formats with explicit handling of timestamps, units, and sampling rates. Receive a repeatable conversion workflow and checks that compare the exported values with the source measurement.
Discuss a MF4 ProjectProblems I can investigate
Find the behavior behind the symptom
- 01
Large measurement files
Measurement size or volume makes interactive inspection and processing impractical. A focused conversion or batch workflow can reduce repetitive manual handling.
- 02
Measurement format conversion needed
Export selected measurement channels to CSV or another agreed target. Bus-log exports require suitable raw bus records; decoded signal values alone do not establish the original frames.
- 03
Measurement event hard to locate
A relevant event is difficult to find within long or numerous recordings. Automated searches and focused signal views can narrow the investigation.
- 04
Unknown signal correlation
The signals associated with an observed vehicle behavior are not known. Measurement analysis can compare available signals and document evidence around possible correlations.
What I can help with
Focused engineering work in Vehicle Data & Measurement
Format conversion workflows
Define channel selection, time origin, units, and output columns before conversion. Preserve separate time bases or document an agreed resampling rule instead of silently aligning signals with different sampling rates.
Signal analysis and correlation
Search recordings, compare signal behavior, and investigate relationships around an observed event without assuming a root cause in advance.
CAN-aware measurement processing
Use DBC definitions to interpret CAN or CAN-FD measurement content when the required database is available.
Repeatable automation
Replace manual conversion and inspection steps with maintainable Python workflows, including batch processing and automated report generation.
What to send
Start with the evidence you already have
MF4/MDF measurement
An ASAM MDF measurement containing timestamped signals and metadata.
DBC
A CAN database defining messages and signals, when decoding or signal interpretation is required.
Problem description
Observed symptoms, context, reproduction steps, and expected behavior.
How the analysis works
From recorded data to engineering findings
- 01
Review the measurement task
Clarify the required output, relevant recordings, expected signal content, and the event or behavior to investigate.
- 02
Inspect available data
Parse the MF4/MDF measurement and review its signals and metadata alongside the supplied DBC and problem description.
- 03
Implement the conversion or analysis
Build the smallest practical workflow for conversion, event search, signal correlation, visualization, or batch processing.
- 04
Check the result against the task
Compare exported channel names, units, sample counts, timestamps, and selected values with the source. Record dropped metadata, invalid samples, and any resampling so the target workflow can interpret the output correctly.
What you receive
Deliverables matched to the investigation
Engineering analysis
A documented technical analysis with evidence and findings.
Python analysis script
A repeatable Python conversion script with the agreed channel mapping, target format, time-base handling, and source-to-output verification checks.
Measurement viewer
An application for navigating and plotting measurement signals.
Automated report
A repeatably generated report containing analysis or test results.
Technologies & formats
Automotive data and analysis environments
- MF4
MDF 4 Measurement
The fourth-generation ASAM MDF format for synchronized measurement data.
- MDF
Measurement Data Format
The ASAM family of binary measurement-data formats.
- MDA
ETAS MDA
A measurement-data analysis and visualization application.
- Python
Python
A general-purpose language widely used for automotive analysis, tooling, and automation.
- DBC
CAN Database
A text format describing CAN messages, signals, nodes, scaling, and metadata.
- python-can
python-can
A Python library providing a common API for CAN interfaces and messages.
- cantools
cantools
A Python package for parsing CAN databases and encoding or decoding messages.
- CSV
Comma-Separated Values
A tabular text format often used for exchanging decoded engineering data.
- REST API
REST API
An HTTP resource-oriented interface used for software and cloud integration.
- CAN
Controller Area Network
A priority-based broadcast bus used for in-vehicle control communication.
- CAN-FD
CAN Flexible Data-rate
An extension of CAN with larger payloads and a faster data phase.
FAQ
Practical questions before an investigation
- Can you work from an MF4 measurement without a DBC?
- Yes, the MF4/MDF measurement can still be parsed and reviewed. A DBC is needed when interpretation depends on CAN message and signal definitions.
- Is the work limited to one measurement file?
- No. The workflow can be scoped to individual recordings or repeated across numerous measurements through batch processing.
- Can the output support an existing analysis workflow?
- Yes. The target can be shaped around the required conversion, signal analysis, viewer, or automated report, based on the available measurement data and problem description.
- Will the analysis identify the root cause automatically?
- No outcome is assumed in advance. The work documents available evidence, signal relationships, and findings, while noting gaps in the supplied data.
Discuss the evidence
Discuss a MF4 Project
Share an MF4 measurement, the relevant DBC, and a short problem description to scope the conversion or analysis workflow.