Linux CAN drivers development
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@pengutronix.de>
To: "Max S." <max@schneidersoft.net>, Austin Schuh <austin@peloton-tech.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Bus off
Date: Fri, 27 Jun 2014 09:04:19 +0200	[thread overview]
Message-ID: <53AD1773.1090300@pengutronix.de> (raw)
In-Reply-To: <1403823263.24938.12.camel@blackbox>

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]

On 06/27/2014 12:54 AM, Max S. wrote:
> When there is only one node. The lone node will continuously attempt to
> transmit.
> 
> the tx error counter will increase and the node will move from
> error_active to error_passive, and then to bus_off. At least one node I
> know of will leave bus_off when it receives 128x11 consecutive dominant
> bits and ten try to send again.

If the bus is properly terminated, a lone CAN node will not go into bus
off, though its error counters will increase until error passive.

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: 242 bytes --]

  reply	other threads:[~2014-06-27  7:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 17:13 Bus off Austin Schuh
2014-06-26 22:54 ` Max S.
2014-06-27  7:04   ` Marc Kleine-Budde [this message]
2014-06-27  5:05 ` Kurt Van Dijck
2014-06-27 15:22   ` Jason R1 White
2014-06-27 15:35     ` Wolfgang Grandegger
2014-06-27 15:45       ` Jason R1 White
2014-06-27 15:50         ` Marc Kleine-Budde
2014-06-27 16:28         ` Wolfgang Grandegger
2014-06-27 17:34           ` Oliver Hartkopp
2014-06-28  1:29             ` Austin Schuh
2014-06-28  8:52               ` Wolfgang Grandegger
2014-06-28 18:48                 ` Austin Schuh

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=53AD1773.1090300@pengutronix.de \
    --to=mkl@pengutronix.de \
    --cc=austin@peloton-tech.com \
    --cc=linux-can@vger.kernel.org \
    --cc=max@schneidersoft.net \
    /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