CAN Bus Data Decoder
Decode a signal from raw CAN bus data bytes using a start bit and signal length. Extract the selected CAN field and view its binary, hexadecimal and unsigned decimal value.
What Is a CAN Bus Data Decoder?
A CAN bus data decoder helps interpret the data bytes carried inside a Controller Area Network frame. A CAN message may contain several different signals packed into individual bytes or groups of bits.
Instead of treating the complete payload as one number, a decoder can extract only the bit range assigned to a particular signal.
This calculator accepts raw hexadecimal CAN payload bytes and extracts one unsigned signal using its start-bit position and bit length.
How This CAN Data Decoder Works
Enter the hexadecimal bytes from the CAN data field, specify where the desired signal begins, and provide the number of bits assigned to that signal.
The calculator identifies those bits and converts the extracted field into binary, hexadecimal and unsigned decimal form.
Start bit: 8
Length: 8 bits
Selected byte: 34
Decimal: 52
CAN Payload Byte Example
Consider the following four-byte payload:
Byte 1 = 34
Byte 2 = 56
Byte 3 = 78
Each hexadecimal byte contains eight binary bits.
34 = 00110100
56 = 01010110
78 = 01111000
With this calculator’s numbering convention, bits 0 through 7 belong to Byte 0, bits 8 through 15 belong to Byte 1, and so on.
CAN Start Bit
The start bit identifies the first bit of the signal inside the payload. In this calculator, bit numbering begins with the least-significant bit of Byte 0.
| Payload Byte | Bit Positions |
|---|---|
| Byte 0 | 0–7 |
| Byte 1 | 8–15 |
| Byte 2 | 16–23 |
| Byte 3 | 24–31 |
| Byte 4 | 32–39 |
| Byte 5 | 40–47 |
| Byte 6 | 48–55 |
| Byte 7 | 56–63 |
CAN Signal Length
The signal length specifies how many consecutive bits belong to the field being decoded. A signal does not have to occupy an entire byte.
For example, a four-bit field can represent a mode, state, counter or small numerical value while leaving the remaining bits available for other signals.
Length: 4
Only bits 0, 1, 2 and 3 are extracted.
Extracting a Multi-Byte CAN Signal
Signals can also span more than one payload byte. For example, a 16-bit field beginning at bit 8 uses the second and third bytes of the payload under the numbering convention used by this calculator.
Start: 8
Length: 16
Selected bytes: 34 56
Because this page uses little-endian signal extraction, the lower-addressed byte contributes the least-significant portion of the extracted integer.
CAN Data Bytes and Binary Representation
Hexadecimal is commonly used to display CAN payloads because one hexadecimal byte maps directly to eight binary bits.
Binary: 10100101
Decimal: 165
Viewing the payload in binary makes it easier to understand signal boundaries, flags and packed bit fields.
Where CAN Data Decoding Is Used
CAN data decoding is useful in automotive diagnostics, embedded systems, industrial automation, robotics, vehicle testing, telemetry, CAN logging and electronic control unit development.
Raw CAN traffic often appears as hexadecimal bytes. Signal definitions specify how particular values are packed inside those bytes.
CAN Data Decoder vs CAN ID Calculator
The CAN identifier and CAN data field perform different jobs.
| Field | Purpose |
|---|---|
| CAN ID | Identifies and prioritizes the CAN message |
| CAN Data | Carries the actual payload bytes and encoded signals |
This calculator focuses on the payload. CAN identifier calculations belong to the separate CAN ID Calculator.
CAN Decoder vs DBC Decoder
A DBC file contains signal definitions such as start bit, length, byte order, scale, offset and signal names. This calculator does not read or interpret DBC files.
Instead, it is designed for cases where you already know the bit location and length of the signal and want to inspect the raw binary value manually.
Important CAN Data Decoding Notes
It accepts between one and eight classic CAN payload bytes.
Bit 0 is defined as the least-significant bit of Byte 0.
The extraction method on this page uses little-endian bit significance.
Real CAN databases may define signals using Intel or Motorola byte ordering and DBC-specific start-bit conventions.
The calculator does not automatically apply engineering scale or offset.
It does not determine what a signal represents without the vehicle, ECU or equipment signal documentation.
For production CAN analysis, always follow the exact signal definition supplied by the manufacturer or DBC database.