https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6651
--- Comment #6 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2011-12-08 15:06:26 CET ---
(In reply to comment #3)
> (In reply to comment #2)
> > Is CANopen a higher layer protocol, on top of SocketCAN, or an alternative
> > protocol, besides SocketCAN?
> >
...
> SocketCAN (http://en.wikipedia.org/wiki/Socketcan) is just a driver/framework
> for CAN (http://en.wikipedia.org/wiki/Controller_area_network). So SocketCAN
> dissector fetches a CAN frame (ID, flags, data length and data (max. 8 bytes)).
> This is raw CAN data without much interpretation. This is sufficient for custom
> protocols running over CAN or diagnostics.
>
> CANopen (http://en.wikipedia.org/wiki/Canopen) uses CAN as transportation layer
> and really interprets the CAN frames. The problem is it uses both ID and data,
> so I can't just pass the 8 bytes of data field. I need the whole CAN frame. The
> separation of SocketCAN and CANopen gives me on overview about CAN frame flags
> like extended/standard frame, error frame etc. In CANopen dissector I provide
> info about CANopen frame type and its fields.
>
So what you are saying is that both SocketCAN and CANopen sit on top of the
CAN datalink layer? CANopen has no relation with SocketCAN other than working
on the same communications medium?
Then one or the other should bind to WTAP_ENCAP_SOCKETCAN and LINUX_SLL_P_CAN,
not stacked like this.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.