From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Brent Sink <Brent.Sink@we-ics.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>,
Kurt Van Dijck <kurt.van.dijck@eia.be>
Subject: Re: Reading messages that use BAM, or have a DLC larger than 8
Date: Wed, 21 Aug 2013 22:19:22 +0200 [thread overview]
Message-ID: <521520CA.5080700@pengutronix.de> (raw)
In-Reply-To: <52151DCA.3000606@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On 08/21/2013 08:43 PM, Brent Sink wrote:
> How do I read J1939 messages that use the BAM format? Some of the
> diagnostic messages that are on the DM01 message have a DLC that is
> often larger than 8 bytes when the message contains more than one
> error. Is there something special that I need to do to enable reading
> these messages? Thanks!
With mainline linux you just receive raw CAN frames. I'm not a j1939
expert, as far as I can see, BAM is a transport protocol for CAN.
There are two options:
1) You have to implement the BAM protocol yourself either,
a) inside the kernel or
b) inside userspace.
2) Talk to Kurt (Cc'ed) if his j1939 patches support BAM.
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 --]
next prev parent reply other threads:[~2013-08-21 20:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9522AFA707AD744DA5CF5DF53E30277430EEDB1B86@WEICSUS1.weics.local>
[not found] ` <9522AFA707AD744DA5CF5DF53E30277430EEDB1B86-m2CP4sPuupzvI/EAa86jFoT4S9po1h25@public.gmane.org>
2013-08-21 20:06 ` [SPAM] Reading messages that use BAM, or have a DLC larger than 8 Marc Kleine-Budde
2013-08-21 20:19 ` Marc Kleine-Budde [this message]
2013-08-22 7:56 ` Kurt Van Dijck
2013-08-22 14:22 ` Brent Sink
2013-08-22 14:38 ` Kurt Van Dijck
2013-08-22 16:24 ` Brent Sink
2013-08-22 17:56 ` Kurt Van Dijck
2013-08-26 20:00 ` Brent Sink
2013-08-27 6:54 ` Kurt Van Dijck
2013-08-27 18:17 ` Brent Sink
2013-08-27 21:00 ` Kurt Van Dijck
[not found] ` <1377640991.4869.13.camel@ergasia.protologos.net>
2013-08-28 9:29 ` Kurt Van Dijck
[not found] ` <1377694586.1254.25.camel@ergasia.protologos.net>
2013-08-29 19:36 ` Kurt Van Dijck
2013-08-29 15:02 ` AW: " Michael Luxen
2013-08-29 19:56 ` Kurt Van Dijck
2013-08-30 9:28 ` AW: " Michael Luxen
2013-08-30 17:57 ` Kurt Van Dijck
2013-08-30 18:06 ` Kurt Van Dijck
2013-08-27 0:30 ` Brent Sink
2013-08-27 7:02 ` Kurt Van Dijck
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=521520CA.5080700@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=Brent.Sink@we-ics.com \
--cc=kurt.van.dijck@eia.be \
--cc=linux-can@vger.kernel.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.