From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Michael Luxen <mluxen@gmx.net>
Cc: linux-can Mailing List <linux-can@vger.kernel.org>
Subject: Re: AW: Web GUI for can-utils (i.e. cangw, cansend, candump)
Date: Mon, 10 Jun 2013 20:22:56 +0200 [thread overview]
Message-ID: <51B61980.5060302@hartkopp.net> (raw)
In-Reply-To: <zarafa.51b5ff24.7028.506b738f3f6d3b02@v14647.1blu.de>
On 10.06.2013 18:30, Michael Luxen wrote:
> Thnak you for pointing me to the interestin toolchain with .kcd files (CANbabel translator), socketcand and Kayak.
> Nevertheless I did some tests last weekend on my BeagleBone Black setup with DCAN0/DCAN1.
>
> If I fire round about 37%@500kbit/s to DCAN0 I get a tast load of round about 45% of socketcand. In general it's possible for me to use Kayak on i.e. my Windows machine and connect to my BeagleBone Black via ethernet. But if I use the second CAN channel (DCAN1) or increase the busload of channel one (DCAN0) the taskload/CPUload increases unacceptable.
>
> Did you have the same experience with socketcand and Kayak?
Usually we use it with localhost IP communication.
An in the rare cases we use a MPC5200@400MHz based embedded system with two
CAN interfaces without any problems so far.
> Why isn't it possible to connect directly to the can0/can1 socketcan interfaces without socketcand?
Kayak is Java based. And Java does not support PF_CAN sockets. Therefore the
workaround via IP networking was necessary.
Best regards,
Oliver
next prev parent reply other threads:[~2013-06-10 18:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 16:30 AW: Web GUI for can-utils (i.e. cangw, cansend, candump) Michael Luxen
2013-06-10 18:22 ` Oliver Hartkopp [this message]
2013-06-11 9:54 ` Mohamed HAMZAOUI
-- strict thread matches above, loose matches on Subject: below --
2013-06-16 8:18 Michael Luxen
2013-06-19 17:29 ` 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=51B61980.5060302@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mluxen@gmx.net \
/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).