26 (36)
►
To load the logger configuration to the device, open menu
Build
and select
Download
.
→
IxAdmin is started.
►
Load the logger configuration with IxAdmin to the CANnector Log (see
Configurations to the Device, p. 28
).
7.2.4
Using Signals as Trigger
Fig. 27
Trigger when message Test is received
►
In source (
1
) select the CAN bus to be logged and select tab
ECUs
(
1
).
►
In drop-down list
Map Subject
select
Signal
(
5
)
►
Select tab
Trigger
(
4
) as destination.
►
Drag and drop the desired trigger signal from source (
1
) to destination trigger (
4
).
→
The mapped signal is the input signal (
2
).
►
To define the logic, right-click in the trigger window.
→
Menu with possible function blocks is opened:
Function block
Description
New trigger signal
Output of the trigger engine, can be used in the logger to start/stop the
recording or being mapped to any other signal of the configuration.
New clock
Can be used as input for the trigger engine, intended to start the logging
at a certain time/day based on the realtime clock of the CANnector.
New counter
Used as a counter, that counts down every time an input event is
available (for example an input trigger signal). Can be used for example
to start the logger only after a certain count of events.
New debouncing
Delays the output signal a certain amount of time after having received
a input signal.
New flipflop
Stores a certain sporadic event, for example to keep it available for a
later comparison.
New threshold
Compares the input signal with a certain value. A threshold is needed
for every trigger input signal. In case of a message as trigger input
signal, the comparison should be greater than 0.
New timer
Delays the output for a definable amount of time, can be used for
example to stop the recording after a specified period of time after the
start.
New OR, XOR, AND, NOT
Can be used for logical comparison of two input signals.
►
Add the desired function blocks to the trigger window.
CANnector Log User Manual
4.01.0091.21000 1.1 en-US
