Re: Socketcan-users Digest, Vol 77, Issue 2

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Socketcan-users Digest, Vol 77, Issue 2

Anil Mathews (India - Bangalore)
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.

Anil Mathews
________________________________________________________________________

Mindteck | No. 10, Industrial Layout, 7th Main, 80 Feet Road, 3rd Block, Koramangala, Bangalore 560034, India
Email: [hidden email] | Tel: +91 80 4154 8000; Mob No:919535529638 | www.mindteck.com

--------------

Disclaimer
This message is for the named recipient(s) above and may contain confidential, proprietary or legally privileged information of MINDTECK.  If you have received this message in error, please immediately delete all copies of it, and notify the sender.  Do not disseminate this message to anyone if you are not the intended recipient.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of [hidden email]
Sent: Tuesday, August 20, 2013 3:30 PM
To: [hidden email]
Subject: Socketcan-users Digest, Vol 77, Issue 2

Send Socketcan-users mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.berlios.de/mailman/listinfo/socketcan-users
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific than "Re: Contents of Socketcan-users digest..."


Today's Topics:

   1. Finding a transmitter's CAN ID (Rob__V)
   2. Re: Finding a transmitter's CAN ID (Stefan May)
   3. Re: Finding a transmitter's CAN ID (Steffen Rose)


----------------------------------------------------------------------

Message: 1
Date: Mon, 19 Aug 2013 07:43:59 -0700 (PDT)
From: Rob__V <[hidden email]>
To: [hidden email]
Subject: [Socketcan-users] Finding a transmitter's CAN ID
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Hi all,

I am currently working on a project with several embedded platforms connect via CAN:
1 x Linux board connected via SocketCAN
N x embedded boards using the Atmega16M1 (CAN) MCU.

The Linux board is 'treated' as the master and needs to know the CAN ID of each atmega board that sends it a CAN message. So my question is :

How is the Linux/SocketCAN board able to determine the CAN ID of other networked nodes when they transmit ?

Of course, each CAN node can determine the target ID for each message but I am not sure if the source ID is known ... outside of arbitration.


Thank you for your time.

All the best,
Rob



--
View this message in context: http://socket-can.996257.n3.nabble.com/Finding-a-transmitter-s-CAN-ID-tp7678.html
Sent from the Socket-CAN Users mailing list archive at Nabble.com.


------------------------------

Message: 2
Date: Mon, 19 Aug 2013 17:02:58 +0200
From: Stefan May <[hidden email]>
To: Rob__V <[hidden email]>
Cc: [hidden email]
Subject: Re: [Socketcan-users] Finding a transmitter's CAN ID
Message-ID: <1376924578.4851.17.camel@mpslxmarvin>
Content-Type: text/plain; charset="utf-8"

You cannot determine the source of a CAN message as the CAN bus is a broadcast bus. There is no concept of addressable nodes in CAN.

mfg, Stefan.


On Mo, 2013-08-19 at 07:43 -0700, Rob__V wrote:

> Hi all,
>
> I am currently working on a project with several embedded platforms
> connect via CAN:
> 1 x Linux board connected via SocketCAN N x embedded boards using the
> Atmega16M1 (CAN) MCU.
>
> The Linux board is 'treated' as the master and needs to know the CAN
> ID of each atmega board that sends it a CAN message. So my question is
> :
>
> How is the Linux/SocketCAN board able to determine the CAN ID of other
> networked nodes when they transmit ?
>
> Of course, each CAN node can determine the target ID for each message
> but I am not sure if the source ID is known ... outside of arbitration.
>
>
> Thank you for your time.
>
> All the best,
> Rob
>
>
>
> --
> View this message in context:
> http://socket-can.996257.n3.nabble.com/Finding-a-transmitter-s-CAN-ID-
> tp7678.html Sent from the Socket-CAN Users mailing list archive at
> Nabble.com.
> _______________________________________________
> Socketcan-users mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/socketcan-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://lists.berlios.de/pipermail/socketcan-users/attachments/20130819/a2c4290c/attachment-0001.pgp>

------------------------------

Message: 3
Date: Tue, 20 Aug 2013 09:42:27 +0200
From: Steffen Rose <[hidden email]>
To: [hidden email]
Subject: Re: [Socketcan-users] Finding a transmitter's CAN ID
Message-ID: <2691849.HSteIlc2iz@lisa>
Content-Type: text/plain; charset="utf-8"

Hello,

> How is the Linux/SocketCAN board able to determine the CAN ID of other
> networked nodes when they transmit ?

Within CAN network every CANID should have only one transmitter. It is your definition to define a rule, which node can send a specific CAN Id.

But in case a node works wrong and send a not allowed CAN Id it is a problem to determine the transmitter.

--
Mit freundlichen Gr??en / Best regards
Steffen Rose



------------------------------

_______________________________________________
Socketcan-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/socketcan-users

End of Socketcan-users Digest, Vol 77, Issue 2
**********************************************

______________________________________________________________________
This email has been scanned by the Boundary Defense for Email Security System. For more information please visit http://www.apptix.com/email-security/antispam-virus
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Boundary Defense for Email Security System. For more information please visit http://www.apptix.com/email-security/antispam-virus
______________________________________________________________________
_______________________________________________
Socketcan-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/socketcan-users
Reply | Threaded
Open this post in threaded view
|

FW: Socketcan-users Digest, Vol 77, Issue 2

Anil Mathews (India - Bangalore)







Anil Mathews
________________________________________________________________________

Mindteck | No. 10, Industrial Layout, 7th Main, 80 Feet Road, 3rd Block, Koramangala, Bangalore 560034, India
Email: [hidden email] | Tel: +91 80 4154 8000; Mob No:919535529638 | www.mindteck.com

