From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Janusz Uzycki <janusz.uzycki@elproma.com.pl>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: slcanpty
Date: Wed, 05 Jun 2013 21:44:13 +0200 [thread overview]
Message-ID: <51AF950D.1050004@hartkopp.net> (raw)
In-Reply-To: <2DAB3DC2841347E7AF7833620339B427@laptop2>
Hi Janusz,
the slcanpty programm is just some kind of proof of concept to make applications
run, that use the slcan ASCII protocol.
E.g. http://www.port.de/en/products/canopen/diagnose/can-analyzer-can-report.html
which has the LAWICEL CAN hardware as possible hardware:
See at www.canusb.com
If you would like to have a "remote control" via IP networking for SocketCAN,
I would recommend the socketcand:
https://github.com/dschanoeh/socketcand
Please google for "socketcand", there's a video also ...
http://www.youtube.com/watch?v=6vqCu1WY2F8
Regards,
Oliver
On 05.06.2013 18:24, Janusz Uzycki wrote:
> Hi Oliver.
>
> I want to use slcanpty as mcp251x socket-CAN to TCP server in order to check
> CAN open (via CAN festival). Do you happen to know it is good idea?
> I noticed some obstacles:
> - the program uses select() for stdin - what is a reason instead of signals?
> Some workaround is to call slcanpty /dev/ptmx can0 < /dev/ptmx & because
> /dev/null does not support select() and code finishes immediately.
> - why did you comment out filter settings M/m? What did you mean by "the
> filter is no SocketCAN filter :-(" exactly?
> - the program does not finishes if PTY was closed - errno should be checked
> otherwise the main loop runs very fast (select() does not wait)
> Good point for me is to use eg. stdin/out instead of PTY. However the program
> seems to work ok with socat's PTY.
>
> best regards
> Janusz Uzycki
>
next parent reply other threads:[~2013-06-05 19:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2DAB3DC2841347E7AF7833620339B427@laptop2>
2013-06-05 19:44 ` Oliver Hartkopp [this message]
2013-06-06 12:03 ` slcanpty Janusz Uzycki
2013-06-06 18:31 ` slcanpty Oliver Hartkopp
2013-06-06 20:43 ` slcanpty janusz.uzycki
2013-06-07 13:40 ` [PATCH] slcanpty janusz.uzycki
2013-06-08 11:09 ` Oliver Hartkopp
2013-06-10 9:06 ` janusz.uzycki
2013-06-10 9:16 ` janusz.uzycki
2013-06-10 9:36 ` janusz.uzycki
2013-06-10 9:42 ` [PATCH 1/2] slcanpty: "slcanpty < /dev/null" issue fix janusz.uzycki
2013-06-10 9:44 ` [PATCH 2/2] slcanpty: /dev/tty support for tests janusz.uzycki
2013-06-10 9:53 ` janusz.uzycki
2013-06-10 18:29 ` Oliver Hartkopp
2013-06-10 18:38 ` janusz.uzycki
2013-06-11 20:28 ` Oliver Hartkopp
2013-06-11 16:29 ` slcanpty janusz.uzycki
2013-06-11 20:32 ` slcanpty Oliver Hartkopp
2013-06-11 21:19 ` slcanpty janusz.uzycki
2013-06-12 15:25 ` slcanpty Oliver Hartkopp
2013-06-14 8:42 ` slcanpty Janusz Uzycki
2013-06-18 8:24 ` slcanpty j.uzycki
2013-06-19 17:15 ` slcanpty Oliver Hartkopp
2013-06-19 22:39 ` slcanpty j.uzycki
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=51AF950D.1050004@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=janusz.uzycki@elproma.com.pl \
--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).