CAN FD and DBC Workflow
For CAN FD projects, use DBC as the primary database format in BUSMASTER. DBC files can describe frames longer than 8 bytes and are the recommended path for CAN FD transmit-window editing, signal interpretation, signal watch, graphing, logging analysis, and replay analysis.
Why DBC Is Recommended
Section titled “Why DBC Is Recommended”CAN FD extends the payload length up to 64 bytes and can use FD and BRS frame attributes. The legacy DBF workflow was designed around classic CAN and does not provide a complete open path for CAN FD frame attributes. For this reason, BUSMUST recommends DBC for all CAN FD databases.### Using a DBC File
- Open or associate the DBC database from the database menu.
- Confirm that the CAN FD messages and signal definitions are visible in BUSMASTER.
- Use the transmit window to add database messages, edit physical or raw signal values, and send the frames.
- Use Message Window interpretation, Signal Watch, and Signal Graph to check received signal values.### DBF Limitation
DBF remains available for legacy classic-CAN projects, but it should not be used as the main database format for CAN FD. If a project requires CAN FD payload length, FD frame type, or BRS behavior, convert or maintain the database as DBC.### Compatibility Notes
DBC files from different tools may contain syntax variations. If a DBC fails to load or signals are interpreted incorrectly, try saving the file again from a DBC editor and remove nonessential messages until the incompatible section is found. Share the problematic DBC with BUSMUST support when compatibility analysis is required.
Authoritative source: BUSMASTER DITA help source CANFD_DBC_Workflow.dita, compiled into BUSMASTER.CHM with the application.