Search tips

apple banana
Find rows that contain at least one of the two words.

+apple +juice
Find rows that contain both words.

+apple macintosh
Find rows that contain the word 'apple', but rank rows higher if they also contain 'macintosh'.

+apple -macintosh
Find rows that contain the word 'apple' but not 'macintosh'.

+apple ~macintosh
Find rows that contain the word 'apple', but if the row also contains the word 'macintosh', rate it lower than if row does not. This is "softer" than a search for '+apple -macintosh', for which the presence of 'macintosh' causes the row not to be returned at all.

+apple +(>turnover >strudel)
Find rows that contain the words 'apple' and 'turnover', or 'apple' and 'strudel' (in any order), but rank 'apple turnover' higher than 'apple strudel'.

Find rows that contain words such as 'apple', 'apples', 'applesauce', or 'applet'.

"some words"
Find rows that contain the exact phrase 'some words' (for example, rows that contain 'some words of wisdom' but not "some noise words").

By continuing to use this site you agree to the use of cookies. For more information and to find out how to change this click here. Accept Cookies
Please enable cookies in your browser for this website.
Advanced search

FlexRay-FlexRay synchronization with CANoe as gateway

Last updated: 2019-04-16

One FlexRay bus provides a global system time on which all ECUs can synchronize. When two FlexRay buses are required, they run normally independently of each other. Even if both buses implement the same schedule, they have an offset to each other and they possibly drift. The synchronous FlexRay time for ECUs on the different buses gets lost.

Moreover, when data must be transferred from one bus to the other, a so-called FlexRay – FlexRay gateway creates a non-negligible delay in terms of multiples of the cluster’s period (in any of the directions), because of the time-triggered bus access. For event-triggered buses (like CAN) the delay only depends (on low bus loads) nearly on the reaction delay (which is much smaller than the message’s cycle period) of the gateway application.

Additionally, due to a normally non-existing synchronization between both FlexRay clusters, they will drift to each other. Therefore, the routing delay may vary during run-time and is in-deterministically.

For details, see Vector Application Note:
AN-IND-1-010 FlexRay-FlexRay synchronization with CANoe as gateway

Article Options
Views: 2651
Rate this article: