本文へ移動
cccskills
無料GitHub で公開

simulink-customize-a2l

Customize A2L (ASAP2) files generated from Simulink models using coder.asap2 and coder.mapping APIs. Use this skill when adding COMPU_METHODs, creating GROUPs, converting STD_AXIS to COM_AXIS, adding BIT_OPERATIONs, creating VARIANT_CODING, excluding measurements or struct elements, removing DEFAULT_EVENT_LIST, or any A2L customization for calibration tool compatibility (INCA, CANape). Also use when the user mentions ASAP2, ECU calibration data, A2L export.

インストール方法を見る

含まれるファイル(7)

  • SKILL.md10.2 KB
  • manifest.yaml495 B
  • references/compu-method-guidance.md3.6 KB
  • references/construction-time-properties.md4.6 KB
  • references/customization-patterns.md3.0 KB
  • references/object-properties.md18.1 KB
  • references/variant-coding-guidance.md5.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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);

% 2. Customize elements
add(descObj, newElement);
set(descObj, 'ElementType', 'Name', Prop=value);
info = get(descObj, 'ElementType', 'Name');
names = find(descObj, 'ElementType');
delete(descObj, 'ElementType', 'Name');

% 3. Export — MUST pass descObj back or all customizations are silently lost
coder.asap2.export(modelName, CustomEcuDescriptions=descObj);

Critical: When using Path B, omitting CustomEcuDescriptions=descObj in the export call silently discards all customizations with no error.

Critical: When using Path B, construction-time options (SupportStructureElements, etc.) CANNOT be passed to export alongside CustomEcuDescriptions — they must be passed to getEcuDescriptions.

Key Functions

FunctionPurpose
coder.asap2.getEcuDescriptionsCreate ECU description object (construction-time config)
coder.asap2.exportExport A2L file with customizations
coder.asap2.CompuMethodCreate computation method
coder.asap2.CharacteristicCreate characteristic (parameter)
coder.asap2.MeasurementCreate measurement (signal)
coder.asap2.GroupCreate A2L group
coder.asap2.RecordLayoutCreate record layout
coder.asap2.AxisInfoCreate axis points or axis descriptor
coder.asap2.VarCriterionCreate variant criterion
coder.asap2.VarCharacteristicCreate variant characteristic
coder.asap2.FunctionCreate FUNCTION object for grouping measurements/characteristics
coder.mapping.api.getGet code mapping object (persistent settings)
setInport / setOutportControl inport/outport A2L export (persistent)

See references/object-properties.md for mandatory fields, valid types, and creation order for each coder.asap2.* class.

Pattern Routing

Match the user's task to the correct reference for detailed guidance:

TaskKey RuleReference
Add COMPU_METHOD (RAT_FUNC, LINEAR, TAB_VERB)RAT_FUNC COEFFS direction is PHYS→INT — invert the desired formulareferences/compu-method-guidance.md
Convert STD_AXIS to COM_AXIS (shared breakpoints)Use ForceShared=true on the Characteristic — do NOT manually create AXIS_PTSreferences/customization-patterns.md
Add BIT_OPERATION to a measurementMust set BOTH BitMask AND MaskData — either alone produces no outputreferences/customization-patterns.md
Exclude inports/outports persistentlyUse coder.mapping.api + setInport/setOutport + slbuildreferences/customization-patterns.md
Create VARIANT_CODINGMust create supporting CHARACTERISTIC objects (selection + variant-dependent) with RecordLayouts and CompuMethods BEFORE VarCriterion/VarCharacteristic. All multi-value properties must be string arrays (not char/cell).references/variant-coding-guidance.md
Create Characteristic (CURVE, MAP, CUBOID)RecordLayout struct array must match axis count for STD_AXIS typesreferences/object-properties.md
Create MeasurementSet DataType='SWORD', EcuAddress='@ECU_Address@name@', CompuMethodName='NO_COMPU_METHOD' as defaultsreferences/object-properties.md
Create GroupSee mandatory fields and ROOT constraintreferences/object-properties.md
Create RecordLayoutStruct array required for multi-axis types (MAP, CUBOID); single struct for VALUE/VAL_BLKreferences/object-properties.md
Create AxisInfo / AXIS_PTSDual role: add(descObj, axisInfo) creates AXIS_PTS; characteristic.AxisInfo = [...] creates AXIS_DESCRreferences/object-properties.md
Control construction-time options (SupportStructureElements, IncludeDefaultEventList, etc.)Must pass at getEcuDescriptions() — cannot set after construction or pass to export with CustomEcuDescriptionsreferences/construction-time-properties.md

Release Requirements

FeatureMinimum Release
COMPU_METHOD, Measurement, Characteristic, BIT_OPERATIONR2022b
RecordLayout, AxisInfo (STD_AXIS, CUBOID)R2023a
Group (ROOT groups)R2023b
VarCriterion, VarCharacteristic (variant coding)R2025a

If the user's release is too old, inform them. Do not attempt workarounds — the APIs do not exist on older releases.

Common Mistakes

These cause silent failures or incorrect calibration data. Always check before generating code:

