From: Tom Evans <tom_usenet@optusnet.com.au>
To: Mike Purvis <mpurvis@clearpathrobotics.com>,
Armin Burchardt <armin@uni-bremen.de>
Cc: linux-can@vger.kernel.org
Subject: Re: Standard CAN over IP
Date: Thu, 05 Feb 2015 11:50:22 +1100 [thread overview]
Message-ID: <54D2BE4E.7090202@optusnet.com.au> (raw)
In-Reply-To: <CACsJT9NuErtQOxTXffx=WYS5j6u8A-mv1XuA6Jxusn+tcDSRrw@mail.gmail.com>
On 05/02/15 08:38, Mike Purvis wrote:
> Armin—
>
> Fantastic, thanks for the pointer, this is just what I was looking
> for. I've given it a quick try, and the binary in Ubuntu 14.04's
> can-utils package appears to do what I want in terms of creating a net
> device.
>
> For future travellers, the protocol is documented in the slcan.c
> source file, from the kernel tree:
That Kconfig in drivers/net/can also has the following in it:
config CAN_SLCAN
As only the sending and receiving of CAN frames is implemented,
this driver should work with the (serial/USB) CAN hardware from:
www.canusb.com / www.can232.com / www.mictronics.de /
www.canhack.de
If your PC has spare serial ports, or if you want to buy some reliable
USB-to-serial converters, then you might want to consider the above-mentioned
serial-to-can devices:
http://www.can232.com/?page_id=14
Or the normal USB ones on the above site. They might be cheap enough for you.
Or you could start here:
http://www.mictronics.de/projects/usb-can-bus/
Tom
next prev parent reply other threads:[~2015-02-05 0:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 20:27 Standard CAN over IP Mike Purvis
2015-02-04 20:44 ` Armin Burchardt
2015-02-04 21:38 ` Mike Purvis
2015-02-04 22:42 ` Gerhard Bertelsmann
2015-02-05 0:50 ` Tom Evans [this message]
2015-02-05 13:15 ` Mike Purvis
2015-02-06 8:33 ` Michal Sojka
2015-02-09 16:00 ` Mike Purvis
2015-02-09 18:32 ` Oliver Hartkopp
2015-02-04 23:43 ` Tom Evans
2015-02-18 17:57 ` Maximilian Güntner
[not found] ` <CACsJT9M4QbYkDvQkGfhFuwA6haNyV5zesUFtLzB5VEbxP=obBA@mail.gmail.com>
2015-02-19 3:21 ` Mike Purvis
2015-02-19 14:58 ` Maximilian Güntner
2015-02-20 11:43 ` Oliver Hartkopp
2015-02-23 12:25 ` Maximilian Güntner
2015-02-23 13:08 ` Oliver Hartkopp
2015-02-23 14:27 ` Maximilian Güntner
2015-02-23 16:22 ` Oliver Hartkopp
2015-03-20 16:54 ` Maximilian Güntner
2015-03-23 10:28 ` Pankajkumar Misra (RBEI/EEA2)
2015-03-23 13:15 ` Maximilian Güntner
2015-03-23 16:57 ` Pankajkumar Misra (RBEI/EEA2)
2015-03-23 13:23 ` GARNERO, PIERRE (P.)
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=54D2BE4E.7090202@optusnet.com.au \
--to=tom_usenet@optusnet.com.au \
--cc=armin@uni-bremen.de \
--cc=linux-can@vger.kernel.org \
--cc=mpurvis@clearpathrobotics.com \
/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).