From: Oliver Hartkopp <oliver.hartkopp@volkswagen.de>
To: Sebastian Haas <dev@sebastianhaas.info>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: RxFilter issues vcan
Date: Thu, 30 May 2013 10:49:28 +0200 [thread overview]
Message-ID: <51A71298.1070202@volkswagen.de> (raw)
In-Reply-To: <51A70F0E.1010902@sebastianhaas.info>
Am 30.05.2013 10:34, schrieb Sebastian Haas:
> Hi,
>
> Am 30.05.2013 06:58, schrieb Oliver Hartkopp:
>> On 29.05.2013 22:55, Sebastian Haas wrote:
>>> Hello everybody,
>>>
>>> I played a bit with the RxFilters and noticed that they are behaving somewhat
>>> strange.
>>>
>>> If I start candump this way:
>>> sh@helios:~/workspace/node-can$ candump vcan0,100~7ff,101~7ff
>>> I want to receive any messages except 100h and 101h.
>>>
>>> When I send a message which matches the filter, it is received twice:
>>> sh@helios:~/workspace/node-can$ cansend vcan0 1ff#22
>>> vcan0 1FF [1] 22
>>> vcan0 1FF [1] 22
>>>
>>> When I send a message which should not received at all, it is received:
>>> sh@helios:~/workspace/node-can$ cansend vcan0 100#22
>>> vcan0 100 [1] 22
>>>
>>> Did I misunderstood the filter here?
>>
>> The filters are independent and therefore "logical OR".
> Ok. That explain why received 100h even though I tried to filter it out. But
> why receive a message twice while it was only sent once?
You have defined two(!) filters that let pass the CAN-ID 0x1FF.
So what else would you expect?
:-)
>
> Sebastian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-30 8:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 20:55 RxFilter issues vcan Sebastian Haas
2013-05-30 4:58 ` Oliver Hartkopp
2013-05-30 8:34 ` Sebastian Haas
2013-05-30 8:49 ` Oliver Hartkopp [this message]
2013-05-30 9:06 ` Sebastian Haas
2013-05-30 10:17 ` RFC: (optional) software filtering in candump Kurt Van Dijck
2013-05-30 12:07 ` Oliver Hartkopp
2013-05-30 12:35 ` Kurt Van Dijck
2013-05-30 15:37 ` Sebastian Haas
2013-05-30 15:55 ` Oliver Hartkopp
2013-05-31 20:40 ` Sebastian Haas
2013-06-01 14:15 ` Oliver Hartkopp
2013-06-01 18:35 ` Sebastian Haas
2013-06-02 9:59 ` RFC SFF bitfield filter - was " Oliver Hartkopp
2013-06-02 11:17 ` Kurt Van Dijck
2013-06-02 12:23 ` Sebastian Haas
2013-06-02 11:23 ` Kurt Van Dijck
2013-06-04 8:22 ` AW: " Sandro Anders | CarMedialab
2015-03-17 10:44 ` Marc Kleine-Budde
2015-03-17 11:34 ` Marc Kleine-Budde
2015-03-17 12:04 ` Oliver Hartkopp
2015-03-17 13:02 ` Oliver Hartkopp
2015-03-17 13:33 ` Marc Kleine-Budde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51A71298.1070202@volkswagen.de \
--to=oliver.hartkopp@volkswagen.de \
--cc=dev@sebastianhaas.info \
--cc=linux-can@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).