From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Felix Seitz <felix.seitz@thm-motorsport.de>, linux-can@vger.kernel.org
Subject: Re: cansniffer loop time
Date: Tue, 24 Jun 2014 17:35:25 +0200 [thread overview]
Message-ID: <53A99ABD.7020407@pengutronix.de> (raw)
In-Reply-To: <53A99784.5020609@thm-motorsport.de>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
Hey Felix,
On 06/24/2014 05:21 PM, Felix Seitz wrote:
> we from THM Motorsport are using the cansniffer running on a Raspberry
What is "the cansniffer"?
> Pi to read out sensor data traffic on the CANbus in our car.
> I would like to set the cansniffer's loop time lower than 100ms. I tried
> to changing the source code but apparently I don't fully understand
> where the loop delay comes from.
> Could you give me some tips on how to set a lower delay for the
> cansniffer? 20ms delay would be perfect.
Despite the fact, that the rpi is not the best hardware/software for
doing CAN under Linux, there is no delay within the Linux Kernel that
would cause a loop delay.
If you see such a delay it's probably in the application of "the
cansniffer". The rpi has no CAN controller on the board, there are
several possibilities to upgrade CAN support. The worst solution is to
attach an mcp2515 via SPI, USB based CAN dongles give much better
performance. However USB on the rpi is quite bad, too...
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 242 bytes --]
next prev parent reply other threads:[~2014-06-24 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 15:21 cansniffer loop time Felix Seitz
2014-06-24 15:35 ` Marc Kleine-Budde [this message]
2014-06-24 15:44 ` Oliver Hartkopp
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=53A99ABD.7020407@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=felix.seitz@thm-motorsport.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.