From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Michael Economides <mecono@gmail.com>
Cc: linux-can@vger.kernel.org
Subject: Re: read() question from newbie
Date: Tue, 17 Apr 2012 08:08:18 +0200 [thread overview]
Message-ID: <4F8D08D2.3090701@hartkopp.net> (raw)
In-Reply-To: <CABHoAv=FhULnAY+a2CbNjdyEEOoBKdEAezL7NQLo+PdfeyRTow@mail.gmail.com>
On 17.04.2012 06:16, Michael Economides wrote:
>>
>> I assume there is a CAN bus problem:
>>
>> - wiring (CAN_L/CAN_H)
>> - correct CAN termination (2x 120 Ohms)
>> - different bitrate
>>
>
> I think you are right, but I have checked that, it looks ok. I will
> check again.
>
> I am using a PCAN USB adapter, and the PCAN software says there is an
> "acknowledge error" when it sends a frame to my Linux board.
This is an indication for a missing counterpart CAN node:
- Wrong connection wiring
- Wrong termination
- Wrong bitrate
>
> When the Linux board tries to send a frame to PCAN, the PCAN software
> says "form error acknowledge delimiter".
>
> It seems this is the same error in both cases, just worded differently.
Yes. But this means the same regarding the obvious problems.
>
> In your opinion, is this most likely a hardware issue? Or is there
> still some way I could be doing something wrong at the software level?
Did you swap CAN_H / CAN_L ??
It's definitely one of the three points above. No SW problem ...
Try to add a third CAN node - if you have one.
Regards,
Oliver
next prev parent reply other threads:[~2012-04-17 6:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABHoAvngDnUfh6w7NXQksrmeLq52_cRp809rFZ+HriwYpZqo9w@mail.gmail.com>
2012-03-02 22:09 ` read() question from newbie Michael Economides
2012-03-03 9:05 ` Oliver Hartkopp
2012-03-05 17:49 ` Michael Economides
2012-03-05 22:19 ` Oliver Hartkopp
2012-03-05 22:22 ` Oliver Hartkopp
2012-03-06 18:53 ` Michael Economides
2012-03-06 20:14 ` Oliver Hartkopp
2012-04-17 4:16 ` Michael Economides
2012-04-17 6:08 ` Oliver Hartkopp [this message]
2012-04-18 20:13 ` Michael Economides
2012-04-18 20:32 ` Wolfgang Grandegger
2012-04-18 23:10 ` Michael Economides
2012-04-19 8:39 ` Wolfgang Grandegger
2012-04-18 20:59 ` Marc Kleine-Budde
2012-04-18 21:21 ` Michael Economides
2012-04-19 7:27 ` Marc Kleine-Budde
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=4F8D08D2.3090701@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@vger.kernel.org \
--cc=mecono@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.