Dervo Global logoDervoGlobalAll articlesContact
Insights › Automotive
Automotive

Reviewing ARXML and DBC changes between releases: a practical checklist

Dervo Automotive team · 30 October 2026 · 2 min read

Communication matrices change with every release. A checklist for catching the changes that break ECUs, restbus models and tests before they reach the bench.

Every vehicle program delivers new versions of its communication matrix: DBC files for CAN networks and ARXML files for AUTOSAR systems. A single changed factor, start bit or interface can break an ECU, a restbus simulation or a whole test suite. A short review at every delivery saves days of debugging.

1. Compare before you integrate

Never drop a new file straight into the build. Compare it with the previous release and list every change: added and removed messages, signals, ports and interfaces, and every changed value. Then check each change has a matching change request.

2. Changes that break things quietly

3. Checks on every file

4. Update everything downstream

A matrix change rarely stops at the ECU. Check restbus and simulation models, HIL test configurations, test cases and expected values, diagnostic descriptions, and any documentation sent to suppliers.

5. Keep a record

Save the change list with the release. When a test fails three weeks later, it is the fastest way to find out what changed.

Try it

Our free DBC compare and checker and ARXML viewer, compare and checker do steps 1 to 3 in your browser and export the result to Excel. Your files are never uploaded.

Managing a communication matrix across releases or suppliers? Talk to a Dervo Automotive engineer.
ShareLinkedInWhatsApp

Need help with this?

Dervo Global supports automotive programs with testing and engineering, and growing businesses with simple CRM and HR & Payroll tools.

More articles