From: Wolfgang Grandegger <wg@domain.hid>
To: "Berruer Sébastien" <sebastien.berruer@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] RE : State of implementation of CAN, CANOpen in Xenomai
Date: Thu, 23 Jul 2009 19:08:19 +0200 [thread overview]
Message-ID: <4A689903.5010107@domain.hid> (raw)
In-Reply-To: <EB48F2CADC239E44A8598CC0B0571102E4A99E@XVS-DCFR-21.europe.corp.altran.com>
Berruer Sébastien wrote:
> I'm on the first step of the project and I have to choose a complete
> system for my customer. I looking at the constraints both for hardware
> and software and the possibly dependency between them.
OK.
>> 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.
>
> Sorry, I've made a misunderstood about the CAN organization. In fact,
> the RT-Socket-CAN is a kind of user API for ease the use of CAN bus,
> isn't it? It seems that, generally, the handling of protocol, like the
> access to media or arbitration, is done in the chip.
Yep.
>> 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.
>
> My client asks for a complete implementation of the CANOpen protocol. I
> will take all a look at this site and if it's clear for that use.
Usually, only a sub-set of the CANopen protocol is implemented.
Wolfgang
prev parent reply other threads:[~2009-07-23 17:08 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
2009-07-23 10:00 ` [Xenomai-help] RE : " Berruer Sébastien
2009-07-23 17:08 ` Wolfgang Grandegger [this message]
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=4A689903.5010107@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.