* Re: [Socketcan-users] Socketcan-users Digest, Vol 77, Issue 2
[not found] ` <8A49CFF5759B8644A46158D75AFC117D68584B51@AUSP01DAG0102.collaborationhost.net>
@ 2013-08-20 11:02 ` Marc Kleine-Budde
0 siblings, 0 replies; only message in thread
From: Marc Kleine-Budde @ 2013-08-20 11:02 UTC (permalink / raw)
To: Anil Mathews (India - Bangalore); +Cc: linux-can@vger.kernel.org, Rob__V
[-- 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 --]
^ permalink raw reply [flat|nested] only message in thread