WaveBPS
All DocsProductsLearning CenterSupport
  • Introducing WaveBPS: Portable Low level analog serial data analysis
  • Getting Data into WaveBPS
    • WaveBPS Import Data Video
  • Live Capture with WaveBPS
  • Navigation
  • Advanced Analysis
  • Automated Test with WaveBPS
  • WaveBPS Basic Databases
  • Cursor Measurements
  • Event List Columns
  • Setting up Serial Decoding in WaveBPS
  • Loading custom data into WaveBPS
  • Exporting Waveforms from WaveBPS
  • Scalar Measurement List
  • Licensing WaveBPS
  • WBPS Binary File Format
    • Double Precision Format
    • Unsigned short Format
  • CAN / CAN FD Bus
    • CAN / CAN FD Bus Bit Stuffing
    • CAN / CAN FD Bus Data Frame
    • CAN / CAN FD Bus Errors
    • Extended Data Frames
    • CAN / CAN FD Bus Physical Layers
    • CAN / CAN FD Bus Remote Data Frame
    • Single Wire CAN / CAN FD
  • FlexRay
    • FlexRay Dynamic Frame
    • FlexRay Static Frame
    • FlexRay Startup
    • FlexRay Wakeup Symbol
    • FlexRay Physical Layer
  • Example Waveforms
    • FlexRay versus CAN / CAN FD BUS
    • CAN / CAN FD bus at 70 % utilization 120 megasamples
    • CAN / CAN FD Bus Waveform Decoding
    • FlexRay Frame Decode
    • FlexRay Dynamic Frame
    • LIN Bus Decode
    • Low Speed Fault Tolerant CAN / CAN FD Waveform
  • LIN Bus
    • LIN Errors
    • LIN Frame
    • LIN Header
    • LIN Slave Section
  • Other Buses
    • UART: K-Line, J1708, ISO9141, GM CGI, RS232
    • SPI bus
    • I2C or SMBus
    • J1850
  • Compare FlexRay, CAN / CAN FD bus and LIN Bus
  • WaveBPS Video Links
  • Specifications
Powered by GitBook
LogoLogo

Applications

  • Cybersecurity
  • Data Logging
  • Simulate ECU Functions
  • Diagnostics, Testing and Validation

Products

  • Vehicle Network Adapters
  • Data Loggers
  • Software
  • Automotive Ethernet Tools

Support

  • Support Resources
  • Contact Support
  • Class Schedule & Registration
  • Training Video Library

Company

  • About
  • News
  • Events
  • Contact Us

Copyright © 2025 | All Rights Reserved

On this page
  1. CAN / CAN FD Bus

CAN / CAN FD Bus Data Frame

PreviousCAN / CAN FD Bus Bit StuffingNextCAN / CAN FD Bus Errors

Last updated 11 months ago

The CAN / CAN FD bus data frame does the work on CAN / CAN FD. The whole point of CAN / CAN FD is to send data between networked controllers - and that is the job of the data frame.

The data frame begins with a single SOF (start of frame) bit and is followed by the CAN / CAN FD Identifier. The CAN / CAN FD Identifier is used to identify the message and the node the message is coming from. The identifier can be either 11 bits long or 29 bits long depending on the state of some reserved bits.

After the CAN / CAN FD Identifier, there is a data section that first begins with a data length. The CAN / CAN FD data frame can have 0 to 8 bytes so it uses 4 bits to encode length. The data bytes directly follow the data length.

Following the CRC is the Ack field. This field will be set by all other nodes on the network who properly received the frame.

After the Ack bit there will be a quiet time called end of frame space followed by a minimum inter-frame space.

Following the data is the . The CRC is a calculation that is made on the first part of the CAN / CAN FD frame by both the receiver and transmitter. If they match the receiver assumes that it received the data correctly.

CRC
Picture of a CAN / CAN FD data frame
The CAN / CAN FD Data Frame Starts with a SOF bit and then ID bits.
The data bytes follow the data length (DLC) in the CAN / CAN FD Frame.
The CAN / CAN FD CRC checks data integrity while the ack indicates reception by another node.