All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Max S." <max@schneidersoft.net>
To: Austin Schuh <austin@peloton-tech.com>
Cc: linux-can@vger.kernel.org
Subject: Re: Bus off
Date: Thu, 26 Jun 2014 22:54:23 +0000	[thread overview]
Message-ID: <1403823263.24938.12.camel@blackbox> (raw)
In-Reply-To: <CANGgnMZyG1UDVigM-68tu27=oNYfaw0OWxCv4uT+NfN4v=vm2A@mail.gmail.com>

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 controller will wait for linux to restart it, it will probably
retry transmitting the frame upon being restart.

Restart does not mean reset as far as i know.

Regardless of what state the linux queue is in the frame in the
controllers outgoing message objects will continue to try to send,
unless explicitly told to cancel transmission. (at least on the
controllers i know. not that many :/)

Hence you will see the cycling error frames.

typically heartbeat frames are used to tell if a node exists or not.
each node send a predefined message at a desired interval, and you just
listen.

Regards,
Max S.

On Thu, 2014-06-26 at 10:13 -0700, Austin Schuh wrote:
> Does anyone know if the TX queues are cleared on BUS-OFF?
> 
> I have a machine connected to a network where all the other CAN nodes
> shut off periodically.  I monitor whether or not they are sending, and
> don't send messages unless I think they are on.  Right after they shut
> off, I occasionally send out a message when they are off, which
> triggers a bus-off.  I'm seeing lots of bus-off/restarts due to
> restart-ms=1000 after the nodes shut down, and I'm pretty certain that
> I'm not sending anything at that time.  Any ideas on what is going on
> would be appreciated.
> 
> Thanks,
>     Austin
> --
> To unsubscribe from this list: send the line "unsubscribe linux-can" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  reply	other threads:[~2014-06-26 22:55 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. [this message]
2014-06-27  7:04   ` Marc Kleine-Budde
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=1403823263.24938.12.camel@blackbox \
    --to=max@schneidersoft.net \
    --cc=austin@peloton-tech.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 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.