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

Example for Triggering on Slopes/Edges

Last updated: 2019-10-21

The following LTL example triggers logging on a slope change of a signal, e.g. from 0 to1, from 0 to 7, from 2 to 6, from 5 to 0, but not on constant values of this signal.


_Sig1 is the signal that is observed and will cause the trigger to fire. It is contained in the message _Bot1 received on CAN1. This symbolic representation of messages and signals can be used when including DBCs to your logging configuration and converting them to INC files for symbolic name usage.



output LED1=(1)
          LED2=(Trigger)  { light up LED2 when Trigger occurs}

    On RECEIVE (CAN1 _Bot1) BEGIN  { on reception of the message _Bot1 on CAN1 that contains the triggering signal}
        SIGNAL_NOW= _Sig1  { _Sig1 is the signal that triggers, e.g. from an included DBC file }
STOP 1 (Trigger)
START 1 (not Trigger)



For the GL Loggers the Vector Logger Configurator 2.5 and higher allows triggers on signal changes. Select on the trigger page On change as relational operator for the selected signal.  

Article Options
Views: 646