From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Anil Mathews (India - Bangalore)" <anil.mathews@mindteck.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Rob__V <r.valler@enextra.de>
Subject: Re: [Socketcan-users] Socketcan-users Digest, Vol 77, Issue 2
Date: Tue, 20 Aug 2013 13:02:40 +0200 [thread overview]
Message-ID: <52134CD0.5030209@pengutronix.de> (raw)
In-Reply-To: <8A49CFF5759B8644A46158D75AFC117D68584B51@AUSP01DAG0102.collaborationhost.net>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
On 08/20/2013 12:42 PM, Anil Mathews (India - Bangalore) wrote:
> Hi Rob,
> As per my understanding every CAN node should have a hardcoded
> address accessed from rotary switch,or read from eeprom etc.Every
> message ID should be anded with this CAN ID so that each message will
> be unique in the network.Now each individual CAN nodes will process
> these messages using their filter and mask and if it matches they can
> extract the CAN ID and take appropriate action.All these action code
> for a particular CAN ID our application should be capable to do.
What you describe is a layer on top of raw CAN. There are many different
layers on top of raw CAN, some of them are even standardized. The usage
of the CAN id depends on the uppers layers.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
parent reply other threads:[~2013-08-20 11:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8A49CFF5759B8644A46158D75AFC117D68584B51@AUSP01DAG0102.collaborationhost.net>]
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=52134CD0.5030209@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anil.mathews@mindteck.com \
--cc=linux-can@vger.kernel.org \
--cc=r.valler@enextra.de \
/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).