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. LIN Bus

LIN Header

PreviousLIN FrameNextLIN Slave Section

Last updated 11 months ago

The LIN Header is the first part of the LIN Message. It begins with a sync break, followed by a sync waveform and then the LIN identifier. After this portion of the message, the ID indicates which node should respond with the .

The Sync break is a break that is low for 13 or more bits. All LIN devices see this symbol as the start of a message as it is a special symbol that forces a UART frame error.

After the Sync break is the sync waveform. The sync waveform is always the UART byte 0x55. This byte, as you can see from the the picture below, is an alternating sequence of 1's and 0's. This waveform allows the slave devices to calibrate their UART clock to that of the master. This allows cost savings in slave devices using a time and temperature dependant, but cheap .

After the Sync byte is the LIN ID. The LIN ID consists of 6 ID bits and 2 . The parity bits are calculated according to the LIN Specification. Normally, parity bits are pre-calculated for receivers and transmitters. When an ID is referenced including the parity bits it is called the "protected ID" - the normal LIN ID is without the parity bits. For example, the LIN ID shown below is the LIN ID 0x01 with a protected ID of 0xC1.

parity bits
slave part of the message
UART
R-C Oscillator
Sent by the master node, the LIN Break indicates the start of a LIN Frame
The sync byte is always hex 0x55 and can be used by slave devices to calibrate their clocks
The ID indicates what data needs to sent in the data section and includes parity bits.