|This article needs additional citations for verification. (January 2008)|
FlexRay is an automotive network communications protocol developed by the FlexRay Consortium to govern on-board automotive computing. It is designed to be faster and more reliable than CAN and TTP, but it is also more expensive. VisualSim FlexRay library  enables a system designer to construct models of complex standard and non-standard FlexRay topologies. This graphical model of the FlexRay topology can contain any number of nodes that transmit across the static and dynamic slots. The FlexRay consortium disbanded in 2009. The FlexRay standard is now a set of ISO standards ISO 17458-1 to 17458-5 
FlexRay supports high data rates, up to 10 Mbit/s, explicitly supports both star and "party line" bus topologies, and can have two independent data channels for fault-tolerance (communication can continue with reduced bandwidth if one channel is inoperative). The bus operates on a time cycle, divided into two parts: the static segment and the dynamic segment. The static segment is preallocated into slices for individual communication types, providing a stronger real-time guarantee than its predecessor CAN. The dynamic segment operates more like CAN, with nodes taking control of the bus as available, allowing event-triggered behavior.
The FlexRay Consortium was made up of the following core members:
- Freescale Semiconductor
- Robert Bosch GmbH
- NXP Semiconductors
- BMW AG
- Volkswagen AG
- Daimler AG
- General Motors
There were also Premium Associate and Associate members of FlexRay consortium. By September 2009, there were 28 premium associate members and more than 60 associate members. At the end of 2009, the consortium disbanded.
The first series production vehicle with FlexRay was at the end of 2006 in the BMW X5, enabling a new and fast adaptive damping system. Full use of FlexRay was introduced in 2008 in the new BMW 7 Series (F01).
- Audi A6
- Audi A8
- Bentley Mulsanne
- BMW X5
- BMW 3-Series
- BMW 7-Series
- BMW 5 Series Gran Turismo
- BMW 5-Series
- Mercedes-Benz S-Class
- Rolls-Royce Ghost
FlexRay system consists of a bus and processors (Electronic control unit, or ECUs). Each ECU has an independent clock. The clock drift must be not more than 0.15% from the reference clock, so the difference between the slowest and the fastest clock in the system is no greater than 0.3%.
This means that, if ECU-s is a sender and ECU-r is a receiver, then for every 300 cycles of the sender there will be between 299 and 301 cycles of the receiver. The clocks are resynchronized frequently enough to assure that this causes no problems. Clock is sent in static segment.
Bits on the bus
Correct averaging in case of no errors. The signal is merely delayed by 2 cycles.
Errors near the middle of 8-cycle region are canceled.
Errors near the boundary of 8-cycle region may affect the boundary bit.
At each time, only one ECU writes to the bus. Each bit to be sent is held on the bus for 8 sample clock cycles. The receiver keeps a buffer of the last 5 samples, and uses the majority of the last 5 samples as the input signal.
Single-cycle transmission errors may affect results near the boundary of the bits, but will not affect cycles in the middle of the 8-cycle region.
The value of the bit is sampled in the middle of the 8-bit region. The errors are moved to the extreme cycles, and the clock is synchronized frequently enough for the drift to be small. (Drift is smaller than 1 cycle per 300 cycles, and during transmission the clock is synchronized more than once every 300 cycles).
All the communication is sent in the form of frames. The message consists of bytes , packed in the following way:
- Transmission Start Signal (TSS) – bit 0
- Frame Start Signal (FSS) – bit 1
- m times:
- Byte Start Signal 0 (BSS0) – bit 1
- Byte Start Signal 1 (BSS1) – bit 0
- 0-th bit of i-th byte
- 1-st bit of i-th byte
- 2-nd bit of i-th byte
- 7-th bit of i-th byte
- Frame End Signal (FES) – bit 0
- Transmission End Signal (TES) – bit 1
If nothing is being communicated, the bus is held in state 1 (high voltage), so every receiver knows that the communication started when the voltage drops to 0.
The receiver knows when the message is complete by checking whether BSS0 (1) or FES (0) was received.
Note that 8-cycle per bit has nothing to do with bytes. Each byte takes 80 cycles to transfer. 16 for BSS0 and BSS1 and 64 for its bits. Also note that BSS0 has value 1, and BSS1 has value 0.
Clocks are resynchronized when the voted signal changes from 1 to 0, if the receiver was in either idle state or expecting BSS1.
As synchronization is done on the voted signal, small transmission errors during synchronization that affect the boundary bits may skew the synchronization no more than 1 cycle. As there are at most 88 cycles between synchronization (BSS1, 8 bits of the last byte, FES and TES - 11 bits of 8 cycles each), and the clock drift is no larger than 1 per 300 cycles, the drift may skew the clock no more than 1 cycle. Small transmission errors during the receiving may affect only the boundary bits. So in the worst case the two middle bits are correct, and thus the sampled value is correct.
Here's an example of a particularly bad case - error during synchronization, a lost cycle due to clock drift and error in transmission.
Errors that happened in the example
- Because of a single-bit error during synchronization, the synchronization was delayed by 1 cycle
- Receiver clock was slower than sender clock, so receiver missed one cycle (marked X). This will not happen again before the next synchronization due to limits on maximum allowable clock drift.
- Because of a single-bit error during transmission, a bit was voted wrongly near the result.
Despite so many errors, the communication was received correctly.
The green cells are sampling points. All except the first are synchronized by the 1->0 edge in the transmission fragment shown.
|Signal to be sent||1||0||1||0||1|
|On the bus||1||1||1||1||1||1||1||1||0||1||0||0||0||0||0||0||1||1||1||1||1||1||1||1||0||0||0||0||0||0||1||0||1||1|
When developing and/or troubleshooting the FlexRay bus, examination of hardware signals can be very important. Logic analyzers and bus analyzers are tools which collect, analyze, decode, store signals so people can view the high-speed waveforms at their leisure.
The future of FlexRay
The bus has certain disadvantages like lower operating voltage levels and asymmetry of the edges, which leads to problems in extending the network length. Ethernet may replace FlexRay for bandwidth intensive, non-safety critical applications.
- Controller Area Network (CAN)
- Local Interconnect Network (LIN) - lower cost and lower bandwidth than CAN
- "VisualSim FlexRay Library"
- The FlexRay Electrical Physical Layer Evolution; Automotive 2010.
- "How FlexRay Works". Retrieved 21 March 2014.
- "2011 Audi A8 4.2 FSI First Drive". Retrieved 18 February 2010.
- http://www.eetimes.com/document.asp?doc_id=1256700. Retrieved 21 July 2013. Missing or empty
- FlexRay FlexRay Consortium
- FlexRay Starter Kit Low cost FlexRay Starter Kit with the BOSCH E-Ray controller from DuxSolutions, also FlexRay Network Design tool available
- FlexRay Overview Technical Overview of FlexRay by National Instruments
- Flexray Products Samtec FlexRay product
- Flexray design tool Low cost network design tool for FlexRay
- FlexRay controller core Free VHDL core
- FlexRay debugging Measurement, Debug and Analysis for Embedded Automotive Designs by Tektronix