From: Giox79 <giovanniparodi79@gmail.com>
To: linux-can@vger.kernel.org
Subject: Re: Parsing j1939 from raw candump
Date: Tue, 26 Mar 2013 21:17:40 +0000 (UTC) [thread overview]
Message-ID: <loom.20130326T221001-133@post.gmane.org> (raw)
In-Reply-To: 20130326191831.GA22696@vandijck-laurijssen.be
Hi Kurt, first thanks a lot
Kurt Van Dijck <kurt.van.dijck <at> eia.be> writes:
>
> On Mon, Mar 25, 2013 at 09:02:43PM +0000, Giox79 wrote:
> > Is there anyone that can suggest me how to approach
> > this topic? I tried using the j1939-71 standard,
> > but as far as I understand, it explains differences between
> > different packages, but I didn't find an
> > explanation about header and trailer of J1939 packet.
>
> j1939-21 & j1939-81
> are the ones used by the j1939 linux kernel.
Mumble, I was wrong.
So as far as I understand, I have to use J1939-71 only after decoding from raw
to j1939 using the suggested docs.
I can use 71 to understand the payload of J1939 packets.
Am I right?
>
> > Please note that I have the whole j1939 standard and that
> > at present time I can't integrate the j1939 canutils in linux
> > kernel because I should use for other kind of constraints
> > a 2.6 linux kernel.
>
> which specific 2.6 one did it start from (like 2.6.28 or 2.6.35 or ...)
The version is 2.6.35.3
>
> > Any help, reference to specific sections of j1939 standard
> > and so on will be appreciated.
> > Giovanni
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-can" in
> > the body of a message to majordomo <at> vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-03-26 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 21:02 Parsing j1939 from raw candump Giox79
2013-03-26 19:18 ` Kurt Van Dijck
2013-03-26 21:17 ` Giox79 [this message]
2013-03-27 8:09 ` Kurt Van Dijck
2013-03-27 12:04 ` Kurt Van Dijck
2013-03-27 12:36 ` Giox79
2013-03-27 13:25 ` Kurt Van Dijck
2013-04-02 19:53 ` Giox79
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=loom.20130326T221001-133@post.gmane.org \
--to=giovanniparodi79@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox