VCOS Studio

Beta

Beta feature. Report issues via Bug report.

AutoC reads and writes ECUC configuration through VCOS Studio. On Settings → Install paths, select the Studio .venv created by init_env. The project directory contains *.vcosproject.

The .venv should sit beside the Studio install (for example D:\code\haloos\vcos\.venv). It must be Python 3.8.x. AutoC does not create that environment.

Open the project and set paths

1. Open a project — pick the folder that contains *.vcosproject.
2. Settings → Install paths: set .venv.
3. Settings → VCOS Studio: confirm the project path. For mixed projects, set External modules — Configuration sync.
4. Click Save, then Reload.

Success: a VCOS Studio card under Project → Project info. Use Save, Verify, and Generate on a module. For mixed projects, Save MCAL on the EB card.

Advanced

Module filters — Include modules / Exclude modules on Settings → VCOS Studio (case-sensitive).

ASW — foreign-reference enums; always scans the open project. See ASW.

Configuration sync

In mixed projects, EB configures MCAL and VCOS configures the rest of the BSW. Unlike DaVinci, you must declare External modules on the VCOS side so Save on an EB module in Project info can sync MCAL into VCOS ECUC ARXML.

1. Set paths as above and in EB tresos, then save and reload
2. Open Settings → VCOS Studio → External modules and enter VCOS-side config names (e.g. Can, Mcu — not the EB name Can_43_FLEXCAN)
3. Edit EB MCAL, then Save that EB module in Project → Project info

What you change	In Project info
EB MCAL listed under External modules	EB module Save (syncs VCOS ECUC ARXML)
VCOS-owned stack modules	VCOS module Save, Verify, or Generate

Module config names may differ (EB Can_43_FLEXCAN ↔ VCOS Can), but container SHORT-NAMEs should match — sync writes by container path.

	Notes
Use	VCOS ECUC config names (Can, Mcu)
Not	EB plugin names (e.g. Can_43_FLEXCAN)
vs Exclude modules	External modules = not loaded by VCOS, but ARXML mirror target for EB save