23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

FlexRay 44-3<br />

Header segment (5 bytes)<br />

Payload segment<br />

(0 ... 254 bytes)<br />

Trailer segment<br />

(3 bytes)<br />

Reserved bit<br />

Payload preamble indicator<br />

Nullframe indicator<br />

Sync frame indicator<br />

Startup frame indicator<br />

Frame identifier<br />

Payload length Header CRC Cycle count Payload Frame CRC<br />

FIGURE 44.2<br />

Frame format.<br />

44.2.2 Framing<br />

A frame sent in either the static or dynamic segment consists of a header, the payload, and a trailer.<br />

The 5-byte long header is made up of five control bits, an 11 bit long frame identifier, a payload length<br />

field, a header cyclic redundancy checksum (CRC), and a cycle count field; cf. Figure 44.2. The header<br />

CRC secures the sync frame indicator bit, the startup frame indicator control bit, the frame identifier,<br />

and the payload length field. The payload holds an even number of bytes (between 0 and 254) that carry<br />

the application data. When the payload preamble indicator control bit in the header is set, a part of<br />

the payload in the static segment is reserved for network management information. Special cases are<br />

nullframes that are identified by the nullframe indicator control bit set in the header; these frames have<br />

all the payload bits set to zero. Null frames are sent autonomously by the network controller whenever<br />

no new data are at hand from the node’s host. The trailer contains a CRC over the entire frame with a<br />

Hamming distance of 6 for frame lengths up to 248 bytes payload and a Hamming distance of 4 for<br />

frame lengths between 249 and 254 bytes payload. With a Hamming distance of 6, up to 5 arbitrary bit<br />

flips can be detected.<br />

44.2.3 Startup of a Cluster<br />

When the cluster is not running (e.g., after power-up) the host of a dedicated, so-called coldstart node<br />

may try to start the cluster. It sends a collision avoidance symbol and waits for a response within a configured<br />

time. When no response is received, the node stops its start-up attempts and waits for an attempt<br />

from another node to start the cluster. When the latter occurs, the leading coldstart node will reply and<br />

synchronize its timebase. Both nodes will now make the transition to an active state and other noncoldstart<br />

nodes may join the cluster, see [FE05] or [R08] for details.<br />

44.2.4 Physical Layer<br />

FlexRay employs a variant of the inverted non-return-to-zero (NRZ-I) coding for bit transmission.<br />

A standard NRZ-I code represents a “One” with a change in the physical level whereas a “Zero” is with<br />

no change. The modification of the employed coding consists of a byte-start sequence (the bit combination<br />

“10”) that is prepended to every byte. The falling edge between these two bits is used for bitresynchronization.<br />

Furthermore, every frame transmission is prepended by a transmission start and a<br />

frame start sequence. The transmission start sequence consists of 3–15 bits and is used to activate star<br />

couplers. Since activation takes some time, a few bits of the transmission start sequence are usually<br />

consumed by them. Furthermore, the end of a frame is followed by a frame end sequence consisting of<br />

the bits “01,” and an idle phase where the transmitter is turned off. Figure 44.3 illustrates the coding of<br />

an entire FlexRay frame.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!