Customize A2L Files

Customize A2L (ASAP2) files generated from Simulink models using the coder.asap2 and coder.mapping APIs, avoiding silent errors and undocumented pitfalls.

When to Use

• Adding or modifying COMPU_METHODs (LINEAR, RAT_FUNC, TAB_VERB, IDENTICAL)
• Creating or modifying GROUPs in the A2L file
• Converting STD_AXIS to COM_AXIS for lookup tables
• Adding BIT_OPERATION (LEFT_SHIFT, RIGHT_SHIFT, SIGN_EXTEND) to measurements
• Creating VARIANT_CODING (VarCriterion, VarCharacteristic)
• Excluding inports, outports, or struct elements from the A2L
• Removing DEFAULT_EVENT_LIST or other IF_DATA blocks
• Any customization passed via CustomEcuDescriptions to coder.asap2.export

When NOT to Use

• Reading or parsing existing A2L files (use Vehicle Network Toolbox a2lfile)
• Configuring XCP/CAN transport layers
• Setting up Simulink model code generation (storage classes, data dictionaries)
• General Embedded Coder build workflows without A2L customization

Core Workflow

Decision: Direct export vs. customization workflow

• No element customization needed (only configuration like excluding struct elements or DEFAULT_EVENT_LIST): call coder.asap2.export directly with name-value options. No getEcuDescriptions needed.
• Element customization needed (adding/modifying/deleting measurements, characteristics, groups, etc.): use the full getEcuDescriptions → customize → export workflow.

% === Path A: Config-only (no element changes) ===
load_system(modelName);
slbuild(modelName);
coder.asap2.export(modelName, SupportStructureElements=false, IncludeDefaultEventList=false);

% === Path B: Element customization ===
load_system(modelName);
slbuild(modelName);

% 1. Create ECU descriptions, pass ALL configuration options here
descObj = coder.asap2.getEcuDescriptions(modelName, ...
    SupportStructureElements=false, ...
    IncludeDefaultEventList=false);