Professional Documents
Culture Documents
In-Vehicle Communication
M. Muthukumar
Introduction
1 2 4.5 10
incremental cost per node [$]
Local Interconnect Network
Physical layer
Frame Contents
Arbitration
Node Synchronization
Error Detection & Handling
Physical Layer
Bit Stuffing
Bit stuffing is used to guarantee enough
edges in the NRZ bit stream to maintain
synchronization.
After five identical and consecutive bit
levels have been transmitted, the
transmitter will automatically inject (stuff)
a bit of the opposite polarity into the bit
stream.
Receivers of the message will
automatically delete (de-stuff) such bits.
Error Detection
Message Level
Cyclic Redundancy Checks
Frame Checks
Acknowledgment Checks
Bit Level
Bit Monitoring
Bit Stuffing
If any node detects six consecutive bits
of the same level, a stuff error is flagged.
Message Level Error Detection
Frame Format
CRC delimiter
ACK delimiter
End of Frame Bit Field
Interframe Space (the 3 bit INTermission
field and a possible Bus Idle time).
Message Level Error Detection
Bit Monitoring
Each bit level (dominant or recessive) on
the bus is monitored by the transmitting
node.
Bit monitoring is not performed during
arbitration or on the ACK Slot.
Bit Level Error Detection
Bit Stuffing
The coding for bit stuffing requires that
five consecutive bits of the same level to
be followed by a complimentary bit level.
Six consecutive bits of the same level
cause a bit stuffing error
Error Flag
Communication can be ET or TT
Time slots are allocated
Reserved slot
Arbitration slot
Free slot
Requires global time synchronization
LIN Protocol
Master Task
Determines order and priority of messages.
Monitors Data and check byte and controls the error
handler.
Serves as a reference with its clock base (stable clock
necessary)
Receives Wake- Up Break from slave nodes
Slave Task
Is one of 2-16 members on the bus
Receives or transmits data when an appropriate ID is
sent by the master.
The node serving as a master can be slave.
Master
To accomplish this the master
sends Sync Break
sends Sync Byte
sends ID-Field
monitors Data Bytes and Check Byte, and
evaluates them on consistance
receives WakeUp Break from slave nodes when
the bus is inactive and they request some action.
serves as a reference with it’s clock base.
Slave
Synch Byte:
Specific Pattern for Determination of Time Base
(Determination of the time between two rising edges)
A Synch Byte precedes any Message Frame
ID-Field:
Message Identifier, Incorporates Information about the
sender, the receivers, the purpose, and the Data field
length.
Length 6 Bit.
4 classes of 1/2/4/8 Data Bytes. The length coding is in
the
2 LSB of the ID-Field. Each class has 16 Identifiers. A
total of 64 Message Identifiers are possible.
2 Parity Bits protect this highly sensitive ID-Field.
Flex Ray (Time Triggered Protocol)
It is deterministic and error tolerant high speed
bus.
Supports up to 64 nodes connected point to
point or over a classical bus structure.
Synchronous transmission for time critical data
and asynchronous for non-time critical data via
freely configurable, static & dynamic time
segments.
Automatic fault localization, bus guardian used
for deactivation of controller by error
messages.
Security requirements
Redundant communications
Avoid collision for bus access
Option for variable geometry redundancy
Operates by a ‘never give up’ strategy,
thus ensuring that any unavailable
communication system automatically
disables distributed backup mechanism.
Application class
Class 1 – Communication with high
bandwidth
Class 2 – Deterministic communication with
high bandwidth
Class 3 – deterministic and redundant
communication with high bandwidth
Header segment
Payload segment – useful data
Trailer segment - end of frame
Bit coding
Non return to zero, transmission of each
byte is framed by a start and stop bit
Bit rate
Nominal value of 100ns, implying a
gross bit rate of 100Mbps
Network topology will all have major
effects on quality of bit carried.
Fault tolerance mechanism