Skip to content

Databases and DBC

bigt92 edited this page Oct 28, 2026 · 2 revisions

English · Italiano

Databases and DBC

BUSMASTER works with its own database format, .dbf. Most CAN networks are described with DBC files (Vector CANdb++). BUSMASTER-NG can load a DBC directly: it converts it to a .dbf for you.

Load a DBC

CAN → Database → Load DBC (or Ctrl+Shift+M), then choose one or more .dbc files.

For each DBC, BUSMASTER-NG:

  1. converts it to a BUSMASTER database with the same name next to the DBC (Motor.dbc → Motor.dbf). If that folder is read-only, the database goes to %LOCALAPPDATA%\BUSMASTER-NG\DBC;
  2. associates the database, so message names and signals appear in the message window, signal watch, transmit window, ...;
  3. writes in the Trace Window (View → Trace Window) the result, any warnings and the path of the database.

If a .dbf with the same name already exists, BUSMASTER-NG asks before replacing it, and tells you whether that file was created from this DBC and whether the DBC changed since then:

  • Yes converts the DBC again and replaces the file;
  • No associates the existing file as it is (useful if you changed it in the database editor);
  • Cancel skips this DBC.

The configuration remembers the .dbf. When the DBC changes, load it again.

Conversion warnings

They are shown in the Trace Window and saved in <name>.log next to the database.

Warning Meaning
Min or max value outside the range of the signal – Limited to the range of the signal The range written in the DBC does not fit in the signal's bits; the database uses the largest possible range. Usually harmless
IEEE float/double signal – Kept, but BUSMASTER shows its raw value The signal is a floating point number: BUSMASTER shows it as an integer (see Limits)
More than 8 data bytes (CAN FD) – Message skipped BUSMASTER databases cannot hold CAN FD messages (see Limits)
... Match not Found in Param List An attribute of the DBC refers to an unknown definition; only that attribute is lost

If the conversion fails, a message box says why; the most common reason is a DBC without any CAN message of up to 8 bytes.

Associate and dissociate BUSMASTER databases

  • CAN → Database → Database → Associate (Ctrl+M): use an existing .dbf.
  • CAN → Database → Database → Dissociate (Ctrl+T): remove databases from the configuration (the files stay).

More than one database can be associated at the same time.

Edit a database

Tools → Editors → CAN DBF Editor: create, open and change .dbf files (messages, signals, value descriptions).

  • Factor and offset are kept with all their digits (also factors such as 0.0000001).
  • Signal Details shows the physical range (raw value × factor + offset) next to the raw minimum and maximum; you can type it with decimals and the raw values follow, rounded to the step of the factor.
  • The line below the fields shows where the signal lies in the message: LSB, MSB and the start bit it has in a DBC file. For Motorola signals Byte Index and Start Bit are the position of the least significant bit, and the signal continues towards byte 0: a 16-bit signal in bytes 0 and 1 has Byte Index 1, Start Bit 0.

Convert files

Tools → Format Converter converts between formats, among them DBC → DBF, DBF → DBC (to go back to CANdb++ or other tools) and J1939 DBC → DBF. The converters were fixed in BUSMASTER-NG: decimal numbers no longer depend on the language of Windows, large offsets and very small factors are kept exactly, Motorola and 64-bit signals convert correctly in both directions.

Databases converted with BUSMASTER 3.2.2 on an Italian or German Windows can contain wrong factors and offsets (for example 0.5 written as 0). If you still have the DBC, load it again with Load DBC.

Limits

These come from the database engine of the original BUSMASTER (DBManager.dll), which is closed source and cannot be changed:

  • factor and offset are used with about 7 significant digits (the .dbf keeps all digits);
  • IEEE float / double signals are shown as raw integers;
  • CAN FD: frames up to 64 bytes are sent and received with interfaces that support them, but shown as raw bytes; a database with a message longer than 8 bytes is refused;
  • multiplexed signals are all shown, whatever the value of the multiplexer.

Technical details and the status of the related issues of the original project: docs/dbc-support.md.

Clone this wiki locally