--------------

Disclaimer
This message is for the named recipient(s) above and may contain confidential, proprietary or legally privileged information of MINDTECK.  If you have received this message in error, please immediately delete all copies of it, and notify the sender.  Do not disseminate this message to anyone if you are not the intended recipient.

FYI..
-----Original Message-----
From: Anil Mathews (India - Bangalore)
Sent: Tuesday, August 20, 2013 4:12 PM
To: [hidden email]
Subject: RE: Socketcan-users Digest, Vol 77, Issue 2

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.

Anil Mathews
________________________________________________________________________

Mindteck | No. 10, Industrial Layout, 7th Main, 80 Feet Road, 3rd Block, Koramangala, Bangalore 560034, India
Email: [hidden email] | Tel: +91 80 4154 8000; Mob No:919535529638 | www.mindteck.com

--------------

Disclaimer
This message is for the named recipient(s) above and may contain confidential, proprietary or legally privileged information of MINDTECK.  If you have received this message in error, please immediately delete all copies of it, and notify the sender.  Do not disseminate this message to anyone if you are not the intended recipient.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of [hidden email]
Sent: Tuesday, August 20, 2013 3:30 PM
To: [hidden email]
Subject: Socketcan-users Digest, Vol 77, Issue 2

Send Socketcan-users mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.berlios.de/mailman/listinfo/socketcan-users
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific than "Re: Contents of Socketcan-users digest..."


Today's Topics:

   1. Finding a transmitter's CAN ID (Rob__V)
   2. Re: Finding a transmitter's CAN ID (Stefan May)
   3. Re: Finding a transmitter's CAN ID (Steffen Rose)


----------------------------------------------------------------------

Message: 1
Date: Mon, 19 Aug 2013 07:43:59 -0700 (PDT)
From: Rob__V <[hidden email]>
To: [hidden email]
Subject: [Socketcan-users] Finding a transmitter's CAN ID
Message-ID: <[hidden email]>
Content-Type: text/plain; charset=us-ascii

Hi all,

I am currently working on a project with several embedded platforms connect via CAN:
1 x Linux board connected via SocketCAN
N x embedded boards using the Atmega16M1 (CAN) MCU.

The Linux board is 'treated' as the master and needs to know the CAN ID of each atmega board that sends it a CAN message. So my question is :

How is the Linux/SocketCAN board able to determine the CAN ID of other networked nodes when they transmit ?

Of course, each CAN node can determine the target ID for each message but I am not sure if the source ID is known ... outside of arbitration.


Thank you for your time.

All the best,
Rob



--
View this message in context: http://socket-can.996257.n3.nabble.com/Finding-a-transmitter-s-CAN-ID-tp7678.html
Sent from the Socket-CAN Users mailing list archive at Nabble.com.


------------------------------

Message: 2
Date: Mon, 19 Aug 2013 17:02:58 +0200
From: Stefan May <[hidden email]>
To: Rob__V <[hidden email]>
Cc: [hidden email]
Subject: Re: [Socketcan-users] Finding a transmitter's CAN ID
Message-ID: <1376924578.4851.17.camel@mpslxmarvin>
Content-Type: text/plain; charset="utf-8"

You cannot determine the source of a CAN message as the CAN bus is a broadcast bus. There is no concept of addressable nodes in CAN.

mfg, Stefan.


On Mo, 2013-08-19 at 07:43 -0700, Rob__V wrote:

> Hi all,
>
> I am currently working on a project with several embedded platforms
> connect via CAN:
> 1 x Linux board connected via SocketCAN N x embedded boards using the
> Atmega16M1 (CAN) MCU.
>
> The Linux board is 'treated' as the master and needs to know the CAN
> ID of each atmega board that sends it a CAN message. So my question is
> :
>
> How is the Linux/SocketCAN board able to determine the CAN ID of other
> networked nodes when they transmit ?
>
> Of course, each CAN node can determine the target ID for each message
> but I am not sure if the source ID is known ... outside of arbitration.
>
>
> Thank you for your time.
>
> All the best,
> Rob
>
>
>
> --
> View this message in context:
> http://socket-can.996257.n3.nabble.com/Finding-a-transmitter-s-CAN-ID-
> tp7678.html Sent from the Socket-CAN Users mailing list archive at
> Nabble.com.
> _______________________________________________
> Socketcan-users mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/socketcan-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://lists.berlios.de/pipermail/socketcan-users/attachments/20130819/a2c4290c/attachment-0001.pgp>

------------------------------

Message: 3
Date: Tue, 20 Aug 2013 09:42:27 +0200
From: Steffen Rose <[hidden email]>
To: [hidden email]
Subject: Re: [Socketcan-users] Finding a transmitter's CAN ID
Message-ID: <2691849.HSteIlc2iz@lisa>
Content-Type: text/plain; charset="utf-8"

Hello,

> How is the Linux/SocketCAN board able to determine the CAN ID of other
> networked nodes when they transmit ?

Within CAN network every CANID should have only one transmitter. It is your definition to define a rule, which node can send a specific CAN Id.

But in case a node works wrong and send a not allowed CAN Id it is a problem to determine the transmitter.

--
Mit freundlichen Gr??en / Best regards
Steffen Rose



------------------------------

_______________________________________________
Socketcan-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/socketcan-users

End of Socketcan-users Digest, Vol 77, Issue 2
**********************************************

______________________________________________________________________
This email has been scanned by the Boundary Defense for Email Security System. For more information please visit http://www.apptix.com/email-security/antispam-virus
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Boundary Defense for Email Security System. For more information please visit http://www.apptix.com/email-security/antispam-virus
______________________________________________________________________
_______________________________________________
Socketcan-users mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/socketcan-users