From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Mike Mogenson <michael.mogenson@gmail.com>
Cc: "linux-can@vger.kernel.org" <linux-can@vger.kernel.org>
Subject: Re: Acknowledging messages with SocketCAN
Date: Tue, 04 Jun 2013 18:33:47 +0200 [thread overview]
Message-ID: <51AE16EB.6080209@pengutronix.de> (raw)
In-Reply-To: <CALr1zciumzF8ijW-o4YabN3oi=wf+Ph9N9XSH+b=b1UPQhgzww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
Hello Mike,
please use the linux-can mailinglist (Cc'ed)
On 06/04/2013 06:21 PM, Mike Mogenson wrote:
> First, thank you for your project.
I'm just one of the developers working on this project, you're welcome.
> Second, I'm using your can-utils on a BeagleBone running Ubuntu with the
> 3.2 kernel. Everything is working well with my can0 device in loopback
> mode. However, when I connect a CAN enabled motor controller to the
> CANbus, the BeagleBone doesn't appear to acknowledge the motor
> controller's heartbeat message and the motor controller retries its
> message over and over.
It's normal behaviour that a CAN node repeats the message if it is not
acked on the bus.
> I don't see anything with candump or in
> /proc/net/can/stats, but I can see the message repeating over and over
> with an oscilloscope on the CANbus.
Ensure that your CAN network is properly terminated on both ends (120 Ohms).
Configure the bitrate of your d-can correctly, it must be the same as
the bitrate of your motor. With canutils:
canconfig can0 bitrate 1250000
or iproute2's ip (the "ip" from busybox doesn't work):
ip link set can0 type can bitrate 125000
Then activate your CAN:
ifconfig can0 up
> Do I have to configure SocketCAN on the BeagleBone
> to acknowledge messages? How can I set the BeagleBone to have a
> specific Node ID? To my knowledge, the heartbeat message is not
> directed at a specific Node ID, but I will eventually need to direct
> messages from CAN devices to the BeagleBone.
regards,
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: 263 bytes --]
parent reply other threads:[~2013-06-04 16:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CALr1zciumzF8ijW-o4YabN3oi=wf+Ph9N9XSH+b=b1UPQhgzww@mail.gmail.com>]
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=51AE16EB.6080209@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=michael.mogenson@gmail.com \
/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.