From: "Heinz-Jürgen Oertel" <oe@emtas.de>
To: vklein <vk4514@arcor.de>
Cc: linux-can@vger.kernel.org
Subject: Re: newbi Question: NMEA2000 and BeagleBone
Date: Thu, 26 Mar 2015 17:35:05 +0100 [thread overview]
Message-ID: <3106872.8FfSxeHsfU@heinz> (raw)
In-Reply-To: <551432DB.8010406@arcor.de>
Am Donnerstag, 26. März 2015, 17:24:59 schrieb vklein:
> Am 26.03.2015 um 16:50 schrieb Heinz-Jürgen Oertel:
> > Am Donnerstag, 26. März 2015, 14:36:39 schrieb vklein:
> >> At the moment I use a Actisense NTG-1 USB and a Raspberry pi with the
> >> canboat software.
> >
> > It looks like the
> > Actisense NTG-1 USB
> > http://www.actisense.com/products/nmea-2000/ngt-1/ngt1-specs.html
> > is already a CAN interface and canboat can interprete the NMEA2000 PGNs.
> > What else do you need?
> > And if the software runs on the Raspberry it will run on the BeagleBone
too.
> >
> >
> The actisense-NTG1 is exactly the hardware I use.
> But its rather expensive (189 € ) and there may be another way to get
> the data.
>
>
There are many cheaper CAN USB interfaces.
And of course you can use the integrated CAN in the BeagleBone.
You have to add a transceiver and for system security galvanic isolation.
Because canboat is open source, it should be easy to adopt the SocketCAN or
can4linux CAN message format. In any case you don't need the J1939 software.
Only receiving NMEA frames is easy, decoding the PGNs requires knowledge of
it.
--
Mit freundlichen Grüßen
Heinz-Jürgen Oertel
emtas GmbH
next prev parent reply other threads:[~2015-03-26 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 13:36 newbi Question: NMEA2000 and BeagleBone vklein
[not found] ` <3468382.ObYm91FbAa@heinz>
[not found] ` <551432DB.8010406@arcor.de>
2015-03-26 16:35 ` Heinz-Jürgen Oertel [this message]
2015-03-26 23:29 ` Andrew Lentvorski
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=3106872.8FfSxeHsfU@heinz \
--to=oe@emtas.de \
--cc=linux-can@vger.kernel.org \
--cc=vk4514@arcor.de \
/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.