|
The Trace module provides the following trigger types:
|
The trigger condition of the Message Count Trigger
to start or stop the trace recording is fulfilled after reception of the
configured number of messages. |
|
|
The trigger condition of the ID/Data Trigger is
fulfilled after a message with a specified identifier and/or specified data is
received. |
|
|
The trigger condition of the Remote/Errorframe Trigger
is fulfilled after an error frame and/or a remote frame with specified data
and/or identifier is received. |
Generally a distinction is made between two Trigger-Events:
|
|
Start-Trigger-Event: determines the start of a Trace-recording
|
|
|
Stop-Trigger-Event: determines the abort of a Trace-recording
|
If no start trigger is specified, the trace recording starts immediately. If no
stop trigger is specified, the recording will run until the maximum possible
recording length is reached or until the user aborts the recording. A Trace can
be stopped at any time by the user, unaffected of specified triggers.
The configuration of the trigger conditions is made over the context menu of the
controller in the list Bus Configuration in the record mode of the Trace
module. Right click to a controller and select the entry Start Trigger | Select
Trigger or Stop Trigger | Select Trigger
In the next step a list box is opened, which allows the selection of the desired
trigger type.
To start the trace redording after the reception of 200 messages, specify a Message
Count Trigger as start trigger and enter the value "200". Start the
transmission in the Sequencer module and view the recorded messages after the
Sequencer module has finished transmission.
For triggering to data contents at the ID/Data Trigger and Remoteframe
Trigger, two entries are used:
|
|
Mask |
|
|
Value |
Mask states the position of the relevant bits in the identifier or data
field, Value states the value that these bits must assume. A trigger
condition can thus also include several combinations of identifiers and data.
If for example triggering to identifiers 0x400 to 0x403 in the ID/Data Trigger
is to be carried out, 0x7FC is entered for the mask and 0x400 for the value
(standard CAN-protocol). For the evaluation of the trigger condition, the
received identifier is AND-joined to the mask and compared with the value. If
there is coincidence, the Trigger occurs. The entry for the data field is made
in the same way.
The masks or values for the identifier and each individual byte of the eight
data bytes can be generated by deleting/setting individual bits. By repeated
clicking, the buttons switch between three states:
|
|
X -> bit is not relevant |
|
|
0 -> bit is relevant and must have the value 0 |
|
|
1 -> bit is relevant and must have the value 1 |
Set an ID/Data Trigger as start tirgger and specify it for messages with
the identifiers 0x400 to 0x403. Additionally set the mask for the first data
byte to "0xFF" and the corresponding value to "0x0F", this will only cause a
trigger event if the first data byte has the value "0x0F". Start the
transmission in the Sequencer module and view the recorded messages after the
Sequencer module has finished transmission.
Now use a Remote/Errorframe Trigger as start trigger. Specify the trigger
for messages with the identifiers 0x400 to 0x403 and set the message length to
"3". Start the transmission in the Sequencer module again and view the recorded
messages.
|