MistakeWhy It's WrongCorrect Approach
coder.asap2.export(modelName) without CustomEcuDescriptions=descObjSilently discards all customizations — no error, exports default A2LAlways pass descObj back when using the customization workflow
RAT_FUNC Coefficients = [0 0.5 -40 0 0 1] for "PHYS = 0.5×INT - 40"COEFFS is PHYS→INT, not INT→PHYS — produces the inverse conversionInvert: INT = 2×PHYS + 80 → [0 2 80 0 0 1]. See references/compu-method-guidance.md
set(descObj, ..., 'CompuMethodName', name) before adding the CompuMethodset() auto-creates a placeholder that blocks subsequent add()delete() the auto-created placeholder, then add() the user's version
MaskData.Shift without BitMaskBIT_OPERATION block is only emitted when both are setAlways set BitMask (e.g., '0xFF') alongside MaskData
MaskData.Shift = 3 expecting LEFT_SHIFTPositive = RIGHT_SHIFT; sign is counterintuitiveUse -3 for LEFT_SHIFT 3
Manually creating AXIS_PTS for STD→COM_AXISUnnecessary complexity; error-prone struct array handlingUse set(descObj, 'Characteristic', name, 'ForceShared', true)
descObj.SupportStructureElements = falseNot a settable property after constructionPass at creation: getEcuDescriptions(mdl, SupportStructureElements=false)
VarAddress = '0x5000' (char vector)Char vector silently produces empty output — no addresses, no criterion nameMust be string array: ["0x5000","0x5008"]
CompuVTabValues.Integers = [0,1,2]Property does not existUse CompuVTabValues.Values = [0, 1, 2]
CompuVTabValues.Literals = {'A','B'} (cell array)Accepted without error but exports 0 elementsMust be string array: ["A","B"]
Skipping slbuild after setInport/setOutportExport silently produces stale A2L with old settingsAlways slbuild after code mapping changes before export
Hardcoding EcuAddress = '0x0000'Calibration tools cannot resolve the address at import timeUse '@ECU_Address@<elementName>@' for linker resolution
Leaving mandatory fields unset on new objectsBlank fields produce invalid A2L — calibration tools reject the fileSee references/object-properties.md for required fields per class
Creating VarCriterion/VarCharacteristic without supporting CHARACTERISTICsVARIANT_CODING references characteristics that don't exist — calibration tool rejects the fileCreate selection CHARACTERISTIC (with TAB_VERB CompuMethod) and variant-dependent CHARACTERISTIC (with RecordLayout) BEFORE VarCriterion/VarCharacteristic. See references/variant-coding-guidance.md

Conventions

  • Verify A2L output with fileread after export — use contains for additions, ~contains for deletions/exclusions
  • Use string arrays (not char vectors or cell arrays) for all multi-value properties
  • Pass all configuration at getEcuDescriptions() construction time
  • Use ForceShared=true for STD→COM_AXIS (never build AXIS_PTS manually for this)
  • Use delete(descObj, 'ElementType', 'Name') to remove auto-created placeholders — this is the only recovery from the auto-creation trap caused by set() on a reference name before the referenced object exists
  • Prefer coder.mapping.api over coder.asap2 when settings should persist with the model

Copyright 2026 The MathWorks, Inc.


レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Author or upgrade Model Advisor checks for Simulink and System Composer models. Covers the full lifecycle: guideline authoring, check specification, Model Advisor check implementation, and qualification testing. Use when creating new checks (edit-time, standard batch, config-parameter, auto-fix), converting legacy StyleOne/StyleTwo/StyleThree checks to modern DetailStyle, creating a guideline for modeling, enforcing a modeling rule, or testing/qualifying a check. Triggers on any modeling constraint (e.g., "blocks shall...", "signals must match...", "parameters shall be set to...").

日本語の概要は準備中です。原文の説明を表示しています。

matlab/simulink-agentic-toolkit1,2152026年10月8日 更新

Synthesize new waveforms from scratch for Simulink inports using createInputDataset. Use ONLY when the user asks to generate, create, or synthesize signals (step, ramp, sine, chirp, pulse, noise) to populate a Dataset for External Inputs or Signal Editor. Covers timeseries and timetable formats with correct data type, interpolation, units, and dimensions. Also covers function-call and trigger inport timing setup. Do NOT use when the user wants to load, import, or read existing data from files (MAT, CSV, spreadsheet) — even if that data will be used as model input. Do NOT use for running simulations or plotting outputs.

日本語の概要は準備中です。原文の説明を表示しています。

matlab/simulink-agentic-toolkit1,2152026年10月8日 更新

Common steps for building multi-layer system architecture models using System Composer. Use when implementing architecture models or when interacting with interface dictionaries, allocation sets, stereotypes, and requirements for architecture components.

日本語の概要は準備中です。原文の説明を表示しています。

matlab/simulink-agentic-toolkit1,2152026年10月8日 更新

Builds and edits Simulink, System Composer, Stateflow, and Simscape models. Use when modifying model structure, parameters, ports, connections, or Stateflow chart internals.

日本語の概要は準備中です。原文の説明を表示しています。

matlab/simulink-agentic-toolkit1,2152026年10月8日 更新

Use this skill when the user asks to check Simulink model compliance against a standard (MISRA, MAB, JMAAB, ISO, DO, IEC, EN, CERT C/CWE, AUTOSAR, Simulink Code Inspector (SLCI)), wants to run Model Advisor checks, or needs a compliance report with fix suggestions. For JMAAB/MAB, supplement deterministic checks with agentic review of uncheckable guidelines.

日本語の概要は準備中です。原文の説明を表示しています。

matlab/simulink-agentic-toolkit1,2152026年10月8日 更新

Guide users through creating and managing .satk/block-policy.json for controlling which blocks the agent can use, which are excluded, and which block parameters the agent should not modify. Use when setting up block usage policy for a project.

日本語の概要は準備中です。原文の説明を表示しています。

matlab/simulink-agentic-toolkit1,2152026年10月8日 更新

matlab のスキルをすべて見る

このスキルの問題を報告する