From: Oliver Hartkopp <socketcan@hartkopp.net>
To: kay Cee <unee0x@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Can bus simulator
Date: Wed, 13 Apr 2016 09:14:40 +0200 [thread overview]
Message-ID: <570DF1E0.7090504@hartkopp.net> (raw)
In-Reply-To: <86DFA4E2-8971-48B1-852D-82DFAFA957DF@gmail.com>
You can use the virtual CAN interfaces, see
https://www.kernel.org/doc/Documentation/networking/can.txt
Chapter 6.4
Regards,
Oliver
On 04/13/2016 08:17 AM, kay Cee wrote:
> Is there a way to test a canbus tester without actual can signals?
>
> I have a can bus testing station but no can signals readily available..
>
> Sent from my iPhone
> --
> 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:[~2016-04-13 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 6:17 Can bus simulator kay Cee
2016-04-13 7:14 ` Oliver Hartkopp [this message]
2016-04-13 7:29 ` Pavel Pisa
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=570DF1E0.7090504@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=unee0x@gmail.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).