Skip to content
BUSMUST
中文Support

BMCLI database

Persistent lifecycle for typed engineering database resources. database owns registration, validation, discovery, and removal; protocol-specific operations remain under dbc, ldf, and future database categories. Resources are stored in the per-user BMCLI state directory and remain available to later processes.

database load

Section titled “database load”

Validate and register a DBC, LDF, A2L, or mapping file. The type is inferred from the extension unless --type is supplied. The default resource name is the filename stem. Loading the same canonical path again is idempotent.

Terminal window
bmcli database load --file=network.dbc --name=vehicle
bmcli database load --file=body.ldf --name=body-lin

database unload

Section titled “database unload”
Terminal window
bmcli database unload vehicle
bmcli database unload --all

database list / info / validate

Section titled “database list / info / validate”
Terminal window
bmcli database list --format=json
bmcli database list --type=dbc --format=json
bmcli database info vehicle --format=json
bmcli database validate --file=network.dbc --format=json
bmcli database validate vehicle --format=json

validate --file does not change registry state. info and validation of a registered resource re-open the source file, so stale or damaged paths fail instead of returning cached parser metadata.

Source of truth: bmcli_reference.md in the BMCLI repository. Run bmcli help <category> <action> --format=json for the exact contract of the installed version.