Message Format
Scheduling
Message Types
Data Assurance
Miscellaneous
Message Header
a The Token is referred to as the Message Header
a The Message Header is sent by the Master Task
a The Message Header Is used for synchronization
a The Message Header includes the identifier
Message Header —
Message Response
a The Message Response Is sent by a Slave Task
a The Message Response Is comprised of the data and checksum
a Classic checksum over data field (LIN 1.x)
a Enhance ksum over data field and ID field (LIN 2.
Message Response
| Data Byte 1 —] + Data Byte n
State Flow Charts
LIN Message (Nominal)
LIN Message
= (W. +N
10+ (Noss + 1) + &
Transmission of a LIN Message
à A time reserve of up to 40% Is given for transmission of a LIN
Header
EN su,
À pe A
Scheduling
Message Types
Principle of Scheduling
2 The LIN Master controls communication in the LIN network; il
does this by placing Message Headers with the specified
Identifiers on the LIN bus at the specified send times
2 Send times and identifiers are defined by the LIN Schedule; the
send times must be selected so that the transmission of the LIN
messages is guaranteed
St
Frome Me) nom > teen
Organization of the LIN Schedule
2 The LIN Schedule Is organized in Mint
Slots (t, t,
LIN Schedule (tn aa)
a An adequate number of Mini Slots E
must be provided to guarant TES
transmission of a LIN me Sie DES
Communication Principle
Message Format
Scheduling
Message Types
nconditional Frames (ID 0-59)
a One Message Respo je Header
à Message Header is always
3 Diagnostic Frames (ID 60-61)
2 Master Request Frame (ID=60, ID=0x3C)
a Slave Ri Frame (ID=61, ID=0x3D)
2 Other Frames (ID 62-63)
a User-defined (1D=62, ID=0x3E)
3 Future extensions (ID=63, ID=0x
Unconditional Frames
Schedule LIN Slave LIM Master Ll
Communication cycle
Diagnostic Frames
à Slave Response Frame (II
ge Header is sent by the LIN Master
ge Response is sent by the relevant LIN Slav.
jonse and Configuration S
a Mes:
à Mess
à Used for: Diagnos
LIN Slave 1 LIN Master LIN Slave 2
Diagnostic Schedule
Frame + Header ID =0%
SRE tesina
Communication Principle
Message Format
Scheduling
Message Types
Data Assurance
Miscellaneous
Data Assurance
Each LIN Slave monitors its operating state and creates a status
report
The status report Is sent periodically to the LIN Master (LIN 2.0)
Monitoring by error detection mechanisms
a Parity
a Checksum
LIN messages detected as corrupt are rejected
Error handling is not part of the LIN specification
Error handling must be defined separately
Communication Principle
Message Format
Scheduling
Message Types
Data Assurance