CANedge2 Docs, Release FW 01.04.02
• Filter from: 500
10
• Filter to: 1000
10
The filter list is constructed with the rejection filter first, followed by the acceptance filter.
Note that messages are first processed by the rejection filter (rejects all odd messages), then
proccessed by the acceptance filter (accepts all message in range). If none of the filters
pass/match, the default behavior is to reject the message. It is in this case important that
the rejection filter is placed before the acceptance filter in the list (processing stops on first
match).
Filter list test table:
Message ID Filter elm 1 Filter elm 2 Result
498
10
Ignore Ignore Reject
499
10
Reject Reject
500
10
Ignore Accept Accept
501
10
Reject Reject
999
10
Reject Reject
1000
10
Ignore Accept Accept
1001
10
Reject Reject
1002
10
Ignore Ignore Reject
Message Prescaling
Message prescaling can be used to decrease the number of logged messages for a given message ID.
Prescaling is applied to the messages accepted by the associated filter. The list of filters can be assigned
a mixture of prescaler types.
Applying filters can dramatically reduce log file size, resulting in prolonged offline logging and reduced
data transfer time and size.
The prescaling type can be set to:
• None: Disables prescaling
• Count: Prescales based on the number of messages
• Time: Prescales based on message period time
• Data: Prescales based on changes in the message data payload
The first message with a given ID is always accepted regardless of prescaling type.
Note: A maximum of 100 unique message IDs can be prescaled for each CAN-bus channel (the first
100 IDs received by the device). Additional unique IDs are not prescaled
Count
Count prescaling reduces the number of messages with a specific ID by a constant factor (prescaling
value). A prescaling value of 2 accepts every 2nd message (with a specific ID), a value of 3 every 3rd
and so on up to 256
2
.
Count prescaling applied to ID 600
10
with a scaling value of 3
2
A scaling factor of 1 effectively disables prescaling
0.4. Configuration 29
To Next Page
Loading...