From raw bytes to physical values
A DBC defines messages and signals: identifier, length, sender, start bit, bit length, byte order, signedness, factor, offset, range, unit, receivers, and optional value tables. A decoder applies those rules to turn payload bits into values such as rpm, degrees Celsius, or state labels.
For a linear signal, the usual relationship is physical value equals raw value multiplied by factor plus offset. Incorrect factor or offset may produce believable but wrong measurements, which is why database review needs test vectors.
Byte order and bit numbering
Intel and Motorola signals differ in how multi-bit values traverse bytes. Tools may display Motorola start bits using different visual conventions, so copying a start bit between tools without confirming their numbering model is risky.
Use a known payload and expected physical value to validate the definition. For critical signals, test minimum, nominal, maximum, negative values when signed, and boundary cases that cross byte positions.
Multiplexing and database quality
Multiplexed messages reuse payload positions for different signal groups selected by a multiplexer value. A decoder must first resolve that selector, then decode only the active group.
Good database maintenance includes unique message ownership, consistent naming, correct cycle times, meaningful units, documented ranges, and change control. An encode-decode round trip with representative values helps catch overlapping signals and impossible definitions early.