DaVinci Configurator
AutoC reads and writes ECUC configuration through Vector DaVinci Configurator. Configurator 5 only. You need the Configurator install directory and a project path that contains *.dpa.
Open the project and set paths
- Open a project — pick the folder that contains
*.dpa. - Open Settings → Install paths and set the Configurator install root (it contains
Core/DVCfgCmd.exe). - Open Settings → DaVinci, confirm the project path, and set SIP or include / exclude modules if needed.
- Click Save, then Reload.

Success: a DaVinci card under Project → Project info.
Use Save and Verify on a module in Project info. Before verify, AutoC copies .dpa to *.autoc.dpa; scripts live in .autoc/davinci-scripts/ in the project.
Advanced
Module filters — Include modules / Exclude modules on Settings → DaVinci (case-sensitive).
ASW — foreign-reference enums; DaVinci also loads from .dpa ECUEX paths. See ASW.
Configuration sync
In mixed projects, EB configures MCAL and DaVinci configures the Vector stack. Save on an EB module in Project info also writes the matching MCAL ARXML in the DaVinci project — no EB export + DaVinci import.
- Set both paths as above and in EB tresos, then save and reload
- Edit EB modules in chat (e.g.
Mcu,Can_43_FLEXCAN) - Open Project → Project info and click Save on that EB module — updates EB XDM and DaVinci
Config/ECUCARXML
EB-only setup (no DaVinci) still saves XDM only.
| What you change | In Project info |
|---|---|
MCAL (Mcu, Port, Can_43_FLEXCAN …) | EB module Save (auto-syncs DaVinci) |
Vector stack (EcuC, PduR, Com …) | DaVinci module Save |
Use EB module names in AutoC; DaVinci may show different labels (e.g. Can) — no manual mapping needed.
Open Configurator after save. If the window was already open, refresh or reopen the project.

The open folder must have both EB .project and DaVinci .dpa, and both paths must point at the same vehicle project.
