From: Wolfgang Grandegger <wg@domain.hid>
To: "Berruer Sébastien" <sebastien.berruer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] State of implementation of CAN, CANOpen in Xenomai
Date: Thu, 23 Jul 2009 11:13:58 +0200 [thread overview]
Message-ID: <4A6829D6.9060301@domain.hid> (raw)
In-Reply-To: <EB48F2CADC239E44A8598CC0B0571102E4A99D@XVS-DCFR-21.europe.corp.altran.com>
Berruer Sébastien wrote:
> Hello,
>
> I'm reviewing the feasibility of a project that would require the driving of
> devices with real time constrains.
OK, then RT-Socket-CAN is a good choice.
> I'm asking for the current state of the CAN implementation. Is it a
> partial or a
> complete implementation of the CAN standard? What are the guarantee
> about real
> time latency?
What exactly do you mean with CAN standard? RT-Socket-CAN allows
low-level access the CAN controller to send and receive messages, handle
errors and set the bit-timing. Standard, extended and RTR frames are
supported.
> I explored briefly the sources of Xenomai, and I read the file
> "ksrc/drivers/can/README". Is it up-to-date? Is there really only
> support for
> the controllers listed in it?
Mainly yes, what CAN controller would you like to use? Writing a
RT-Socket-CAN driver is usually not a big deal.
> I've read in "RTDM and applications" that there would be an effort for
> implementing a CANOpen profile. But, the implementation of CANOpen
> protocol is
> let to users? I can't find any newer reference for that in sources or in the
> documentation of Xenomai. What is the state of this project?
If you are looking for a free CANopen implementation, CANfestival might
be an option, which also supports RT-Socket-CAN, IIRC. Check
http://canfestival.org/ for further information.
> I've seen that there is currently only one implementation of a RT driver
> for the
> 16550A serial controller. Has anybody implemented it for other chip?
What chip/hardware do you have in mind?
> If I finally decide to choose a RT-Patch, instead of Xenomai, I will
> have the
> CAN implementation that will use the Linux networking stack. But I will
> not have
> any guarantee about its real time implementation, isn't it?
The Linux network stack is not hard real-time capable and the real-time
preemption patch will only help partially.
Wolfgang.
next prev parent reply other threads:[~2009-07-23 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-23 8:17 [Xenomai-help] State of implementation of CAN, CANOpen in Xenomai Berruer Sébastien
2009-07-23 9:13 ` Wolfgang Grandegger [this message]
2009-07-23 10:00 ` [Xenomai-help] RE : " Berruer Sébastien
2009-07-23 17:08 ` Wolfgang Grandegger
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=4A6829D6.9060301@domain.hid \
--to=wg@domain.hid \
--cc=sebastien.berruer@domain.hid \
--cc=xenomai@xenomai.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.