Welcome to pyA2L’s documentation

pyA2L is a Python toolkit for working with ASAM MCD-2 MC (ASAP2) A2L files. The library parses A2L into a SQLite-backed model, provides inspection and validation utilities, and enables automation around ECU measurement and calibration metadata.

For background on the ASAP2 standard, see: https://www.asam.net/standards/detail/mcd-2-mc/wiki/

Contents:

• Readme
  • Contents
  • About ASAM MCD-2 MC (ASAP2)
  • What pyA2L offers
  • Why pyA2L?
  • Design highlights
  • Installation
  • Getting Started (Quickstart)
  • Tips
  • Examples
  • Create API and coverage parity
  • Command-line usage
  • Compatibility
  • Project links
  • Contributing
  • Code of Conduct
  • Changelog / Release notes
• Getting Started with pyA2L
  • Import an .a2l file to database
  • Re-importing an existing file
  • Open an existing .a2ldb database
  • Running a first database query
  • Using the Inspect API
  • Working with IF_DATA
  • Validate and export
  • Next steps
  • Migrating from pya2l.DB
• Installation
  • Prerequisites
  • Install from PyPI
  • Install from source (editable)
• Building pyA2L (from source)
  • Prerequisites
  • One‑liner build and install (recommended)
  • Development install
  • Building distribution artifacts
  • Building the documentation
• Configuration
  • Import options
  • Export options
  • Environment variables
  • CLI options (a2ldb-imex)
  • Database pragmas
  • Logging
• Tutorial
  • Basic Usage
  • Working with Modules
  • Advanced Features
  • Working with Variant Coding
  • Common Use Cases
  • Best Practices
  • Conclusion
• Working with IF_DATA
  • The IfData class
  • Quick start
  • Parsed data vs. raw data
  • Using the flatmap
  • Accessing IF_DATA across all entity types
  • Practical examples
  • Manual parsing with IfDataParser
  • Empty IF_DATA and edge cases
  • Best practices
• API Reference
  • Session Management
  • Inspect API
  • Create API
  • Validate API
  • Low-Level ORM Access
• HOW‑TOs
  • Import once, reuse the database
  • Export back to A2L or JSON
  • CLI import/export (a2ldb-imex)
  • Concurrent access and export safety
  • Dump measurements to Excel
  • Handle encodings and quiet mode
  • Creating A2L content programmatically
  • Performance & Best Practices
• Frequently Asked Questions
  • Where to start?
  • While importing my A2L file I’m getting strange Unicode decode errors, what can I do?
  • My A2L file includes tons of files… Do I have to copy all of them to my current working directory?
  • How do I work with IF_DATA sections in A2L files?
  • How do I create new A2L elements programmatically?
  • How do I filter query results when working with A2L elements?
  • Can SYMBOL_LINK have a missing offset?
  • What performance can I expect for large A2L files?
  • Does the exporter preserve all A2L attributes during roundtrip?
  • Any missing questions and answers?
• pya2l
  • pya2l package

Indices and tables

• Index

• Module Index

• Search Page